Project Number Date
test_Tails_ISO_20524-warn-danger-unplug-usb-stick 13 31 Oct 2024, 19:15

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 87 0 0 0 0 87 7 0 7 21:47.601 Passed
Tags: @product
Feature Upgrading an old Tails USB installation
As a Tails user If I have an old version of Tails installed on a USB device and the USB device has a Persistent Storage I want to upgrade Tails on it and keep my Persistent Storage in the process
Tags: @product
2:9.561
Before features/support/hooks.rb:269 0.003
Given a computer 0.201
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 31.214
When I start Tails from USB drive "old" with network unplugged 1:32.503
Then the boot device has safe access rights 3.518
And Tails is running from USB drive "old" 0.322
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.325
And I unplug USB drive "old" 0.215
After features/support/hooks.rb:326 7.141
After features/support/hooks.rb:100 0.008
Tags: @product
2:21.773
Before features/support/hooks.rb:269 0.002
Given a computer 0.172
And I start Tails from USB drive "old" with network unplugged and I login 1:35.488
Then Tails is running from USB drive "old" 0.358
And I create a persistent partition 33.991
And I take note of which tps features are available 1.576
Then a Tails persistence partition exists on USB drive "old" 0.898
And I shutdown Tails and wait for the computer to power off 9.287
After features/support/hooks.rb:326 0.224
After features/support/hooks.rb:100 0.008
Tags: @product
3:4.242
Before features/support/hooks.rb:269 0.003
Given a computer 0.230
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.079
Then Tails is running from USB drive "old" 0.404
And all tps features are active 2.857
When I write some files expected to persist 2.072
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.248
And all persistence configuration files have safe access rights 0.450
And all persistent directories from the old Tails version have safe access rights 2.762
And I take note of which tps features are available 0.537
And I shutdown Tails and wait for the computer to power off 4.210
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.388
After features/support/hooks.rb:326 0.199
After features/support/hooks.rb:100 0.007
Tags: @product
2:55.325
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 23.302
And I log in to a new session 26.728
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.982
And I plug USB drive "to_upgrade" 2.831
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.245
Then the running Tails is installed on USB drive "to_upgrade" 21.768
And I unplug USB drive "to_upgrade" 0.235
And I unplug USB drive "__internal" 0.232
After features/support/hooks.rb:326 8.559
After features/support/hooks.rb:100 0.000
Tags: @product
2:30.480
Before features/support/hooks.rb:269 0.003
Given a computer 0.205
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:19.857
Then all tps features from the old Tails version are active 2.053
And Tails is running from USB drive "to_upgrade" 0.448
And the boot device has safe access rights 3.658
And the expected persistent files created with the old Tails version are present in the filesystem 1.683
And all persistent directories from the old Tails version have safe access rights 2.572
After features/support/hooks.rb:326 1.449
After features/support/hooks.rb:100 0.008
8:7.339
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.947
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.600
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.320
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.493
When the network is plugged 0.073
And Tor is ready 22.431
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.175
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.484
Given I shutdown Tails and wait for the computer to power off 1:36.858
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.944
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.777
And the file system changes introduced in version 6.2~testoverlayfs are present 0.390
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.342
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.iuk
# but we need some way to force upgrading a second time in a row
# even if only the initially installed version is considered
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.299
When the network is plugged 0.067
And Tor is ready 17.840
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.849
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.809
Given I shutdown Tails and wait for the computer to power off 4.778
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.383
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 3.215
And the file system changes introduced in version 6.3~testoverlayfs are present 0.649
And only the 6.3~testoverlayfs SquashFS delta is installed 0.089
# Regression test for #17425 (i.e. the Upgrader would propose
# upgrading to the version that's already running)
Given Tails system time is magically synchronized 0.441
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.595
When the network is plugged 0.089
And Tor is ready 20.737
Then the Upgrader considers the system as up-to-date 0.396
# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)
And I successfully start the Unsafe Browser 18.603
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.384
After features/support/hooks.rb:326 0.829
After features/support/hooks.rb:100 0.012
38.877
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.651
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.429
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the signing key used by the Upgrader is outdated 1.077
But a current signing key is available on our website 0.000
When the network is plugged 0.104
And Tor is ready 20.234
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.297
After features/support/hooks.rb:326 0.707
After features/support/hooks.rb:100 0.000