Project Number Date
test_Tails_ISO_stable 6198 12 Mar 2026, 23: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 13:11.373 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:19.824
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.068
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.959
When I start Tails from USB drive "old" with network unplugged 59.941
Then the boot device has safe access rights 2.977
And Tails is running from USB drive "old" 0.283
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.280
And I unplug USB drive "old" 0.148
After features/support/hooks.rb:331 1.568
After features/support/hooks.rb:100 0.007
Tags: @product
1:33.589
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.066
And I start Tails from USB drive "old" with network unplugged and I login 57.397
Then Tails is running from USB drive "old" 0.280
And I create a persistent partition 25.880
And I take note of which tps features are available 0.781
Then a Tails persistence partition exists on USB drive "old" 0.625
And I shutdown Tails and wait for the computer to power off 8.559
After features/support/hooks.rb:331 0.363
After features/support/hooks.rb:100 0.009
Tags: @product
1:30.959
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.094
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.324
Then Tails is running from USB drive "old" 0.590
And all tps features are active 1.626
When I write some files expected to persist 1.504
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.227
And all persistence configuration files have safe access rights 0.475
And all persistent directories from the old Tails version have safe access rights 2.135
And I take note of which tps features are available 0.230
And I shutdown Tails and wait for the computer to power off 4.113
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.635
After features/support/hooks.rb:331 0.440
After features/support/hooks.rb:100 0.008
Tags: @product
2:16.733
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 without a persistent partition and stopped at Tails Greeter's login screen 9.052
And I log in to a new session 12.942
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.150
And I plug USB drive "to_upgrade" 2.304
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.549
Then the running Tails is installed on USB drive "to_upgrade" 17.449
And I unplug USB drive "to_upgrade" 0.147
And I unplug USB drive "__internal" 0.137
After features/support/hooks.rb:331 2.916
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.834
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.055
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.220
Then all tps features from the old Tails version are active 1.182
And Tails is running from USB drive "to_upgrade" 0.291
And the boot device has safe access rights 2.721
And the expected persistent files created with the old Tails version are present in the filesystem 1.082
And all persistent directories from the old Tails version have safe access rights 2.281
After features/support/hooks.rb:331 0.894
After features/support/hooks.rb:100 0.027
4:51.979
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 8.936
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.235
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.234
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.409
When the network is plugged 0.017
And Tor is ready 22.628
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.432
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.973
Given I shutdown Tails and wait for the computer to power off 19.580
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.902
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.200
And the file system changes introduced in version 6.2~testoverlayfs are present 0.246
And only the 6.2~testoverlayfs SquashFS delta is installed 0.040
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.165
# 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.190
When the network is plugged 0.013
And Tor is ready 21.631
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.397
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.534
Given I shutdown Tails and wait for the computer to power off 17.518
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.207
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.216
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.050
# 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.239
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.252
When the network is plugged 0.019
And Tor is ready 22.484
Then the Upgrader considers the system as up-to-date 0.124
# 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.955
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.494
After features/support/hooks.rb:331 1.076
After features/support/hooks.rb:100 0.028
26.451
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.004
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.229
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.039
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 17.717
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.384
After features/support/hooks.rb:331 0.782
After features/support/hooks.rb:100 0.000