Project Number Date
test_Tails_ISO_stable 6285 10 Apr 2026, 11:21

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:46.531 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.143
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.092
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 14.062
When I start Tails from USB drive "old" with network unplugged 50.317
Then the boot device has safe access rights 2.909
And Tails is running from USB drive "old" 0.252
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.229
And I unplug USB drive "old" 0.142
After features/support/hooks.rb:331 1.187
After features/support/hooks.rb:100 0.006
Tags: @product
1:31.218
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 "old" with network unplugged and I login 56.281
Then Tails is running from USB drive "old" 0.291
And I create a persistent partition 24.568
And I take note of which tps features are available 0.949
Then a Tails persistence partition exists on USB drive "old" 0.603
And I shutdown Tails and wait for the computer to power off 8.465
After features/support/hooks.rb:331 0.193
After features/support/hooks.rb:100 0.008
Tags: @product
1:28.326
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.774
Then Tails is running from USB drive "old" 0.260
And all tps features are active 1.166
When I write some files expected to persist 1.331
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.203
And all persistence configuration files have safe access rights 0.459
And all persistent directories from the old Tails version have safe access rights 2.145
And I take note of which tps features are available 0.274
And I shutdown Tails and wait for the computer to power off 7.109
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.519
After features/support/hooks.rb:331 0.511
After features/support/hooks.rb:100 0.007
Tags: @product
2:13.363
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 8.730
And I log in to a new session 12.622
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.783
And I plug USB drive "to_upgrade" 2.271
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.559
Then the running Tails is installed on USB drive "to_upgrade" 17.122
And I unplug USB drive "to_upgrade" 0.139
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:331 2.089
After features/support/hooks.rb:100 0.000
Tags: @product
1:13.339
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.062
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.085
Then all tps features from the old Tails version are active 1.263
And Tails is running from USB drive "to_upgrade" 0.318
And the boot device has safe access rights 2.820
And the expected persistent files created with the old Tails version are present in the filesystem 1.574
And all persistent directories from the old Tails version have safe access rights 2.213
After features/support/hooks.rb:331 0.896
After features/support/hooks.rb:100 0.041
Tags: @product @automatic_upgrade
4:44.762
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.390
And no SquashFS delta is installed 0.120
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.249
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.232
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.341
When the network is plugged 0.017
And Tor is ready 21.927
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.444
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.644
Given I shutdown Tails and wait for the computer to power off 19.559
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.702
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.307
And the file system changes introduced in version 6.2~testoverlayfs are present 0.255
And only the 6.2~testoverlayfs SquashFS delta is installed 0.053
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.154
# 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.195
When the network is plugged 0.017
And Tor is ready 21.740
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.407
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.380
Given I shutdown Tails and wait for the computer to power off 17.867
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.646
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 1.152
And the file system changes introduced in version 6.3~testoverlayfs are present 0.397
And only the 6.3~testoverlayfs SquashFS delta is installed 0.039
# 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.143
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.200
When the network is plugged 0.014
And Tor is ready 20.739
Then the Upgrader considers the system as up-to-date 0.109
# 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.753
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.470
After features/support/hooks.rb:331 0.709
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
26.377
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 7.993
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.271
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
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.018
And Tor is ready 17.576
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.403
After features/support/hooks.rb:331 0.898
After features/support/hooks.rb:100 0.000