Project Number Date
test_Tails_ISO_devel 4084 23 Nov 2025, 12:06

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:2.085 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:4.420
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.164
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.039
And I write an old version of the Tails USB image to disk "old" 30.320
When I start Tails from USB drive "old" with network unplugged 1:29.176
Then the boot device has safe access rights 2.867
And Tails is running from USB drive "old" 0.283
And there is no persistence partition on USB drive "old" 0.087
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.214
And I unplug USB drive "old" 0.175
After features/support/hooks.rb:331 3.896
After features/support/hooks.rb:100 0.009
Tags: @product
2:9.496
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:24.235
Then Tails is running from USB drive "old" 0.311
And I create a persistent partition 35.148
And I take note of which tps features are available 1.220
Then a Tails persistence partition exists on USB drive "old" 0.680
And I shutdown Tails and wait for the computer to power off 7.709
After features/support/hooks.rb:331 0.589
After features/support/hooks.rb:100 0.011
Tags: @product
2:6.585
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.317
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:33.692
Then Tails is running from USB drive "old" 0.297
And all tps features are active 1.770
When I write some files expected to persist 1.501
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.218
And all persistence configuration files have safe access rights 0.324
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.481
And I shutdown Tails and wait for the computer to power off 7.704
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.798
After features/support/hooks.rb:331 0.386
After features/support/hooks.rb:100 0.009
Tags: @product
2:49.853
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.569
And I log in to a new session 13.189
And I clone USB drive "old" to a new USB drive "to_upgrade" 8.023
And I plug USB drive "to_upgrade" 2.728
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:54.842
Then the running Tails is installed on USB drive "to_upgrade" 18.125
And I unplug USB drive "to_upgrade" 0.184
And I unplug USB drive "__internal" 0.190
After features/support/hooks.rb:331 3.608
After features/support/hooks.rb:100 0.000
Tags: @product
1:45.888
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.017
Given a computer 0.180
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:36.863
Then all tps features from the old Tails version are active 1.378
And Tails is running from USB drive "to_upgrade" 0.303
And the boot device has safe access rights 3.514
And the expected persistent files created with the old Tails version are present in the filesystem 1.367
And all persistent directories from the old Tails version have safe access rights 2.280
After features/support/hooks.rb:331 1.084
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
4:45.198
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.639
And no SquashFS delta is installed 0.072
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.373
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.490
When the network is plugged 0.133
And Tor is ready 12.743
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.655
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.013
Given I shutdown Tails and wait for the computer to power off 9.802
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:38.444
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.384
And the file system changes introduced in version 6.2~testoverlayfs are present 0.283
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.158
# 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.217
When the network is plugged 0.045
And Tor is ready 12.934
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.568
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.748
Given I shutdown Tails and wait for the computer to power off 3.109
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:36.782
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.974
And the file system changes introduced in version 6.3~testoverlayfs are present 0.477
And only the 6.3~testoverlayfs SquashFS delta is installed 0.086
# 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.177
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.246
When the network is plugged 0.068
And Tor is ready 11.176
Then the Upgrader considers the system as up-to-date 0.206
# 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.277
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.473
After features/support/hooks.rb:331 0.915
After features/support/hooks.rb:100 0.029
Tags: @product @automatic_upgrade
20.642
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 9.672
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.313
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the signing key used by the Upgrader is outdated 0.056
But a current signing key is available on our website 0.000
When the network is plugged 0.058
And Tor is ready 9.904
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.559
After features/support/hooks.rb:331 0.716
After features/support/hooks.rb:100 0.000