Project Number Date
test_Tails_ISO_stable 5957 16 Nov 2025, 12:11

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 15:35.758 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.617
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.200
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 30.778
When I start Tails from USB drive "old" with network unplugged 1:20.763
Then the boot device has safe access rights 2.844
And Tails is running from USB drive "old" 0.359
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.065
And udev-watchdog is monitoring the correct device 0.261
And I unplug USB drive "old" 0.180
After features/support/hooks.rb:331 3.870
After features/support/hooks.rb:100 0.010
Tags: @product
2:5.671
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.159
And I start Tails from USB drive "old" with network unplugged and I login 1:25.507
Then Tails is running from USB drive "old" 0.678
And I create a persistent partition 29.159
And I take note of which tps features are available 1.291
Then a Tails persistence partition exists on USB drive "old" 0.638
And I shutdown Tails and wait for the computer to power off 8.236
After features/support/hooks.rb:331 0.397
After features/support/hooks.rb:100 0.009
Tags: @product
2:9.772
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.393
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:36.810
Then Tails is running from USB drive "old" 0.272
And all tps features are active 1.958
When I write some files expected to persist 1.552
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.218
And all persistence configuration files have safe access rights 0.322
And all persistent directories from the old Tails version have safe access rights 1.949
And I take note of which tps features are available 0.433
And I shutdown Tails and wait for the computer to power off 7.591
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.269
After features/support/hooks.rb:331 0.184
After features/support/hooks.rb:100 0.011
Tags: @product
2:32.186
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 14.184
And I log in to a new session 11.970
And I clone USB drive "old" to a new USB drive "to_upgrade" 3.209
And I plug USB drive "to_upgrade" 2.525
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.419
Then the running Tails is installed on USB drive "to_upgrade" 18.493
And I unplug USB drive "to_upgrade" 0.184
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:331 3.590
After features/support/hooks.rb:100 0.000
Tags: @product
1:44.504
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.165
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:36.348
Then all tps features from the old Tails version are active 1.380
And Tails is running from USB drive "to_upgrade" 0.275
And the boot device has safe access rights 2.798
And the expected persistent files created with the old Tails version are present in the filesystem 1.320
And all persistent directories from the old Tails version have safe access rights 2.216
After features/support/hooks.rb:331 0.865
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:44.702
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 with a persistent partition enabled and logged in 12.545
And no SquashFS delta is installed 0.084
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.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.262
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.401
When the network is plugged 0.050
And Tor is ready 12.660
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.868
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.543
Given I shutdown Tails and wait for the computer to power off 4.719
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:38.476
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 1.956
And the file system changes introduced in version 6.2~testoverlayfs are present 0.244
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.144
# 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.319
When the network is plugged 0.053
And Tor is ready 11.655
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.800
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.896
Given I shutdown Tails and wait for the computer to power off 8.072
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:33.777
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.227
And the file system changes introduced in version 6.3~testoverlayfs are present 0.424
And only the 6.3~testoverlayfs SquashFS delta is installed 0.055
# 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.154
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.248
When the network is plugged 0.051
And Tor is ready 11.790
Then the Upgrader considers the system as up-to-date 0.288
# 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 8.044
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.476
After features/support/hooks.rb:331 1.605
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
22.301
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 with a persistent partition enabled and logged in 10.975
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.299
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.060
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 10.196
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.654
After features/support/hooks.rb:331 1.099
After features/support/hooks.rb:100 0.000