Project Number Date
test_Tails_ISO_web-release-6.15.1 4 20 May 2025, 21:32

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:56.351 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:19.479
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.212
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.065
And I write an old version of the Tails USB image to disk "old" 32.028
When I start Tails from USB drive "old" with network unplugged 1:41.900
Then the boot device has safe access rights 3.082
And Tails is running from USB drive "old" 0.341
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.123
And udev-watchdog is monitoring the correct device 0.401
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:330 7.011
After features/support/hooks.rb:100 0.011
Tags: @product
2:12.153
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.215
And I start Tails from USB drive "old" with network unplugged and I login 1:29.891
Then Tails is running from USB drive "old" 0.364
And I create a persistent partition 31.720
And I take note of which tps features are available 2.532
Then a Tails persistence partition exists on USB drive "old" 0.839
And I shutdown Tails and wait for the computer to power off 6.589
After features/support/hooks.rb:330 0.171
After features/support/hooks.rb:100 0.009
Tags: @product
2:57.445
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.007
Then Tails is running from USB drive "old" 0.506
And all tps features are active 2.812
When I write some files expected to persist 1.800
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.249
And all persistence configuration files have safe access rights 0.444
And all persistent directories from the old Tails version have safe access rights 2.846
And I take note of which tps features are available 0.482
And I shutdown Tails and wait for the computer to power off 4.432
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.661
After features/support/hooks.rb:330 0.171
After features/support/hooks.rb:100 0.008
Tags: @product
2:39.542
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.446
And I log in to a new session 20.278
And I clone USB drive "old" to a new USB drive "to_upgrade" 3.551
And I plug USB drive "to_upgrade" 2.462
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.189
Then the running Tails is installed on USB drive "to_upgrade" 25.174
And I unplug USB drive "to_upgrade" 0.218
And I unplug USB drive "__internal" 0.220
After features/support/hooks.rb:330 2.738
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.138
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.220
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.730
Then all tps features from the old Tails version are active 1.730
And Tails is running from USB drive "to_upgrade" 0.366
And the boot device has safe access rights 3.740
And the expected persistent files created with the old Tails version are present in the filesystem 1.549
And all persistent directories from the old Tails version have safe access rights 2.800
After features/support/hooks.rb:330 1.548
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:48.284
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 13.057
And no SquashFS delta is installed 0.263
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.439
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.139
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.345
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.617
When the network is plugged 0.075
And Tor is ready 23.978
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.296
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.084
Given I shutdown Tails and wait for the computer to power off 9.026
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.533
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.237
And the file system changes introduced in version 6.2~testoverlayfs are present 0.327
And only the 6.2~testoverlayfs SquashFS delta is installed 0.089
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.400
# 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.402
When the network is plugged 0.083
And Tor is ready 17.117
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.223
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.674
Given I shutdown Tails and wait for the computer to power off 6.507
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.940
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.147
And the file system changes introduced in version 6.3~testoverlayfs are present 0.489
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.311
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.273
When the network is plugged 0.075
And Tor is ready 16.129
Then the Upgrader considers the system as up-to-date 0.331
# 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.098
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.467
After features/support/hooks.rb:330 0.842
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
42.307
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.376
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.479
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.069
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 19.868
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.371
After features/support/hooks.rb:330 1.244
After features/support/hooks.rb:100 0.000