Project Number Date
test_Tails_ISO_devel 4633 22 Sep 2026, 11:18

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:23.611 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:7.227
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.124
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 13.322
When I start Tails from USB drive "old" with network unplugged 50.246
Then the boot device has safe access rights 1.937
And Tails is running from USB drive "old" 0.191
And there is no persistence partition on USB drive "old" 0.029
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.140
And I unplug USB drive "old" 0.104
After features/support/hooks.rb:339 1.694
After features/support/hooks.rb:108 0.006
Tags: @product
1:21.179
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login 47.498
Then Tails is running from USB drive "old" 0.267
And I create a persistent partition 22.709
And I take note of which tps features are available 6.179
Then a Tails persistence partition exists on USB drive "old" 0.465
And I shutdown Tails and wait for the computer to power off 3.979
After features/support/hooks.rb:339 0.120
After features/support/hooks.rb:108 0.006
Tags: @product
1:33.100
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.622
Then Tails is running from USB drive "old" 0.233
And all tps features are active 7.724
When I write some files expected to persist 1.085
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.160
And all persistence configuration files have safe access rights 0.224
And all persistent directories from the old Tails version have safe access rights 1.719
And I take note of which tps features are available 5.785
And I shutdown Tails and wait for the computer to power off 3.786
# 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.669
After features/support/hooks.rb:339 0.246
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.713
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.229
And I log in to a new session 11.338
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.631
And I plug USB drive "to_upgrade" 2.242
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.957
Then the running Tails is installed on USB drive "to_upgrade" 18.088
And I unplug USB drive "to_upgrade" 0.112
And I unplug USB drive "__internal" 0.111
After features/support/hooks.rb:339 0.628
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.804
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.081
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.631
Then all tps features from the old Tails version are active 1.135
And Tails is running from USB drive "to_upgrade" 0.227
And the boot device has safe access rights 2.033
And the expected persistent files created with the old Tails version are present in the filesystem 0.947
And all persistent directories from the old Tails version have safe access rights 2.748
After features/support/hooks.rb:339 0.833
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:42.081
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.921
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.202
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.212
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.407
When the network is plugged 0.023
And Tor is ready 12.990
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.449
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.325
Given I shutdown Tails and wait for the computer to power off 5.497
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.965
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.233
And the file system changes introduced in version 6.2~testoverlayfs are present 0.256
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.108
# 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.176
When the network is plugged 0.032
And Tor is ready 10.628
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.880
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.516
Given I shutdown Tails and wait for the computer to power off 3.964
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.145
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 8.126
And the file system changes introduced in version 6.3~testoverlayfs are present 0.299
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.114
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.215
When the network is plugged 0.030
And Tor is ready 10.116
Then the Upgrader considers the system as up-to-date 10.375
# 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.314
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.313
After features/support/hooks.rb:339 0.741
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
20.504
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.771
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.246
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.038
But a current signing key is available on our website 0.000
When the network is plugged 0.026
And Tor is ready 11.471
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.896
After features/support/hooks.rb:339 0.694
After features/support/hooks.rb:108 0.000