Project Number Date
test_Tails_ISO_stable 5929 03 Nov 2025, 15:58

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:38.484 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:17.333
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 1.426
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 31.213
When I start Tails from USB drive "old" with network unplugged 1:39.869
Then the boot device has safe access rights 2.843
And Tails is running from USB drive "old" 0.324
And there is no persistence partition on USB drive "old" 0.090
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.237
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:331 4.210
After features/support/hooks.rb:100 0.009
Tags: @product
2:8.938
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.157
And I start Tails from USB drive "old" with network unplugged and I login 1:25.215
Then Tails is running from USB drive "old" 0.290
And I create a persistent partition 33.665
And I take note of which tps features are available 1.127
Then a Tails persistence partition exists on USB drive "old" 0.661
And I shutdown Tails and wait for the computer to power off 7.821
After features/support/hooks.rb:331 0.520
After features/support/hooks.rb:100 0.009
Tags: @product
2:4.137
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:33.848
Then Tails is running from USB drive "old" 0.292
And all tps features are active 1.857
When I write some files expected to persist 1.714
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.335
And all persistence configuration files have safe access rights 0.430
And all persistent directories from the old Tails version have safe access rights 2.478
And I take note of which tps features are available 0.432
And I shutdown Tails and wait for the computer to power off 4.817
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.759
After features/support/hooks.rb:331 0.272
After features/support/hooks.rb:100 0.009
Tags: @product
2:35.452
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.833
And I log in to a new session 16.821
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.412
And I plug USB drive "to_upgrade" 2.413
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.546
Then the running Tails is installed on USB drive "to_upgrade" 20.031
And I unplug USB drive "to_upgrade" 0.185
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:331 5.553
After features/support/hooks.rb:100 0.000
Tags: @product
2:7.402
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 7.639
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:41.197
Then all tps features from the old Tails version are active 11.907
And Tails is running from USB drive "to_upgrade" 0.324
And the boot device has safe access rights 2.941
And the expected persistent files created with the old Tails version are present in the filesystem 1.259
And all persistent directories from the old Tails version have safe access rights 2.132
After features/support/hooks.rb:331 1.045
After features/support/hooks.rb:100 0.009
4:57.890
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 14.192
And no SquashFS delta is installed 0.080
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.245
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.245
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.416
When the network is plugged 0.073
And Tor is ready 14.957
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.594
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.630
Given I shutdown Tails and wait for the computer to power off 11.242
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:42.769
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 1.998
And the file system changes introduced in version 6.2~testoverlayfs are present 0.281
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.173
# 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.239
When the network is plugged 0.052
And Tor is ready 10.909
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.712
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.949
Given I shutdown Tails and wait for the computer to power off 7.723
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:37.471
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.186
And the file system changes introduced in version 6.3~testoverlayfs are present 0.448
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.154
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.189
When the network is plugged 0.056
And Tor is ready 10.732
Then the Upgrader considers the system as up-to-date 0.185
# 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.315
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.444
After features/support/hooks.rb:331 0.817
After features/support/hooks.rb:100 0.018
27.329
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.184
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.262
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.064
But a current signing key is available on our website 0.000
When the network is plugged 0.060
And Tor is ready 13.900
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.806
After features/support/hooks.rb:331 1.012
After features/support/hooks.rb:100 0.000