Project Number Date
test_Tails_ISO_devel 3713 01 Mar 2025, 12:42

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:40.831 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:14.839
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.191
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 31.353
When I start Tails from USB drive "old" with network unplugged 1:37.887
Then the boot device has safe access rights 3.264
And Tails is running from USB drive "old" 0.344
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.341
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:330 8.941
After features/support/hooks.rb:100 0.008
Tags: @product
2:9.653
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login 1:24.783
Then Tails is running from USB drive "old" 0.362
And I create a persistent partition 32.467
And I take note of which tps features are available 2.300
Then a Tails persistence partition exists on USB drive "old" 0.872
And I shutdown Tails and wait for the computer to power off 8.680
After features/support/hooks.rb:330 0.315
After features/support/hooks.rb:100 0.013
Tags: @product
2:59.979
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given a computer 0.223
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.092
Then Tails is running from USB drive "old" 1.365
And all tps features are active 2.208
When I write some files expected to persist 3.589
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.264
And all persistence configuration files have safe access rights 0.379
And all persistent directories from the old Tails version have safe access rights 2.394
And I take note of which tps features are available 0.483
And I shutdown Tails and wait for the computer to power off 6.620
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.359
After features/support/hooks.rb:330 0.159
After features/support/hooks.rb:100 0.009
Tags: @product
2:28.262
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 9.752
And I log in to a new session 17.886
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.638
And I plug USB drive "to_upgrade" 2.389
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.387
Then the running Tails is installed on USB drive "to_upgrade" 21.801
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:330 2.444
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.130
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.605
Then all tps features from the old Tails version are active 1.683
And Tails is running from USB drive "to_upgrade" 0.345
And the boot device has safe access rights 3.252
And the expected persistent files created with the old Tails version are present in the filesystem 1.621
And all persistent directories from the old Tails version have safe access rights 2.434
After features/support/hooks.rb:330 1.280
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:54.628
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.792
And no SquashFS delta is installed 1.035
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.478
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.489
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.511
When the network is plugged 0.072
And Tor is ready 23.705
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.240
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.541
Given I shutdown Tails and wait for the computer to power off 10.813
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.936
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.367
And the file system changes introduced in version 6.2~testoverlayfs are present 0.375
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.284
# 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.293
When the network is plugged 0.098
And Tor is ready 18.877
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.552
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.722
Given I shutdown Tails and wait for the computer to power off 6.541
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.404
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.380
And the file system changes introduced in version 6.3~testoverlayfs are present 0.564
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.310
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.341
When the network is plugged 0.077
And Tor is ready 19.372
Then the Upgrader considers the system as up-to-date 0.337
# 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.757
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.116
After features/support/hooks.rb:330 0.710
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
38.336
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.169
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.433
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the signing key used by the Upgrader is outdated 0.086
But a current signing key is available on our website 0.000
When the network is plugged 0.063
And Tor is ready 19.175
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.334
After features/support/hooks.rb:330 0.760
After features/support/hooks.rb:100 0.000