Project Number Date
test_Tails_ISO_stable 6686 21 Sep 2026, 18:23

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:31.915 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:9.739
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.087
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.034
And I write an old version of the Tails USB image to disk "old" 13.588
When I start Tails from USB drive "old" with network unplugged 52.179
Then the boot device has safe access rights 2.222
And Tails is running from USB drive "old" 0.202
And there is no persistence partition on USB drive "old" 0.055
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.168
And I unplug USB drive "old" 0.121
After features/support/hooks.rb:339 1.296
After features/support/hooks.rb:108 0.018
Tags: @product
1:24.610
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login 49.038
Then Tails is running from USB drive "old" 0.210
And I create a persistent partition 23.852
And I take note of which tps features are available 6.741
Then a Tails persistence partition exists on USB drive "old" 0.640
And I shutdown Tails and wait for the computer to power off 4.038
After features/support/hooks.rb:339 0.225
After features/support/hooks.rb:108 0.006
Tags: @product
1:35.587
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.110
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.269
Then Tails is running from USB drive "old" 0.199
And all tps features are active 7.660
When I write some files expected to persist 1.105
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.192
And all persistence configuration files have safe access rights 0.287
And all persistent directories from the old Tails version have safe access rights 1.856
And I take note of which tps features are available 6.160
And I shutdown Tails and wait for the computer to power off 4.049
# 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.697
After features/support/hooks.rb:339 0.220
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.754
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.217
And I log in to a new session 11.260
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.757
And I plug USB drive "to_upgrade" 2.203
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.545
Then the running Tails is installed on USB drive "to_upgrade" 18.482
And I unplug USB drive "to_upgrade" 0.163
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:339 1.724
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.191
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.098
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.334
Then all tps features from the old Tails version are active 0.999
And Tails is running from USB drive "to_upgrade" 0.210
And the boot device has safe access rights 2.086
And the expected persistent files created with the old Tails version are present in the filesystem 0.919
And all persistent directories from the old Tails version have safe access rights 1.542
After features/support/hooks.rb:339 0.515
After features/support/hooks.rb:108 0.005
3:40.961
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 21.415
And no SquashFS delta is installed 0.061
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.232
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.211
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.376
When the network is plugged 0.026
And Tor is ready 11.196
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.226
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.848
Given I shutdown Tails and wait for the computer to power off 5.410
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.863
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.677
And the file system changes introduced in version 6.2~testoverlayfs are present 0.204
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.081
# 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.192
When the network is plugged 0.026
And Tor is ready 10.463
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.333
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.562
Given I shutdown Tails and wait for the computer to power off 3.852
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.255
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.833
And the file system changes introduced in version 6.3~testoverlayfs are present 0.630
And only the 6.3~testoverlayfs SquashFS delta is installed 0.040
# 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.099
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.197
When the network is plugged 0.033
And Tor is ready 10.461
Then the Upgrader considers the system as up-to-date 0.113
# 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.554
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.380
After features/support/hooks.rb:339 0.852
After features/support/hooks.rb:108 0.011
19.069
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 7.891
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.166
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.044
And Tor is ready 9.347
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.517
After features/support/hooks.rb:339 0.653
After features/support/hooks.rb:108 0.000