Project Number Date
test_Tails_ISO_closed-issues-design-doc 3 28 May 2026, 18:09

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 12:3.556 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:13.400
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.066
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 14.883
When I start Tails from USB drive "old" with network unplugged 53.170
Then the boot device has safe access rights 3.468
And Tails is running from USB drive "old" 0.291
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.234
And I unplug USB drive "old" 0.153
After features/support/hooks.rb:335 1.637
After features/support/hooks.rb:104 0.013
Tags: @product
1:34.978
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.008
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login 59.246
Then Tails is running from USB drive "old" 0.310
And I create a persistent partition 27.067
And I take note of which tps features are available 0.528
Then a Tails persistence partition exists on USB drive "old" 0.635
And I shutdown Tails and wait for the computer to power off 7.110
After features/support/hooks.rb:335 0.470
After features/support/hooks.rb:104 0.012
Tags: @product
1:28.678
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.094
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.851
Then Tails is running from USB drive "old" 0.305
And all tps features are active 1.346
When I write some files expected to persist 1.315
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.158
And all persistence configuration files have safe access rights 0.326
And all persistent directories from the old Tails version have safe access rights 2.099
And I take note of which tps features are available 0.175
And I shutdown Tails and wait for the computer to power off 4.128
# 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" 12.877
After features/support/hooks.rb:335 0.142
After features/support/hooks.rb:104 0.007
Tags: @product
2:15.924
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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.883
And I log in to a new session 13.896
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.951
And I plug USB drive "to_upgrade" 2.231
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.790
Then the running Tails is installed on USB drive "to_upgrade" 16.818
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.136
After features/support/hooks.rb:335 3.763
After features/support/hooks.rb:104 0.000
Tags: @product
1:15.655
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.058
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.027
Then all tps features from the old Tails version are active 1.597
And Tails is running from USB drive "to_upgrade" 0.296
And the boot device has safe access rights 2.936
And the expected persistent files created with the old Tails version are present in the filesystem 1.437
And all persistent directories from the old Tails version have safe access rights 2.300
After features/support/hooks.rb:335 0.649
After features/support/hooks.rb:104 0.008
Tags: @product @automatic_upgrade
3:53.548
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.678
And no SquashFS delta is installed 0.058
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.297
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.297
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.363
When the network is plugged 0.019
And Tor is ready 13.059
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.311
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.570
Given I shutdown Tails and wait for the computer to power off 10.025
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.539
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.644
And the file system changes introduced in version 6.2~testoverlayfs are present 0.248
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.163
# 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.018
And Tor is ready 10.486
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.443
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.666
Given I shutdown Tails and wait for the computer to power off 7.142
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.751
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.046
And the file system changes introduced in version 6.3~testoverlayfs are present 0.352
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.125
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.227
When the network is plugged 0.039
And Tor is ready 11.620
Then the Upgrader considers the system as up-to-date 10.622
# 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.803
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.531
After features/support/hooks.rb:335 0.931
After features/support/hooks.rb:104 0.011
Tags: @product @automatic_upgrade
21.369
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.741
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.242
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.064
But a current signing key is available on our website 0.000
When the network is plugged 0.022
And Tor is ready 10.271
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.975
After features/support/hooks.rb:335 0.908
After features/support/hooks.rb:104 0.000