Project Number Date
test_Tails_ISO_stable 6015 19 Dec 2025, 07:14

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:3.579 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:7.518
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.059
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.245
When I start Tails from USB drive "old" with network unplugged 50.051
Then the boot device has safe access rights 2.493
And Tails is running from USB drive "old" 0.222
And there is no persistence partition on USB drive "old" 0.036
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.192
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:331 3.569
After features/support/hooks.rb:100 0.055
Tags: @product
1:23.748
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login 50.825
Then Tails is running from USB drive "old" 0.264
And I create a persistent partition 23.578
And I take note of which tps features are available 0.645
Then a Tails persistence partition exists on USB drive "old" 0.548
And I shutdown Tails and wait for the computer to power off 7.834
After features/support/hooks.rb:331 0.566
After features/support/hooks.rb:100 0.007
Tags: @product
1:22.707
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.447
Then Tails is running from USB drive "old" 0.252
And all tps features are active 1.117
When I write some files expected to persist 1.220
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.167
And all persistence configuration files have safe access rights 0.229
And all persistent directories from the old Tails version have safe access rights 2.085
And I take note of which tps features are available 0.132
And I shutdown Tails and wait for the computer to power off 7.943
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.058
After features/support/hooks.rb:331 0.124
After features/support/hooks.rb:100 0.007
Tags: @product
2:11.341
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.592
And I log in to a new session 12.676
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.817
And I plug USB drive "to_upgrade" 2.241
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.259
Then the running Tails is installed on USB drive "to_upgrade" 15.476
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.145
After features/support/hooks.rb:331 3.813
After features/support/hooks.rb:100 0.000
Tags: @product
1:5.820
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.048
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.802
Then all tps features from the old Tails version are active 1.029
And Tails is running from USB drive "to_upgrade" 0.266
And the boot device has safe access rights 2.428
And the expected persistent files created with the old Tails version are present in the filesystem 1.291
And all persistent directories from the old Tails version have safe access rights 1.953
After features/support/hooks.rb:331 0.991
After features/support/hooks.rb:100 0.006
3:33.514
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 8.061
And no SquashFS delta is installed 0.067
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.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.226
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.318
When the network is plugged 0.013
And Tor is ready 13.653
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.481
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.808
Given I shutdown Tails and wait for the computer to power off 9.458
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.946
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.194
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.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.127
# 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.239
When the network is plugged 0.017
And Tor is ready 9.717
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.079
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.965
Given I shutdown Tails and wait for the computer to power off 7.937
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 57.772
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.072
And the file system changes introduced in version 6.3~testoverlayfs are present 0.374
And only the 6.3~testoverlayfs SquashFS delta is installed 0.053
# 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.143
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.175
When the network is plugged 0.018
And Tor is ready 11.445
Then the Upgrader considers the system as up-to-date 10.545
# 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.722
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.316
After features/support/hooks.rb:331 0.968
After features/support/hooks.rb:100 0.017
18.926
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 7.337
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.219
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 9.390
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.840
After features/support/hooks.rb:331 0.809
After features/support/hooks.rb:100 0.000