Project Number Date
test_Tails_ISO_stable 6221 22 Mar 2026, 11:25

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 14:14.448 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:25.512
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.056
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 15.192
When I start Tails from USB drive "old" with network unplugged 1:5.604
Then the boot device has safe access rights 2.874
And Tails is running from USB drive "old" 0.248
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.063
And udev-watchdog is monitoring the correct device 0.236
And I unplug USB drive "old" 0.145
After features/support/hooks.rb:331 3.877
After features/support/hooks.rb:100 0.009
Tags: @product
1:31.392
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login 57.072
Then Tails is running from USB drive "old" 0.263
And I create a persistent partition 25.498
And I take note of which tps features are available 0.878
Then a Tails persistence partition exists on USB drive "old" 0.616
And I shutdown Tails and wait for the computer to power off 6.974
After features/support/hooks.rb:331 0.534
After features/support/hooks.rb:100 0.007
Tags: @product
1:31.310
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.066
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.593
Then Tails is running from USB drive "old" 0.281
And all tps features are active 1.668
When I write some files expected to persist 1.733
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.221
And all persistence configuration files have safe access rights 0.516
And all persistent directories from the old Tails version have safe access rights 2.262
And I take note of which tps features are available 0.221
And I shutdown Tails and wait for the computer to power off 4.253
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.491
After features/support/hooks.rb:331 0.598
After features/support/hooks.rb:100 0.009
Tags: @product
2:21.138
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 9.179
And I log in to a new session 18.110
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.865
And I plug USB drive "to_upgrade" 2.245
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.007
Then the running Tails is installed on USB drive "to_upgrade" 17.378
And I unplug USB drive "to_upgrade" 0.169
And I unplug USB drive "__internal" 0.180
After features/support/hooks.rb:331 3.412
After features/support/hooks.rb:100 0.000
Tags: @product
1:19.639
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.097
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:11.476
Then all tps features from the old Tails version are active 1.321
And Tails is running from USB drive "to_upgrade" 0.312
And the boot device has safe access rights 2.871
And the expected persistent files created with the old Tails version are present in the filesystem 1.272
And all persistent directories from the old Tails version have safe access rights 2.288
After features/support/hooks.rb:331 0.699
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
5:15.092
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.787
And no SquashFS delta is installed 0.118
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.323
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.236
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.336
When the network is plugged 0.019
And Tor is ready 44.364
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.452
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.424
Given I shutdown Tails and wait for the computer to power off 20.980
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.593
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.316
And the file system changes introduced in version 6.2~testoverlayfs are present 0.258
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.149
# 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.199
When the network is plugged 0.016
And Tor is ready 23.970
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.420
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.609
Given I shutdown Tails and wait for the computer to power off 18.050
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.894
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.358
And the file system changes introduced in version 6.3~testoverlayfs are present 0.432
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.169
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.222
When the network is plugged 0.020
And Tor is ready 21.669
Then the Upgrader considers the system as up-to-date 0.104
# 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.932
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.504
After features/support/hooks.rb:331 1.021
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
50.362
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.318
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.276
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.046
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 41.247
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.401
After features/support/hooks.rb:331 0.881
After features/support/hooks.rb:100 0.000