Project Number Date
test_Tails_ISO_stable 5940 10 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:55.565 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
2:30.002
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.167
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 38.216
When I start Tails from USB drive "old" with network unplugged 1:46.755
Then the boot device has safe access rights 2.800
And Tails is running from USB drive "old" 0.345
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.066
And udev-watchdog is monitoring the correct device 0.303
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:331 4.066
After features/support/hooks.rb:100 0.011
Tags: @product
2:4.758
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.165
And I start Tails from USB drive "old" with network unplugged and I login 1:25.445
Then Tails is running from USB drive "old" 0.245
And I create a persistent partition 28.918
And I take note of which tps features are available 1.363
Then a Tails persistence partition exists on USB drive "old" 0.639
And I shutdown Tails and wait for the computer to power off 7.979
After features/support/hooks.rb:331 0.320
After features/support/hooks.rb:100 0.010
Tags: @product
2:14.945
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:41.179
Then Tails is running from USB drive "old" 0.749
And all tps features are active 2.072
When I write some files expected to persist 1.539
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.193
And all persistence configuration files have safe access rights 0.359
And all persistent directories from the old Tails version have safe access rights 2.157
And I take note of which tps features are available 0.481
And I shutdown Tails and wait for the computer to power off 8.111
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.930
After features/support/hooks.rb:331 0.446
After features/support/hooks.rb:100 0.008
Tags: @product
2:33.476
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 without a persistent partition and stopped at Tails Greeter's login screen 13.003
And I log in to a new session 15.935
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.131
And I plug USB drive "to_upgrade" 2.418
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.878
Then the running Tails is installed on USB drive "to_upgrade" 20.698
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:331 3.994
After features/support/hooks.rb:100 0.000
Tags: @product
1:44.637
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.160
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:35.780
Then all tps features from the old Tails version are active 1.427
And Tails is running from USB drive "to_upgrade" 0.330
And the boot device has safe access rights 3.011
And the expected persistent files created with the old Tails version are present in the filesystem 1.697
And all persistent directories from the old Tails version have safe access rights 2.229
After features/support/hooks.rb:331 0.735
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
5:24.084
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 12.197
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.292
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.290
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.446
When the network is plugged 0.076
And Tor is ready 43.138
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.601
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.526
Given I shutdown Tails and wait for the computer to power off 12.464
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:39.168
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.218
And the file system changes introduced in version 6.2~testoverlayfs are present 0.284
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.134
# 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.264
When the network is plugged 0.051
And Tor is ready 12.583
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.564
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.294
Given I shutdown Tails and wait for the computer to power off 7.658
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:38.733
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.003
And the file system changes introduced in version 6.3~testoverlayfs are present 0.510
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.155
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.243
When the network is plugged 0.061
And Tor is ready 11.148
Then the Upgrader considers the system as up-to-date 0.333
# 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.875
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.445
After features/support/hooks.rb:331 1.354
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
23.659
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.650
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.288
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
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.066
And Tor is ready 10.855
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.685
After features/support/hooks.rb:331 0.715
After features/support/hooks.rb:100 0.000