Project Number Date
test_Tails_ISO_stable 6580 14 Aug 2026, 11:34

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 11:26.880 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:11.541
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.117
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.073
When I start Tails from USB drive "old" with network unplugged 53.832
Then the boot device has safe access rights 1.873
And Tails is running from USB drive "old" 0.237
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.042
And udev-watchdog is monitoring the correct device 0.160
And I unplug USB drive "old" 0.124
After features/support/hooks.rb:339 3.572
After features/support/hooks.rb:108 0.005
Tags: @product
1:21.302
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.089
And I start Tails from USB drive "old" with network unplugged and I login 47.804
Then Tails is running from USB drive "old" 0.213
And I create a persistent partition 23.419
And I take note of which tps features are available 6.642
Then a Tails persistence partition exists on USB drive "old" 0.515
And I shutdown Tails and wait for the computer to power off 2.616
After features/support/hooks.rb:339 0.560
After features/support/hooks.rb:108 0.005
Tags: @product
1:33.626
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.056
Then Tails is running from USB drive "old" 0.224
And all tps features are active 6.766
When I write some files expected to persist 1.270
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.118
And all persistence configuration files have safe access rights 0.243
And all persistent directories from the old Tails version have safe access rights 1.646
And I take note of which tps features are available 6.070
And I shutdown Tails and wait for the computer to power off 5.378
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 11.772
After features/support/hooks.rb:339 0.192
After features/support/hooks.rb:108 0.006
Tags: @product
2:25.110
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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 21.813
And I log in to a new session 11.116
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.648
And I plug USB drive "to_upgrade" 2.207
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.918
Then the running Tails is installed on USB drive "to_upgrade" 18.176
And I unplug USB drive "to_upgrade" 0.118
And I unplug USB drive "__internal" 0.111
After features/support/hooks.rb:339 1.498
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.963
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.076
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.911
Then all tps features from the old Tails version are active 1.009
And Tails is running from USB drive "to_upgrade" 0.215
And the boot device has safe access rights 2.116
And the expected persistent files created with the old Tails version are present in the filesystem 1.016
And all persistent directories from the old Tails version have safe access rights 1.616
After features/support/hooks.rb:339 0.661
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:30.664
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.420
And no SquashFS delta is installed 0.050
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.239
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.272
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.356
When the network is plugged 0.026
And Tor is ready 11.782
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.632
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.488
Given I shutdown Tails and wait for the computer to power off 5.274
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.408
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.094
And the file system changes introduced in version 6.2~testoverlayfs are present 0.190
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.140
# 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.221
When the network is plugged 0.025
And Tor is ready 10.165
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.874
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.109
Given I shutdown Tails and wait for the computer to power off 4.093
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.520
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.126
And the file system changes introduced in version 6.3~testoverlayfs are present 0.313
And only the 6.3~testoverlayfs SquashFS delta is installed 0.036
# 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.150
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.226
When the network is plugged 0.025
And Tor is ready 10.354
Then the Upgrader considers the system as up-to-date 0.095
# 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 3.494
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.352
After features/support/hooks.rb:339 0.700
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
18.671
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.763
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.197
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 8.462
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.125
After features/support/hooks.rb:339 1.029
After features/support/hooks.rb:108 0.000