Project Number Date
test_Tails_ISO_stable 6069 15 Jan 2026, 15:46

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:22.757 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:6.529
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.014
And I write an old version of the Tails USB image to disk "old" 13.395
When I start Tails from USB drive "old" with network unplugged 48.895
Then the boot device has safe access rights 2.492
And Tails is running from USB drive "old" 0.245
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.206
And I unplug USB drive "old" 0.128
After features/support/hooks.rb:331 3.551
After features/support/hooks.rb:100 0.032
Tags: @product
1:21.651
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 "old" with network unplugged and I login 52.127
Then Tails is running from USB drive "old" 0.226
And I create a persistent partition 23.611
And I take note of which tps features are available 0.674
Then a Tails persistence partition exists on USB drive "old" 0.488
And I shutdown Tails and wait for the computer to power off 4.472
After features/support/hooks.rb:331 0.228
After features/support/hooks.rb:100 0.006
Tags: @product
1:23.335
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.549
Then Tails is running from USB drive "old" 0.250
And all tps features are active 1.203
When I write some files expected to persist 1.267
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.151
And all persistence configuration files have safe access rights 0.251
And all persistent directories from the old Tails version have safe access rights 1.641
And I take note of which tps features are available 0.139
And I shutdown Tails and wait for the computer to power off 8.156
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.652
After features/support/hooks.rb:331 0.499
After features/support/hooks.rb:100 0.007
Tags: @product
2:8.744
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 without a persistent partition and stopped at Tails Greeter's login screen 8.508
And I log in to a new session 9.612
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.737
And I plug USB drive "to_upgrade" 2.215
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.376
Then the running Tails is installed on USB drive "to_upgrade" 15.047
And I unplug USB drive "to_upgrade" 0.122
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:331 4.194
After features/support/hooks.rb:100 0.000
Tags: @product
1:6.161
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.047
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.371
Then all tps features from the old Tails version are active 1.036
And Tails is running from USB drive "to_upgrade" 0.246
And the boot device has safe access rights 2.519
And the expected persistent files created with the old Tails version are present in the filesystem 1.066
And all persistent directories from the old Tails version have safe access rights 1.873
After features/support/hooks.rb:331 0.572
After features/support/hooks.rb:100 0.027
Tags: @product @automatic_upgrade
3:57.223
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 8.154
And no SquashFS delta is installed 0.110
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.281
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.254
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.363
When the network is plugged 0.017
And Tor is ready 42.648
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.348
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.484
Given I shutdown Tails and wait for the computer to power off 10.876
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.986
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.121
And the file system changes introduced in version 6.2~testoverlayfs are present 0.223
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.131
# 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.192
When the network is plugged 0.014
And Tor is ready 10.981
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.347
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.138
Given I shutdown Tails and wait for the computer to power off 7.809
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.258
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.028
And the file system changes introduced in version 6.3~testoverlayfs are present 0.354
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.130
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.355
When the network is plugged 0.081
And Tor is ready 9.685
Then the Upgrader considers the system as up-to-date 10.534
# 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.757
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.394
After features/support/hooks.rb:331 0.668
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
19.112
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.576
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.297
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 9.357
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.769
After features/support/hooks.rb:331 0.621
After features/support/hooks.rb:100 0.000