Project Number Date
test_Tails_ISO_stable 4735 22 Mar 2024, 11:59

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 17:19.365 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
1:47.674
Before features/support/hooks.rb:245 0.006
Given a computer 0.192
And I create a 7200 MiB disk named "old" 0.034
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 26.052
When I start Tails from USB drive "old" with network unplugged 1:16.654
Then the boot device has safe access rights 2.770
And Tails is running from USB drive "old" 0.298
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.070
And udev-watchdog is monitoring the correct device 0.300
And I unplug USB drive "old" 0.176
After features/support/hooks.rb:291 3.530
After features/support/hooks.rb:75 0.008
Tags: @product
1:59.177
Before features/support/hooks.rb:245 0.005
Given a computer 0.241
And I start Tails from USB drive "old" with network unplugged and I login 1:13.748
Then Tails is running from USB drive "old" 0.345
And I create a persistent partition 35.707
And I take note of which tps features are available 1.346
Then a Tails persistence partition exists on USB drive "old" 0.765
And I shutdown Tails and wait for the computer to power off 7.022
After features/support/hooks.rb:291 0.169
After features/support/hooks.rb:75 0.010
Tags: @product
2:28.627
Before features/support/hooks.rb:245 0.006
Given a computer 0.172
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:0.704
Then Tails is running from USB drive "old" 0.339
And all tps features are active 1.651
When I write some files expected to persist 1.560
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.197
And all persistence configuration files have safe access rights 0.366
And all persistent directories from the old Tails version have safe access rights 2.729
And I take note of which tps features are available 1.783
And I shutdown Tails and wait for the computer to power off 4.016
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.106
After features/support/hooks.rb:291 0.106
After features/support/hooks.rb:75 0.011
Tags: @product
2:23.981
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.761
And I log in to a new session 17.693
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.743
And I plug USB drive "to_upgrade" 2.415
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.535
Then the running Tails is installed on USB drive "to_upgrade" 12.459
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.173
After features/support/hooks.rb:291 3.541
After features/support/hooks.rb:75 0.000
Tags: @product
2:11.849
Before features/support/hooks.rb:245 0.007
Given a computer 0.171
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.761
Then all tps features from the old Tails version are active 1.358
And Tails is running from USB drive "to_upgrade" 0.357
And the boot device has safe access rights 2.975
And the expected persistent files created with the old Tails version are present in the filesystem 1.714
And all persistent directories from the old Tails version have safe access rights 2.511
After features/support/hooks.rb:291 0.820
After features/support/hooks.rb:75 0.010
5:54.908
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.569
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.299
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.277
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.445
When the network is plugged 0.035
And Tor is ready 19.768
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.388
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.621
Given I shutdown Tails and wait for the computer to power off 6.093
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.324
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.706
And the file system changes introduced in version 6.2~testoverlayfs are present 0.287
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.341
# 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.242
When the network is plugged 0.123
And Tor is ready 18.260
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.420
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.044
Given I shutdown Tails and wait for the computer to power off 4.019
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.387
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.705
And the file system changes introduced in version 6.3~testoverlayfs are present 0.447
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.292
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.233
When the network is plugged 0.041
And Tor is ready 17.510
Then the Upgrader considers the system as up-to-date 0.275
# 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 13.450
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.956
After features/support/hooks.rb:291 0.646
After features/support/hooks.rb:75 0.021
33.146
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.749
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.306
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.826
But a current signing key is available on our website 0.000
When the network is plugged 0.041
And Tor is ready 17.092
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.073
After features/support/hooks.rb:291 0.890
After features/support/hooks.rb:75 0.000