Project Number Date
test_Tails_ISO_devel 4064 10 Nov 2025, 17:15

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:17.229 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:0.802
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.202
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 30.639
When I start Tails from USB drive "old" with network unplugged 1:25.222
Then the boot device has safe access rights 2.835
And Tails is running from USB drive "old" 0.278
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.237
And I unplug USB drive "old" 0.162
After features/support/hooks.rb:331 4.133
After features/support/hooks.rb:100 0.013
Tags: @product
2:0.970
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login 1:24.182
Then Tails is running from USB drive "old" 0.682
And I create a persistent partition 28.735
And I take note of which tps features are available 1.240
Then a Tails persistence partition exists on USB drive "old" 0.639
And I shutdown Tails and wait for the computer to power off 5.304
After features/support/hooks.rb:331 0.510
After features/support/hooks.rb:100 0.008
Tags: @product
2:2.809
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:33.959
Then Tails is running from USB drive "old" 0.322
And all tps features are active 2.095
When I write some files expected to persist 1.602
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.318
And all persistence configuration files have safe access rights 0.457
And all persistent directories from the old Tails version have safe access rights 2.280
And I take note of which tps features are available 0.493
And I shutdown Tails and wait for the computer to power off 3.254
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.849
After features/support/hooks.rb:331 0.123
After features/support/hooks.rb:100 0.009
Tags: @product
2:35.321
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 12.792
And I log in to a new session 16.514
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.107
And I plug USB drive "to_upgrade" 2.674
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.434
Then the running Tails is installed on USB drive "to_upgrade" 20.415
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.178
After features/support/hooks.rb:331 3.716
After features/support/hooks.rb:100 0.000
Tags: @product
1:45.531
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.171
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:36.962
Then all tps features from the old Tails version are active 1.527
And Tails is running from USB drive "to_upgrade" 0.290
And the boot device has safe access rights 3.102
And the expected persistent files created with the old Tails version are present in the filesystem 1.368
And all persistent directories from the old Tails version have safe access rights 2.108
After features/support/hooks.rb:331 0.789
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
5:26.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 with a persistent partition enabled and logged in 13.015
And no SquashFS delta is installed 0.109
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.282
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.285
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.531
When the network is plugged 0.057
And Tor is ready 14.740
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.639
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.386
Given I shutdown Tails and wait for the computer to power off 8.554
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.398
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.771
And the file system changes introduced in version 6.2~testoverlayfs are present 0.253
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.153
# 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.194
When the network is plugged 0.047
And Tor is ready 12.185
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.789
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.134
Given I shutdown Tails and wait for the computer to power off 7.762
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:46.952
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.071
And the file system changes introduced in version 6.3~testoverlayfs are present 0.578
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.176
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.255
When the network is plugged 0.061
And Tor is ready 12.621
Then the Upgrader considers the system as up-to-date 0.183
# 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.340
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.731
After features/support/hooks.rb:331 1.329
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
25.318
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.441
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.062
And the signing key used by the Upgrader is outdated 0.061
But a current signing key is available on our website 0.000
When the network is plugged 0.048
And Tor is ready 10.485
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.963
After features/support/hooks.rb:331 1.227
After features/support/hooks.rb:100 0.000