Project Number Date
test_Tails_ISO_devel 4522 30 Jul 2026, 00: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 10:59.357 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
54.566
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.089
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.160
When I start Tails from USB drive "old" with network unplugged 37.760
Then the boot device has safe access rights 1.973
And Tails is running from USB drive "old" 0.206
And there is no persistence partition on USB drive "old" 0.036
And process "udev-watchdog" is running 0.042
And udev-watchdog is monitoring the correct device 0.143
And I unplug USB drive "old" 0.115
After features/support/hooks.rb:339 3.498
After features/support/hooks.rb:108 0.113
Tags: @product
1:18.304
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login 45.887
Then Tails is running from USB drive "old" 0.171
And I create a persistent partition 22.752
And I take note of which tps features are available 6.380
Then a Tails persistence partition exists on USB drive "old" 0.457
And I shutdown Tails and wait for the computer to power off 2.575
After features/support/hooks.rb:339 0.549
After features/support/hooks.rb:108 0.005
Tags: @product
1:30.438
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.073
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.900
Then Tails is running from USB drive "old" 0.192
And all tps features are active 6.761
When I write some files expected to persist 1.034
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.180
And all persistence configuration files have safe access rights 0.238
And all persistent directories from the old Tails version have safe access rights 1.421
And I take note of which tps features are available 6.063
And I shutdown Tails and wait for the computer to power off 2.490
# 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.081
After features/support/hooks.rb:339 0.389
After features/support/hooks.rb:108 0.005
Tags: @product
2:9.842
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 without a persistent partition and stopped at Tails Greeter's login screen 8.152
And I log in to a new session 10.084
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.630
And I plug USB drive "to_upgrade" 2.299
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.583
Then the running Tails is installed on USB drive "to_upgrade" 17.854
And I unplug USB drive "to_upgrade" 0.113
And I unplug USB drive "__internal" 0.122
After features/support/hooks.rb:339 1.539
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.390
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.116
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.751
Then all tps features from the old Tails version are active 1.012
And Tails is running from USB drive "to_upgrade" 0.223
And the boot device has safe access rights 1.972
And the expected persistent files created with the old Tails version are present in the filesystem 0.785
And all persistent directories from the old Tails version have safe access rights 1.528
After features/support/hooks.rb:339 0.838
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:30.667
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.046
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.254
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.173
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.356
When the network is plugged 0.036
And Tor is ready 11.455
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.947
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.660
Given I shutdown Tails and wait for the computer to power off 6.688
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.673
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 7.006
And the file system changes introduced in version 6.2~testoverlayfs are present 0.182
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.082
# 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.141
When the network is plugged 0.047
And Tor is ready 10.138
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.422
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.350
Given I shutdown Tails and wait for the computer to power off 2.556
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.210
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.204
And the file system changes introduced in version 6.3~testoverlayfs are present 0.296
And only the 6.3~testoverlayfs SquashFS delta is installed 0.088
# 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.108
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.200
When the network is plugged 0.032
And Tor is ready 10.107
Then the Upgrader considers the system as up-to-date 10.431
# 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.294
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.284
After features/support/hooks.rb:339 0.654
After features/support/hooks.rb:108 0.008
Tags: @product @automatic_upgrade
31.147
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 20.906
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.215
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.030
And Tor is ready 7.900
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.007
After features/support/hooks.rb:339 0.534
After features/support/hooks.rb:108 0.000