Project Number Date
test_Tails_ISO_stable 5745 27 Jun 2025, 12:47

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:36.035 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:1.470
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.157
And I create a 7200 MiB disk named "old" 0.034
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 31.101
When I start Tails from USB drive "old" with network unplugged 1:25.023
Then the boot device has safe access rights 2.941
And Tails is running from USB drive "old" 0.347
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.118
And udev-watchdog is monitoring the correct device 0.397
And I unplug USB drive "old" 0.235
After features/support/hooks.rb:330 3.839
After features/support/hooks.rb:100 0.032
Tags: @product
2:8.244
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login 1:25.861
Then Tails is running from USB drive "old" 0.300
And I create a persistent partition 30.832
And I take note of which tps features are available 1.514
Then a Tails persistence partition exists on USB drive "old" 0.820
And I shutdown Tails and wait for the computer to power off 8.721
After features/support/hooks.rb:330 0.161
After features/support/hooks.rb:100 0.008
Tags: @product
2:56.295
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.255
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.890
Then Tails is running from USB drive "old" 0.456
And all tps features are active 1.981
When I write some files expected to persist 3.413
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.210
And all persistence configuration files have safe access rights 0.350
And all persistent directories from the old Tails version have safe access rights 2.346
And I take note of which tps features are available 0.408
And I shutdown Tails and wait for the computer to power off 6.578
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.404
After features/support/hooks.rb:330 0.176
After features/support/hooks.rb:100 0.008
Tags: @product
2:33.145
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 without a persistent partition and stopped at Tails Greeter's login screen 9.959
And I log in to a new session 18.268
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.793
And I plug USB drive "to_upgrade" 2.420
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.363
Then the running Tails is installed on USB drive "to_upgrade" 25.928
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.214
After features/support/hooks.rb:330 1.010
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.346
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.175
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.497
Then all tps features from the old Tails version are active 1.511
And Tails is running from USB drive "to_upgrade" 0.315
And the boot device has safe access rights 3.266
And the expected persistent files created with the old Tails version are present in the filesystem 1.495
And all persistent directories from the old Tails version have safe access rights 3.084
After features/support/hooks.rb:330 1.803
After features/support/hooks.rb:100 0.029
Tags: @product @automatic_upgrade
6:51.911
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.246
And no SquashFS delta is installed 0.280
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.409
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.293
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.700
When the network is plugged 0.061
And Tor is ready 24.845
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.251
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.748
Given I shutdown Tails and wait for the computer to power off 8.682
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.255
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 2.051
And the file system changes introduced in version 6.2~testoverlayfs are present 0.313
And only the 6.2~testoverlayfs SquashFS delta is installed 0.088
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.300
# 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.067
And Tor is ready 18.337
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.593
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.680
Given I shutdown Tails and wait for the computer to power off 4.257
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.514
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.988
And the file system changes introduced in version 6.3~testoverlayfs are present 0.555
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.301
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.258
When the network is plugged 0.060
And Tor is ready 19.707
Then the Upgrader considers the system as up-to-date 0.315
# 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.574
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.707
After features/support/hooks.rb:330 0.649
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
41.622
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 10.933
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.584
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.084
And the signing key used by the Upgrader is outdated 0.150
But a current signing key is available on our website 0.000
When the network is plugged 0.099
And Tor is ready 23.121
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.648
After features/support/hooks.rb:330 0.688
After features/support/hooks.rb:100 0.000