Project Number Date
test_Tails_ISO_stable 5932 05 Nov 2025, 12: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 16:24.124 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:59.823
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.176
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 30.818
When I start Tails from USB drive "old" with network unplugged 1:24.056
Then the boot device has safe access rights 2.842
And Tails is running from USB drive "old" 0.294
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.066
And udev-watchdog is monitoring the correct device 0.214
And I unplug USB drive "old" 0.168
After features/support/hooks.rb:331 4.164
After features/support/hooks.rb:100 0.008
Tags: @product
2:7.047
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login 1:27.915
Then Tails is running from USB drive "old" 0.320
And I create a persistent partition 29.235
And I take note of which tps features are available 1.136
Then a Tails persistence partition exists on USB drive "old" 0.713
And I shutdown Tails and wait for the computer to power off 7.549
After features/support/hooks.rb:331 0.477
After features/support/hooks.rb:100 0.011
Tags: @product
2:11.898
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:37.876
Then Tails is running from USB drive "old" 0.275
And all tps features are active 1.815
When I write some files expected to persist 1.479
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.266
And all persistence configuration files have safe access rights 0.388
And all persistent directories from the old Tails version have safe access rights 2.480
And I take note of which tps features are available 0.531
And I shutdown Tails and wait for the computer to power off 7.874
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.710
After features/support/hooks.rb:331 0.572
After features/support/hooks.rb:100 0.018
Tags: @product
2:50.786
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.160
And I log in to a new session 16.954
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.248
And I plug USB drive "to_upgrade" 2.576
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:55.871
Then the running Tails is installed on USB drive "to_upgrade" 20.560
And I unplug USB drive "to_upgrade" 0.184
And I unplug USB drive "__internal" 0.231
After features/support/hooks.rb:331 3.796
After features/support/hooks.rb:100 0.000
Tags: @product
1:48.918
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.223
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:40.291
Then all tps features from the old Tails version are active 1.457
And Tails is running from USB drive "to_upgrade" 0.324
And the boot device has safe access rights 3.039
And the expected persistent files created with the old Tails version are present in the filesystem 1.324
And all persistent directories from the old Tails version have safe access rights 2.257
After features/support/hooks.rb:331 1.067
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
5:1.965
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.110
And no SquashFS delta is installed 0.090
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.364
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.311
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.472
When the network is plugged 0.065
And Tor is ready 13.753
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.825
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.515
Given I shutdown Tails and wait for the computer to power off 11.128
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:40.870
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.305
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.057
# 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.285
When the network is plugged 0.076
And Tor is ready 13.081
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.843
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.176
Given I shutdown Tails and wait for the computer to power off 7.639
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:40.598
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.043
And the file system changes introduced in version 6.3~testoverlayfs are present 0.498
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.195
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.285
When the network is plugged 0.056
And Tor is ready 10.798
Then the Upgrader considers the system as up-to-date 0.216
# 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 5.229
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.521
After features/support/hooks.rb:331 1.232
After features/support/hooks.rb:100 0.038
Tags: @product @automatic_upgrade
23.684
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.283
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.074
But a current signing key is available on our website 0.000
When the network is plugged 0.051
And Tor is ready 11.409
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.723
After features/support/hooks.rb:331 1.140
After features/support/hooks.rb:100 0.000