Project Number Date
test_Tails_ISO_stable 5015 11 Aug 2024, 12:24

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 19:10.304 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:15.079
Before features/support/hooks.rb:269 0.008
Given a computer 0.218
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 29.320
When I start Tails from USB drive "old" with network unplugged 1:40.327
Then the boot device has safe access rights 3.154
And Tails is running from USB drive "old" 0.318
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.310
And I unplug USB drive "old" 0.173
After features/support/hooks.rb:326 3.515
After features/support/hooks.rb:100 0.024
Tags: @product
2:13.888
Before features/support/hooks.rb:269 0.006
Given a computer 0.240
And I start Tails from USB drive "old" with network unplugged and I login 1:31.683
Then Tails is running from USB drive "old" 0.319
And I create a persistent partition 30.692
And I take note of which tps features are available 1.654
Then a Tails persistence partition exists on USB drive "old" 0.764
And I shutdown Tails and wait for the computer to power off 8.533
After features/support/hooks.rb:326 0.165
After features/support/hooks.rb:100 0.009
Tags: @product
2:46.734
Before features/support/hooks.rb:269 0.006
Given a computer 0.234
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:9.134
Then Tails is running from USB drive "old" 0.328
And all tps features are active 2.495
When I write some files expected to persist 1.612
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.235
And all persistence configuration files have safe access rights 0.388
And all persistent directories from the old Tails version have safe access rights 2.623
And I take note of which tps features are available 0.636
And I shutdown Tails and wait for the computer to power off 4.272
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.771
After features/support/hooks.rb:326 0.150
After features/support/hooks.rb:100 0.010
Tags: @product
2:35.487
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.608
And I log in to a new session 23.697
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.506
And I plug USB drive "to_upgrade" 2.417
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.323
Then the running Tails is installed on USB drive "to_upgrade" 17.519
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.206
After features/support/hooks.rb:326 1.902
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.936
Before features/support/hooks.rb:269 0.007
Given a computer 0.218
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.664
Then all tps features from the old Tails version are active 1.644
And Tails is running from USB drive "to_upgrade" 0.313
And the boot device has safe access rights 3.085
And the expected persistent files created with the old Tails version are present in the filesystem 1.513
And all persistent directories from the old Tails version have safe access rights 2.497
After features/support/hooks.rb:326 0.709
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:26.879
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.325
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.402
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.324
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.441
When the network is plugged 0.072
And Tor is ready 23.089
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.356
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.078
Given I shutdown Tails and wait for the computer to power off 8.694
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.209
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.180
And the file system changes introduced in version 6.2~testoverlayfs are present 0.369
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.334
# 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.315
When the network is plugged 0.062
And Tor is ready 18.983
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.900
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.158
Given I shutdown Tails and wait for the computer to power off 4.311
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.486
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.949
And the file system changes introduced in version 6.3~testoverlayfs are present 0.479
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.315
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.345
When the network is plugged 0.113
And Tor is ready 19.982
Then the Upgrader considers the system as up-to-date 0.325
# 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.784
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.161
After features/support/hooks.rb:326 0.738
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
37.299
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.630
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.334
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the signing key used by the Upgrader is outdated 0.856
But a current signing key is available on our website 0.000
When the network is plugged 0.396
And Tor is ready 20.698
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.310
After features/support/hooks.rb:326 0.679
After features/support/hooks.rb:100 0.000