Project Number Date
test_Tails_ISO_stable 4740 26 Mar 2024, 04:29

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:43.374 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:34.231
Before features/support/hooks.rb:245 0.005
Given a computer 0.234
And I create a 7200 MiB disk named "old" 0.080
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 19.313
When I start Tails from USB drive "old" with network unplugged 1:9.287
Then the boot device has safe access rights 3.242
And Tails is running from USB drive "old" 0.361
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.292
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:291 3.719
After features/support/hooks.rb:75 0.012
Tags: @product
2:0.822
Before features/support/hooks.rb:245 0.007
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login 1:17.181
Then Tails is running from USB drive "old" 0.308
And I create a persistent partition 33.532
And I take note of which tps features are available 1.646
Then a Tails persistence partition exists on USB drive "old" 0.813
And I shutdown Tails and wait for the computer to power off 7.126
After features/support/hooks.rb:291 0.157
After features/support/hooks.rb:75 0.009
Tags: @product
2:35.691
Before features/support/hooks.rb:245 0.006
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:7.483
Then Tails is running from USB drive "old" 0.321
And all tps features are active 1.954
When I write some files expected to persist 1.657
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.218
And all persistence configuration files have safe access rights 0.396
And all persistent directories from the old Tails version have safe access rights 2.839
And I take note of which tps features are available 0.432
And I shutdown Tails and wait for the computer to power off 4.018
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.179
After features/support/hooks.rb:291 0.117
After features/support/hooks.rb:75 0.009
Tags: @product
2:21.628
Before features/support/hooks.rb:245 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.857
And I log in to a new session 15.805
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.781
And I plug USB drive "to_upgrade" 2.523
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.593
Then the running Tails is installed on USB drive "to_upgrade" 13.598
And I unplug USB drive "to_upgrade" 0.229
And I unplug USB drive "__internal" 0.239
After features/support/hooks.rb:291 4.001
After features/support/hooks.rb:75 0.000
Tags: @product
2:6.096
Before features/support/hooks.rb:245 0.007
Given a computer 0.313
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:56.045
Then all tps features from the old Tails version are active 2.167
And Tails is running from USB drive "to_upgrade" 0.339
And the boot device has safe access rights 3.076
And the expected persistent files created with the old Tails version are present in the filesystem 1.821
And all persistent directories from the old Tails version have safe access rights 2.332
After features/support/hooks.rb:291 0.855
After features/support/hooks.rb:75 0.012
Tags: @product @automatic_upgrade
6:33.000
Before features/support/hooks.rb:245 0.013
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.486
And no SquashFS delta is installed 0.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.357
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.266
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.461
When the network is plugged 0.035
And Tor is ready 18.739
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.968
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.680
Given I shutdown Tails and wait for the computer to power off 6.140
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.263
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.007
And the file system changes introduced in version 6.2~testoverlayfs are present 0.286
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.302
# 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.280
When the network is plugged 0.057
And Tor is ready 47.199
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.603
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.818
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:54.945
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 1.814
And the file system changes introduced in version 6.3~testoverlayfs are present 0.470
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.320
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.279
When the network is plugged 0.032
And Tor is ready 15.785
Then the Upgrader considers the system as up-to-date 0.253
# 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 15.795
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.034
After features/support/hooks.rb:291 0.879
After features/support/hooks.rb:75 0.040
Tags: @product @automatic_upgrade
31.905
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.821
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.362
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.507
But a current signing key is available on our website 0.000
When the network is plugged 0.108
And Tor is ready 12.981
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.067
After features/support/hooks.rb:291 0.936
After features/support/hooks.rb:75 0.000