Project Number Date
test_Tails_ISO_stable 6296 14 Apr 2026, 13:58

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:45.881 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:22.845
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given a computer 0.078
And I create a 7200 MiB disk named "old" 0.017
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 14.563
When I start Tails from USB drive "old" with network unplugged 1:3.192
Then the boot device has safe access rights 3.154
And Tails is running from USB drive "old" 0.319
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.043
And udev-watchdog is monitoring the correct device 0.232
And I unplug USB drive "old" 0.149
After features/support/hooks.rb:331 3.859
After features/support/hooks.rb:100 0.007
Tags: @product
1:32.242
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.061
And I start Tails from USB drive "old" with network unplugged and I login 57.477
Then Tails is running from USB drive "old" 0.268
And I create a persistent partition 24.427
And I take note of which tps features are available 0.749
Then a Tails persistence partition exists on USB drive "old" 0.614
And I shutdown Tails and wait for the computer to power off 8.642
After features/support/hooks.rb:331 0.628
After features/support/hooks.rb:100 0.006
Tags: @product
1:33.772
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.954
Then Tails is running from USB drive "old" 0.248
And all tps features are active 1.116
When I write some files expected to persist 1.332
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.175
And all persistence configuration files have safe access rights 0.463
And all persistent directories from the old Tails version have safe access rights 2.137
And I take note of which tps features are available 0.210
And I shutdown Tails and wait for the computer to power off 7.416
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.632
After features/support/hooks.rb:331 0.605
After features/support/hooks.rb:100 0.009
Tags: @product
2:21.967
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 without a persistent partition and stopped at Tails Greeter's login screen 8.822
And I log in to a new session 19.042
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.006
And I plug USB drive "to_upgrade" 2.299
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.222
Then the running Tails is installed on USB drive "to_upgrade" 18.168
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.196
After features/support/hooks.rb:331 5.236
After features/support/hooks.rb:100 0.000
Tags: @product
1:22.048
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.053
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:12.193
Then all tps features from the old Tails version are active 1.166
And Tails is running from USB drive "to_upgrade" 0.380
And the boot device has safe access rights 4.153
And the expected persistent files created with the old Tails version are present in the filesystem 1.438
And all persistent directories from the old Tails version have safe access rights 2.663
After features/support/hooks.rb:331 0.834
After features/support/hooks.rb:100 0.006
5:3.749
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.655
And no SquashFS delta is installed 0.108
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.293
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.285
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.366
When the network is plugged 0.015
And Tor is ready 26.084
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.449
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.477
Given I shutdown Tails and wait for the computer to power off 18.080
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.781
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.518
And the file system changes introduced in version 6.2~testoverlayfs are present 0.240
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.193
# 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.264
When the network is plugged 0.021
And Tor is ready 41.492
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.443
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.190
Given I shutdown Tails and wait for the computer to power off 12.529
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.325
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 1.424
And the file system changes introduced in version 6.3~testoverlayfs are present 0.458
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.194
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.240
When the network is plugged 0.016
And Tor is ready 22.028
Then the Upgrader considers the system as up-to-date 0.119
# 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.854
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.386
After features/support/hooks.rb:331 1.068
After features/support/hooks.rb:100 0.013
29.256
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.866
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.341
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.081
And the signing key used by the Upgrader is outdated 0.059
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 20.442
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.446
After features/support/hooks.rb:331 1.099
After features/support/hooks.rb:100 0.000