Project Number Date
test_Tails_ISO_devel 4532 05 Aug 2026, 23:01

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 11:37.512 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:8.323
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.099
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 14.140
When I start Tails from USB drive "old" with network unplugged 50.199
Then the boot device has safe access rights 2.221
And Tails is running from USB drive "old" 0.244
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.044
And udev-watchdog is monitoring the correct device 0.169
And I unplug USB drive "old" 0.111
After features/support/hooks.rb:339 1.087
After features/support/hooks.rb:108 0.005
Tags: @product
1:22.476
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login 48.263
Then Tails is running from USB drive "old" 0.208
And I create a persistent partition 23.612
And I take note of which tps features are available 7.059
Then a Tails persistence partition exists on USB drive "old" 0.557
And I shutdown Tails and wait for the computer to power off 2.694
After features/support/hooks.rb:339 0.353
After features/support/hooks.rb:108 0.006
Tags: @product
1:37.870
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.706
Then Tails is running from USB drive "old" 0.202
And all tps features are active 7.893
When I write some files expected to persist 1.153
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.185
And all persistence configuration files have safe access rights 0.281
And all persistent directories from the old Tails version have safe access rights 1.765
And I take note of which tps features are available 6.181
And I shutdown Tails and wait for the computer to power off 4.014
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 11.410
After features/support/hooks.rb:339 0.488
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.636
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.455
And I log in to a new session 11.817
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.749
And I plug USB drive "to_upgrade" 2.228
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.351
Then the running Tails is installed on USB drive "to_upgrade" 18.767
And I unplug USB drive "to_upgrade" 0.146
And I unplug USB drive "__internal" 0.119
After features/support/hooks.rb:339 0.683
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.598
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.893
Then all tps features from the old Tails version are active 1.091
And Tails is running from USB drive "to_upgrade" 0.202
And the boot device has safe access rights 2.220
And the expected persistent files created with the old Tails version are present in the filesystem 0.850
And all persistent directories from the old Tails version have safe access rights 2.260
After features/support/hooks.rb:339 0.585
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:44.687
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.396
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.177
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.189
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.290
When the network is plugged 0.033
And Tor is ready 12.731
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.549
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.146
Given I shutdown Tails and wait for the computer to power off 5.320
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.794
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.425
And the file system changes introduced in version 6.2~testoverlayfs are present 0.172
And only the 6.2~testoverlayfs SquashFS delta is installed 0.039
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.086
# 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.160
When the network is plugged 0.035
And Tor is ready 11.410
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.308
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.919
Given I shutdown Tails and wait for the computer to power off 3.989
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.306
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.254
And the file system changes introduced in version 6.3~testoverlayfs are present 0.252
And only the 6.3~testoverlayfs SquashFS delta is installed 0.035
# 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.101
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.172
When the network is plugged 0.022
And Tor is ready 10.233
Then the Upgrader considers the system as up-to-date 10.434
# 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 3.163
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.406
After features/support/hooks.rb:339 0.740
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
19.920
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.056
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.219
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.041
And Tor is ready 11.180
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.308
After features/support/hooks.rb:339 0.791
After features/support/hooks.rb:108 0.000