Project Number Date
test_Tails_ISO_stable 6308 19 Apr 2026, 11:39

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 13:48.078 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:16.644
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.055
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 14.414
When I start Tails from USB drive "old" with network unplugged 57.397
Then the boot device has safe access rights 2.884
And Tails is running from USB drive "old" 0.245
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.374
And I unplug USB drive "old" 0.137
After features/support/hooks.rb:331 3.544
After features/support/hooks.rb:100 0.006
Tags: @product
1:28.488
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login 56.901
Then Tails is running from USB drive "old" 0.274
And I create a persistent partition 25.491
And I take note of which tps features are available 0.791
Then a Tails persistence partition exists on USB drive "old" 0.545
And I shutdown Tails and wait for the computer to power off 4.427
After features/support/hooks.rb:331 0.395
After features/support/hooks.rb:100 0.006
Tags: @product
1:26.502
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.350
Then Tails is running from USB drive "old" 0.299
And all tps features are active 1.353
When I write some files expected to persist 1.391
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.180
And all persistence configuration files have safe access rights 0.500
And all persistent directories from the old Tails version have safe access rights 1.920
And I take note of which tps features are available 0.155
And I shutdown Tails and wait for the computer to power off 4.278
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.021
After features/support/hooks.rb:331 0.342
After features/support/hooks.rb:100 0.006
Tags: @product
2:17.733
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 7.745
And I log in to a new session 16.013
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.813
And I plug USB drive "to_upgrade" 2.242
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.041
Then the running Tails is installed on USB drive "to_upgrade" 18.566
And I unplug USB drive "to_upgrade" 0.162
And I unplug USB drive "__internal" 0.148
After features/support/hooks.rb:331 3.275
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.303
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.059
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.733
Then all tps features from the old Tails version are active 1.047
And Tails is running from USB drive "to_upgrade" 0.341
And the boot device has safe access rights 2.595
And the expected persistent files created with the old Tails version are present in the filesystem 1.310
And all persistent directories from the old Tails version have safe access rights 2.214
After features/support/hooks.rb:331 1.072
After features/support/hooks.rb:100 0.007
5:39.038
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.650
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.251
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.234
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.361
When the network is plugged 0.017
And Tor is ready 44.880
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.405
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.475
Given I shutdown Tails and wait for the computer to power off 15.297
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.058
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.197
And the file system changes introduced in version 6.2~testoverlayfs are present 0.216
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.172
# 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.223
When the network is plugged 0.014
And Tor is ready 39.989
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.384
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.795
Given I shutdown Tails and wait for the computer to power off 17.426
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.067
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.183
And the file system changes introduced in version 6.3~testoverlayfs are present 0.398
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.147
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.200
When the network is plugged 0.017
And Tor is ready 40.062
Then the Upgrader considers the system as up-to-date 0.114
# 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.971
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.543
After features/support/hooks.rb:331 1.028
After features/support/hooks.rb:100 0.052
27.367
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 with a persistent partition enabled and logged in 7.899
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.237
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.034
And the signing key used by the Upgrader is outdated 0.055
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 18.745
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.376
After features/support/hooks.rb:331 0.886
After features/support/hooks.rb:100 0.000