Project Number Date
test_Tails_ISO_devel 4143 31 Dec 2025, 07:52

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 10:42.707 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
58.789
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.198
When I start Tails from USB drive "old" with network unplugged 41.475
Then the boot device has safe access rights 2.312
And Tails is running from USB drive "old" 0.238
And there is no persistence partition on USB drive "old" 0.096
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.198
And I unplug USB drive "old" 0.129
After features/support/hooks.rb:331 3.790
After features/support/hooks.rb:100 0.006
Tags: @product
1:25.354
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login 52.060
Then Tails is running from USB drive "old" 0.239
And I create a persistent partition 23.702
And I take note of which tps features are available 0.643
Then a Tails persistence partition exists on USB drive "old" 0.526
And I shutdown Tails and wait for the computer to power off 8.134
After features/support/hooks.rb:331 0.541
After features/support/hooks.rb:100 0.006
Tags: @product
1:21.918
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.197
Then Tails is running from USB drive "old" 0.232
And all tps features are active 1.235
When I write some files expected to persist 1.192
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.174
And all persistence configuration files have safe access rights 0.351
And all persistent directories from the old Tails version have safe access rights 1.800
And I take note of which tps features are available 0.134
And I shutdown Tails and wait for the computer to power off 7.857
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.692
After features/support/hooks.rb:331 0.369
After features/support/hooks.rb:100 0.007
Tags: @product
2:9.544
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 without a persistent partition and stopped at Tails Greeter's login screen 8.330
And I log in to a new session 12.677
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.697
And I plug USB drive "to_upgrade" 2.229
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.216
Then the running Tails is installed on USB drive "to_upgrade" 14.108
And I unplug USB drive "to_upgrade" 0.140
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:331 3.563
After features/support/hooks.rb:100 0.000
Tags: @product
1:5.255
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.054
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.618
Then all tps features from the old Tails version are active 0.892
And Tails is running from USB drive "to_upgrade" 0.272
And the boot device has safe access rights 2.477
And the expected persistent files created with the old Tails version are present in the filesystem 1.124
And all persistent directories from the old Tails version have safe access rights 1.814
After features/support/hooks.rb:331 0.989
After features/support/hooks.rb:100 0.019
3:23.242
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 with a persistent partition enabled and logged in 8.011
And no SquashFS delta is installed 0.060
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.189
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.202
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.344
When the network is plugged 0.019
And Tor is ready 13.146
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.318
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.312
Given I shutdown Tails and wait for the computer to power off 5.358
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.765
Then Tails is running version 6.2~testoverlayfs 0.037
And all tps features are active 1.161
And the file system changes introduced in version 6.2~testoverlayfs are present 0.228
And only the 6.2~testoverlayfs SquashFS delta is installed 0.038
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.163
# 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.189
When the network is plugged 0.014
And Tor is ready 10.410
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.291
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.073
Given I shutdown Tails and wait for the computer to power off 3.989
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.997
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.086
And the file system changes introduced in version 6.3~testoverlayfs are present 0.376
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.158
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.187
When the network is plugged 0.014
And Tor is ready 11.020
Then the Upgrader considers the system as up-to-date 10.481
# 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.155
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.347
After features/support/hooks.rb:331 0.725
After features/support/hooks.rb:100 0.015
18.603
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 7.369
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.199
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.026
And Tor is ready 9.833
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.064
After features/support/hooks.rb:331 0.606
After features/support/hooks.rb:100 0.000