Project Number Date
test_Tails_ISO_stable 6611 27 Aug 2026, 11:36

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:29.126 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.587
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.105
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.502
When I start Tails from USB drive "old" with network unplugged 51.269
Then the boot device has safe access rights 1.959
And Tails is running from USB drive "old" 0.218
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.064
And udev-watchdog is monitoring the correct device 0.178
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:339 1.694
After features/support/hooks.rb:108 0.005
Tags: @product
1:21.266
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login 47.712
Then Tails is running from USB drive "old" 0.261
And I create a persistent partition 22.354
And I take note of which tps features are available 6.223
Then a Tails persistence partition exists on USB drive "old" 0.521
And I shutdown Tails and wait for the computer to power off 4.109
After features/support/hooks.rb:339 0.581
After features/support/hooks.rb:108 0.005
Tags: @product
1:34.745
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.092
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.317
Then Tails is running from USB drive "old" 0.187
And all tps features are active 7.622
When I write some files expected to persist 1.144
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.125
And all persistence configuration files have safe access rights 0.280
And all persistent directories from the old Tails version have safe access rights 1.724
And I take note of which tps features are available 5.783
And I shutdown Tails and wait for the computer to power off 5.151
# 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.314
After features/support/hooks.rb:339 0.540
After features/support/hooks.rb:108 0.005
Tags: @product
2:12.480
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.105
And I log in to a new session 11.763
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.617
And I plug USB drive "to_upgrade" 2.179
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.012
Then the running Tails is installed on USB drive "to_upgrade" 18.520
And I unplug USB drive "to_upgrade" 0.124
And I unplug USB drive "__internal" 0.156
After features/support/hooks.rb:339 1.706
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.376
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.096
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.387
Then all tps features from the old Tails version are active 1.074
And Tails is running from USB drive "to_upgrade" 0.220
And the boot device has safe access rights 2.570
And the expected persistent files created with the old Tails version are present in the filesystem 1.205
And all persistent directories from the old Tails version have safe access rights 1.821
After features/support/hooks.rb:339 0.792
After features/support/hooks.rb:108 0.023
Tags: @product @automatic_upgrade
3:42.489
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 21.591
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.197
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.232
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.385
When the network is plugged 0.037
And Tor is ready 11.896
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.637
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.407
Given I shutdown Tails and wait for the computer to power off 5.258
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.513
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.492
And the file system changes introduced in version 6.2~testoverlayfs are present 0.190
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.102
# 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.159
When the network is plugged 0.038
And Tor is ready 10.216
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.661
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.365
Given I shutdown Tails and wait for the computer to power off 4.018
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.378
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 8.226
And the file system changes introduced in version 6.3~testoverlayfs are present 0.332
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.089
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.191
When the network is plugged 0.025
And Tor is ready 11.035
Then the Upgrader considers the system as up-to-date 0.097
# 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 4.109
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.370
After features/support/hooks.rb:339 0.902
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
19.181
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.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.238
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.033
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.029
And Tor is ready 8.611
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.153
After features/support/hooks.rb:339 0.942
After features/support/hooks.rb:108 0.000