Project Number Date
test_Tails_ISO_devel 3422 09 Jun 2024, 12:34

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 18:43.940 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:59.091
Before features/support/hooks.rb:269 0.006
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 31.021
When I start Tails from USB drive "old" with network unplugged 1:23.018
Then the boot device has safe access rights 2.811
And Tails is running from USB drive "old" 0.302
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.113
And udev-watchdog is monitoring the correct device 0.300
And I unplug USB drive "old" 0.171
After features/support/hooks.rb:315 3.580
After features/support/hooks.rb:100 0.011
Tags: @product
2:12.482
Before features/support/hooks.rb:269 0.008
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login 1:27.318
Then Tails is running from USB drive "old" 0.315
And I create a persistent partition 33.623
And I take note of which tps features are available 1.620
Then a Tails persistence partition exists on USB drive "old" 0.804
And I shutdown Tails and wait for the computer to power off 8.597
After features/support/hooks.rb:315 0.187
After features/support/hooks.rb:100 0.009
Tags: @product
2:46.692
Before features/support/hooks.rb:269 0.005
Given a computer 0.223
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.062
Then Tails is running from USB drive "old" 0.383
And all tps features are active 1.813
When I write some files expected to persist 1.703
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.205
And all persistence configuration files have safe access rights 0.442
And all persistent directories from the old Tails version have safe access rights 2.382
And I take note of which tps features are available 0.523
And I shutdown Tails and wait for the computer to power off 4.584
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.367
After features/support/hooks.rb:315 0.097
After features/support/hooks.rb:100 0.012
Tags: @product
2:25.761
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.425
And I log in to a new session 17.904
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.773
And I plug USB drive "to_upgrade" 2.478
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.210
Then the running Tails is installed on USB drive "to_upgrade" 15.578
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.196
After features/support/hooks.rb:315 6.787
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.385
Before features/support/hooks.rb:269 0.006
Given a computer 0.221
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.618
Then all tps features from the old Tails version are active 1.631
And Tails is running from USB drive "to_upgrade" 0.359
And the boot device has safe access rights 3.174
And the expected persistent files created with the old Tails version are present in the filesystem 1.919
And all persistent directories from the old Tails version have safe access rights 2.461
After features/support/hooks.rb:315 0.726
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:35.622
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.290
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.260
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.245
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.443
When the network is plugged 0.043
And Tor is ready 17.762
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.607
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.262
Given I shutdown Tails and wait for the computer to power off 8.625
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.518
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.119
And the file system changes introduced in version 6.2~testoverlayfs are present 0.320
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.454
# 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.254
When the network is plugged 0.034
And Tor is ready 18.772
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.354
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.940
Given I shutdown Tails and wait for the computer to power off 4.380
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.903
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.931
And the file system changes introduced in version 6.3~testoverlayfs are present 0.485
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.328
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.240
When the network is plugged 0.045
And Tor is ready 19.492
Then the Upgrader considers the system as up-to-date 10.740
# 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 14.514
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.934
After features/support/hooks.rb:315 0.722
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
34.903
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.567
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.294
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 1.153
But a current signing key is available on our website 0.000
When the network is plugged 0.044
And Tor is ready 17.448
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.352
After features/support/hooks.rb:315 0.805
After features/support/hooks.rb:100 0.000