Project Number Date
test_Tails_ISO_stable 6325 23 Apr 2026, 11:33

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 13:6.990 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.098
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.048
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.658
When I start Tails from USB drive "old" with network unplugged 52.865
Then the boot device has safe access rights 2.757
And Tails is running from USB drive "old" 0.246
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.222
And I unplug USB drive "old" 0.140
After features/support/hooks.rb:331 1.152
After features/support/hooks.rb:100 0.005
Tags: @product
1:30.534
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login 55.028
Then Tails is running from USB drive "old" 0.263
And I create a persistent partition 25.540
And I take note of which tps features are available 0.839
Then a Tails persistence partition exists on USB drive "old" 0.613
And I shutdown Tails and wait for the computer to power off 8.191
After features/support/hooks.rb:331 0.348
After features/support/hooks.rb:100 0.010
Tags: @product
1:30.692
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.007
Then Tails is running from USB drive "old" 0.232
And all tps features are active 1.251
When I write some files expected to persist 1.303
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.182
And all persistence configuration files have safe access rights 0.498
And all persistent directories from the old Tails version have safe access rights 1.959
And I take note of which tps features are available 0.204
And I shutdown Tails and wait for the computer to power off 8.433
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.533
After features/support/hooks.rb:331 0.183
After features/support/hooks.rb:100 0.008
Tags: @product
2:12.227
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 without a persistent partition and stopped at Tails Greeter's login screen 8.123
And I log in to a new session 12.630
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.766
And I plug USB drive "to_upgrade" 2.262
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.829
Then the running Tails is installed on USB drive "to_upgrade" 16.323
And I unplug USB drive "to_upgrade" 0.139
And I unplug USB drive "__internal" 0.152
After features/support/hooks.rb:331 3.493
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.494
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.058
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.803
Then all tps features from the old Tails version are active 1.088
And Tails is running from USB drive "to_upgrade" 0.304
And the boot device has safe access rights 2.730
And the expected persistent files created with the old Tails version are present in the filesystem 1.236
And all persistent directories from the old Tails version have safe access rights 2.273
After features/support/hooks.rb:331 0.888
After features/support/hooks.rb:100 0.028
Tags: @product @automatic_upgrade
4:42.946
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.600
And no SquashFS delta is installed 0.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.246
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.269
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.363
When the network is plugged 0.014
And Tor is ready 22.462
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.419
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.778
Given I shutdown Tails and wait for the computer to power off 20.204
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.202
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 1.269
And the file system changes introduced in version 6.2~testoverlayfs are present 0.231
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.139
# 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.211
When the network is plugged 0.014
And Tor is ready 20.267
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.525
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.790
Given I shutdown Tails and wait for the computer to power off 17.366
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.557
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.330
And the file system changes introduced in version 6.3~testoverlayfs are present 0.502
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.290
When the network is plugged 0.038
And Tor is ready 21.625
Then the Upgrader considers the system as up-to-date 0.122
# 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 4.348
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.373
After features/support/hooks.rb:331 1.014
After features/support/hooks.rb:100 0.032
Tags: @product @automatic_upgrade
47.994
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.406
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.255
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 39.799
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.400
After features/support/hooks.rb:331 0.728
After features/support/hooks.rb:100 0.000