Project Number Date
test_Tails_ISO_devel 3833 24 May 2025, 13:15

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 20:14.985 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:20.680
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.650
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 31.983
When I start Tails from USB drive "old" with network unplugged 1:42.303
Then the boot device has safe access rights 3.348
And Tails is running from USB drive "old" 0.423
And there is no persistence partition on USB drive "old" 0.088
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.397
And I unplug USB drive "old" 0.272
After features/support/hooks.rb:330 3.768
After features/support/hooks.rb:100 0.008
Tags: @product
2:22.640
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login 1:35.894
Then Tails is running from USB drive "old" 0.330
And I create a persistent partition 33.774
And I take note of which tps features are available 2.533
Then a Tails persistence partition exists on USB drive "old" 1.016
And I shutdown Tails and wait for the computer to power off 8.888
After features/support/hooks.rb:330 0.167
After features/support/hooks.rb:100 0.010
Tags: @product
3:2.854
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.995
Then Tails is running from USB drive "old" 0.667
And all tps features are active 2.244
When I write some files expected to persist 1.952
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.252
And all persistence configuration files have safe access rights 0.501
And all persistent directories from the old Tails version have safe access rights 3.533
And I take note of which tps features are available 0.524
And I shutdown Tails and wait for the computer to power off 4.489
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.473
After features/support/hooks.rb:330 0.282
After features/support/hooks.rb:100 0.038
Tags: @product
2:37.442
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 11.111
And I log in to a new session 19.003
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.622
And I plug USB drive "to_upgrade" 2.433
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.977
Then the running Tails is installed on USB drive "to_upgrade" 27.726
And I unplug USB drive "to_upgrade" 0.364
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:330 4.075
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.564
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Given a computer 1.226
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.137
Then all tps features from the old Tails version are active 2.140
And Tails is running from USB drive "to_upgrade" 0.407
And the boot device has safe access rights 3.905
And the expected persistent files created with the old Tails version are present in the filesystem 1.705
And all persistent directories from the old Tails version have safe access rights 3.041
After features/support/hooks.rb:330 1.480
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:46.113
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 11.548
And no SquashFS delta is installed 0.224
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.320
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.116
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.433
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.652
When the network is plugged 0.128
And Tor is ready 19.170
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.826
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.929
Given I shutdown Tails and wait for the computer to power off 9.147
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.087
Then Tails is running version 6.2~testoverlayfs 0.048
And all tps features are active 2.227
And the file system changes introduced in version 6.2~testoverlayfs are present 0.316
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.295
# 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.367
When the network is plugged 0.080
And Tor is ready 19.232
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.628
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.105
Given I shutdown Tails and wait for the computer to power off 4.886
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.842
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.425
And the file system changes introduced in version 6.3~testoverlayfs are present 0.531
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.280
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.339
When the network is plugged 0.076
And Tor is ready 18.876
Then the Upgrader considers the system as up-to-date 0.325
# 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.829
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.654
After features/support/hooks.rb:330 0.789
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
37.689
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 10.675
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.413
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.139
But a current signing key is available on our website 0.000
When the network is plugged 0.101
And Tor is ready 21.005
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.295
After features/support/hooks.rb:330 1.331
After features/support/hooks.rb:100 0.000