Project Number Date
test_Tails_ISO_stable 5963 21 Nov 2025, 12:12

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 16:21.315 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:56.852
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.166
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 31.677
When I start Tails from USB drive "old" with network unplugged 1:20.118
Then the boot device has safe access rights 2.838
And Tails is running from USB drive "old" 0.345
And there is no persistence partition on USB drive "old" 0.102
And process "udev-watchdog" is running 0.075
And udev-watchdog is monitoring the correct device 0.237
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:331 3.910
After features/support/hooks.rb:100 0.010
Tags: @product
2:9.899
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.162
And I start Tails from USB drive "old" with network unplugged and I login 1:32.188
Then Tails is running from USB drive "old" 0.281
And I create a persistent partition 27.307
And I take note of which tps features are available 1.191
Then a Tails persistence partition exists on USB drive "old" 0.691
And I shutdown Tails and wait for the computer to power off 8.075
After features/support/hooks.rb:331 0.571
After features/support/hooks.rb:100 0.010
Tags: @product
2:23.376
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.168
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:50.444
Then Tails is running from USB drive "old" 0.314
And all tps features are active 1.848
When I write some files expected to persist 1.497
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.211
And all persistence configuration files have safe access rights 0.525
And all persistent directories from the old Tails version have safe access rights 2.485
And I take note of which tps features are available 0.510
And I shutdown Tails and wait for the computer to power off 7.545
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.823
After features/support/hooks.rb:331 0.562
After features/support/hooks.rb:100 0.009
Tags: @product
2:32.330
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 without a persistent partition and stopped at Tails Greeter's login screen 11.972
And I log in to a new session 11.999
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.633
And I plug USB drive "to_upgrade" 6.256
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.905
Then the running Tails is installed on USB drive "to_upgrade" 20.124
And I unplug USB drive "to_upgrade" 0.231
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:331 4.229
After features/support/hooks.rb:100 0.000
Tags: @product
1:45.050
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.164
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:36.134
Then all tps features from the old Tails version are active 1.559
And Tails is running from USB drive "to_upgrade" 0.318
And the boot device has safe access rights 3.109
And the expected persistent files created with the old Tails version are present in the filesystem 1.532
And all persistent directories from the old Tails version have safe access rights 2.231
After features/support/hooks.rb:331 0.803
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
5:11.410
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 26.954
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.244
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.300
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.443
When the network is plugged 0.052
And Tor is ready 12.841
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.582
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.273
Given I shutdown Tails and wait for the computer to power off 7.910
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:37.696
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.009
And the file system changes introduced in version 6.2~testoverlayfs are present 0.290
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.182
# 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.293
When the network is plugged 0.060
And Tor is ready 10.819
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.212
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.716
Given I shutdown Tails and wait for the computer to power off 7.640
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:38.376
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.184
And the file system changes introduced in version 6.3~testoverlayfs are present 0.438
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.172
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.247
When the network is plugged 0.048
And Tor is ready 18.496
Then the Upgrader considers the system as up-to-date 0.189
# 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 5.881
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.557
After features/support/hooks.rb:331 0.852
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
22.396
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 11.009
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.231
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.054
And Tor is ready 9.276
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.713
After features/support/hooks.rb:331 1.156
After features/support/hooks.rb:100 0.000