Project Number Date
test_Tails_ISO_stable 6007 14 Dec 2025, 12:48

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 14:51.908 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:54.134
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.212
And I create a 7200 MiB disk named "old" 0.111
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 32.092
When I start Tails from USB drive "old" with network unplugged 1:16.496
Then the boot device has safe access rights 3.286
And Tails is running from USB drive "old" 0.318
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.263
And I unplug USB drive "old" 0.176
After features/support/hooks.rb:331 3.881
After features/support/hooks.rb:100 0.010
Tags: @product
1:42.742
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login 1:3.179
Then Tails is running from USB drive "old" 0.357
And I create a persistent partition 29.304
And I take note of which tps features are available 1.051
Then a Tails persistence partition exists on USB drive "old" 0.711
And I shutdown Tails and wait for the computer to power off 7.955
After features/support/hooks.rb:331 0.255
After features/support/hooks.rb:100 0.009
Tags: @product
1:49.836
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:16.056
Then Tails is running from USB drive "old" 0.410
And all tps features are active 1.854
When I write some files expected to persist 1.682
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.205
And all persistence configuration files have safe access rights 0.464
And all persistent directories from the old Tails version have safe access rights 2.368
And I take note of which tps features are available 0.535
And I shutdown Tails and wait for the computer to power off 7.490
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.587
After features/support/hooks.rb:331 0.574
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.265
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 12.169
And I log in to a new session 16.950
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.982
And I plug USB drive "to_upgrade" 2.580
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.611
Then the running Tails is installed on USB drive "to_upgrade" 20.575
And I unplug USB drive "to_upgrade" 0.196
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:331 3.864
After features/support/hooks.rb:100 0.000
Tags: @product
1:24.626
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:15.651
Then all tps features from the old Tails version are active 1.873
And Tails is running from USB drive "to_upgrade" 0.321
And the boot device has safe access rights 3.089
And the expected persistent files created with the old Tails version are present in the filesystem 1.331
And all persistent directories from the old Tails version have safe access rights 2.193
After features/support/hooks.rb:331 0.816
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
5:0.766
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 13.695
And no SquashFS delta is installed 0.107
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.267
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.337
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.448
When the network is plugged 0.056
And Tor is ready 44.227
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.651
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.018
Given I shutdown Tails and wait for the computer to power off 11.111
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.004
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.255
And the file system changes introduced in version 6.2~testoverlayfs are present 0.338
And only the 6.2~testoverlayfs SquashFS delta is installed 0.106
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.201
# 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.242
When the network is plugged 0.062
And Tor is ready 11.212
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.908
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.451
Given I shutdown Tails and wait for the computer to power off 8.056
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.240
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.551
And the file system changes introduced in version 6.3~testoverlayfs are present 0.519
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.216
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.275
When the network is plugged 0.084
And Tor is ready 12.061
Then the Upgrader considers the system as up-to-date 10.698
# 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.674
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.512
After features/support/hooks.rb:331 0.821
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
26.536
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 11.575
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.353
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.072
But a current signing key is available on our website 0.000
When the network is plugged 0.054
And Tor is ready 10.966
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.447
After features/support/hooks.rb:331 0.857
After features/support/hooks.rb:100 0.000