Project Number Date
test_Tails_ISO_stable 6574 12 Aug 2026, 07:27

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:19.164 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
58.614
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.079
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 13.356
When I start Tails from USB drive "old" with network unplugged 41.642
Then the boot device has safe access rights 1.907
And Tails is running from USB drive "old" 0.233
And there is no persistence partition on USB drive "old" 0.036
And process "udev-watchdog" is running 0.027
And udev-watchdog is monitoring the correct device 0.140
And I unplug USB drive "old" 0.111
After features/support/hooks.rb:339 3.420
After features/support/hooks.rb:108 0.005
Tags: @product
1:23.743
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login 49.126
Then Tails is running from USB drive "old" 0.236
And I create a persistent partition 23.139
And I take note of which tps features are available 6.468
Then a Tails persistence partition exists on USB drive "old" 0.666
And I shutdown Tails and wait for the computer to power off 4.014
After features/support/hooks.rb:339 0.172
After features/support/hooks.rb:108 0.009
Tags: @product
1:35.723
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.006
Given a computer 0.114
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.156
Then Tails is running from USB drive "old" 0.255
And all tps features are active 7.532
When I write some files expected to persist 1.181
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.183
And all persistence configuration files have safe access rights 0.264
And all persistent directories from the old Tails version have safe access rights 1.582
And I take note of which tps features are available 6.191
And I shutdown Tails and wait for the computer to power off 4.044
# 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.216
After features/support/hooks.rb:339 0.092
After features/support/hooks.rb:108 0.005
Tags: @product
2:12.083
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.464
And I log in to a new session 11.415
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.699
And I plug USB drive "to_upgrade" 2.198
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.720
Then the running Tails is installed on USB drive "to_upgrade" 18.327
And I unplug USB drive "to_upgrade" 0.121
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:339 1.664
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.258
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.094
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.034
Then all tps features from the old Tails version are active 0.995
And Tails is running from USB drive "to_upgrade" 0.216
And the boot device has safe access rights 1.850
And the expected persistent files created with the old Tails version are present in the filesystem 1.242
And all persistent directories from the old Tails version have safe access rights 1.824
After features/support/hooks.rb:339 0.456
After features/support/hooks.rb:108 0.017
Tags: @product @automatic_upgrade
3:42.304
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.543
And no SquashFS delta is installed 0.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.181
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.215
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.317
When the network is plugged 0.033
And Tor is ready 12.194
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.560
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.187
Given I shutdown Tails and wait for the computer to power off 5.248
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.301
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 8.059
And the file system changes introduced in version 6.2~testoverlayfs are present 0.175
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.101
# 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.157
When the network is plugged 0.036
And Tor is ready 10.476
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.031
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.811
Given I shutdown Tails and wait for the computer to power off 4.236
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.046
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.723
And the file system changes introduced in version 6.3~testoverlayfs are present 0.391
And only the 6.3~testoverlayfs SquashFS delta is installed 0.057
# 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.150
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.287
When the network is plugged 0.023
And Tor is ready 10.285
Then the Upgrader considers the system as up-to-date 10.403
# 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.564
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.318
After features/support/hooks.rb:339 0.953
After features/support/hooks.rb:108 0.008
Tags: @product @automatic_upgrade
19.438
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 7.881
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.186
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the signing key used by the Upgrader is outdated 0.070
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 8.920
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.314
After features/support/hooks.rb:339 0.770
After features/support/hooks.rb:108 0.000