Project Number Date
test_Tails_ISO_stable 4993 02 Aug 2024, 08:40

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:49.323 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:17.246
Before features/support/hooks.rb:269 0.005
Given a computer 0.225
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 30.060
When I start Tails from USB drive "old" with network unplugged 1:41.387
Then the boot device has safe access rights 3.293
And Tails is running from USB drive "old" 0.443
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.141
And udev-watchdog is monitoring the correct device 0.323
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:326 3.567
After features/support/hooks.rb:100 0.024
Tags: @product
2:9.740
Before features/support/hooks.rb:269 0.006
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login 1:25.664
Then Tails is running from USB drive "old" 0.372
And I create a persistent partition 32.521
And I take note of which tps features are available 1.564
Then a Tails persistence partition exists on USB drive "old" 0.803
And I shutdown Tails and wait for the computer to power off 8.604
After features/support/hooks.rb:326 0.210
After features/support/hooks.rb:100 0.009
Tags: @product
2:51.292
Before features/support/hooks.rb:269 0.005
Given a computer 0.252
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.634
Then Tails is running from USB drive "old" 0.347
And all tps features are active 2.337
When I write some files expected to persist 1.966
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.262
And all persistence configuration files have safe access rights 0.445
And all persistent directories from the old Tails version have safe access rights 2.820
And I take note of which tps features are available 0.429
And I shutdown Tails and wait for the computer to power off 4.395
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.402
After features/support/hooks.rb:326 0.111
After features/support/hooks.rb:100 0.011
Tags: @product
2:33.588
Before features/support/hooks.rb:269 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 11.797
And I log in to a new session 21.545
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.426
And I plug USB drive "to_upgrade" 2.434
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.776
Then the running Tails is installed on USB drive "to_upgrade" 22.214
And I unplug USB drive "to_upgrade" 0.190
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:326 2.054
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.007
Before features/support/hooks.rb:269 0.007
Given a computer 0.217
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.031
Then all tps features from the old Tails version are active 1.834
And Tails is running from USB drive "to_upgrade" 0.396
And the boot device has safe access rights 4.075
And the expected persistent files created with the old Tails version are present in the filesystem 1.633
And all persistent directories from the old Tails version have safe access rights 2.817
After features/support/hooks.rb:326 0.803
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:54.032
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.968
And no SquashFS delta is installed 0.107
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.378
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.325
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.504
When the network is plugged 0.041
And Tor is ready 24.565
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.573
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.330
Given I shutdown Tails and wait for the computer to power off 11.384
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.847
Then Tails is running version 6.2~testoverlayfs 0.024
And all tps features are active 6.466
And the file system changes introduced in version 6.2~testoverlayfs are present 0.424
And only the 6.2~testoverlayfs SquashFS delta is installed 0.092
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.372
# 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.463
When the network is plugged 0.050
And Tor is ready 17.799
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.544
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.385
Given I shutdown Tails and wait for the computer to power off 6.787
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.240
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.237
And the file system changes introduced in version 6.3~testoverlayfs are present 0.574
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.375
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.264
When the network is plugged 0.047
And Tor is ready 19.679
Then the Upgrader considers the system as up-to-date 10.836
# 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 16.287
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.899
After features/support/hooks.rb:326 0.742
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
39.415
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 11.695
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.355
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.276
And the signing key used by the Upgrader is outdated 0.840
But a current signing key is available on our website 0.000
When the network is plugged 0.162
And Tor is ready 19.373
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.712
After features/support/hooks.rb:326 0.953
After features/support/hooks.rb:100 0.000