Project Number Date
test_Tails_ISO_stable 6009 15 Dec 2025, 17:27

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:14.040 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:38.305
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.278
And I create a 7200 MiB disk named "old" 0.094
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 31.448
When I start Tails from USB drive "old" with network unplugged 1:1.466
Then the boot device has safe access rights 3.099
And Tails is running from USB drive "old" 0.272
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.265
And I unplug USB drive "old" 0.219
After features/support/hooks.rb:331 3.679
After features/support/hooks.rb:100 0.015
Tags: @product
1:42.889
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login 1:3.754
Then Tails is running from USB drive "old" 0.315
And I create a persistent partition 29.090
And I take note of which tps features are available 1.109
Then a Tails persistence partition exists on USB drive "old" 0.674
And I shutdown Tails and wait for the computer to power off 7.745
After features/support/hooks.rb:331 0.621
After features/support/hooks.rb:100 0.010
Tags: @product
1:45.498
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:12.365
Then Tails is running from USB drive "old" 0.290
And all tps features are active 1.981
When I write some files expected to persist 1.827
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.204
And all persistence configuration files have safe access rights 0.359
And all persistent directories from the old Tails version have safe access rights 2.381
And I take note of which tps features are available 0.463
And I shutdown Tails and wait for the computer to power off 7.618
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.821
After features/support/hooks.rb:331 0.367
After features/support/hooks.rb:100 0.009
Tags: @product
2:48.698
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 without a persistent partition and stopped at Tails Greeter's login screen 12.755
And I log in to a new session 16.003
And I clone USB drive "old" to a new USB drive "to_upgrade" 12.262
And I plug USB drive "to_upgrade" 2.688
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.535
Then the running Tails is installed on USB drive "to_upgrade" 20.996
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.253
After features/support/hooks.rb:331 4.097
After features/support/hooks.rb:100 0.000
Tags: @product
1:26.028
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.194
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:16.588
Then all tps features from the old Tails version are active 1.661
And Tails is running from USB drive "to_upgrade" 0.440
And the boot device has safe access rights 3.295
And the expected persistent files created with the old Tails version are present in the filesystem 1.429
And all persistent directories from the old Tails version have safe access rights 2.419
After features/support/hooks.rb:331 0.954
After features/support/hooks.rb:100 0.008
4:23.123
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 with a persistent partition enabled and logged in 12.938
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.305
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.339
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.448
When the network is plugged 0.091
And Tor is ready 13.311
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.882
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.429
Given I shutdown Tails and wait for the computer to power off 10.875
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.504
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.147
And the file system changes introduced in version 6.2~testoverlayfs are present 0.260
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.145
# 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.223
When the network is plugged 0.054
And Tor is ready 12.515
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.683
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.185
Given I shutdown Tails and wait for the computer to power off 7.576
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.781
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.235
And the file system changes introduced in version 6.3~testoverlayfs are present 0.538
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.194
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.280
When the network is plugged 0.062
And Tor is ready 11.404
Then the Upgrader considers the system as up-to-date 10.594
# 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.276
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.526
After features/support/hooks.rb:331 0.944
After features/support/hooks.rb:100 0.018
29.495
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 with a persistent partition enabled and logged in 14.447
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.247
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 1.746
And Tor is ready 12.368
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.582
After features/support/hooks.rb:331 0.986
After features/support/hooks.rb:100 0.000