Project Number Date
test_Tails_ISO_stable 5928 03 Nov 2025, 15: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 15:55.583 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:8.773
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.160
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 31.928
When I start Tails from USB drive "old" with network unplugged 1:31.700
Then the boot device has safe access rights 2.982
And Tails is running from USB drive "old" 0.314
And there is no persistence partition on USB drive "old" 0.090
And process "udev-watchdog" is running 0.064
And udev-watchdog is monitoring the correct device 0.268
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:331 3.696
After features/support/hooks.rb:100 0.009
Tags: @product
2:3.509
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login 1:24.238
Then Tails is running from USB drive "old" 0.321
And I create a persistent partition 28.962
And I take note of which tps features are available 1.446
Then a Tails persistence partition exists on USB drive "old" 0.704
And I shutdown Tails and wait for the computer to power off 7.659
After features/support/hooks.rb:331 0.409
After features/support/hooks.rb:100 0.010
Tags: @product
2:6.388
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:33.679
Then Tails is running from USB drive "old" 0.281
And all tps features are active 1.772
When I write some files expected to persist 1.475
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.237
And all persistence configuration files have safe access rights 0.356
And all persistent directories from the old Tails version have safe access rights 2.174
And I take note of which tps features are available 0.472
And I shutdown Tails and wait for the computer to power off 7.610
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.140
After features/support/hooks.rb:331 0.510
After features/support/hooks.rb:100 0.011
Tags: @product
2:36.845
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.946
And I log in to a new session 17.028
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.585
And I plug USB drive "to_upgrade" 2.661
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.403
Then the running Tails is installed on USB drive "to_upgrade" 20.785
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:331 4.182
After features/support/hooks.rb:100 0.000
Tags: @product
1:45.049
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.186
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:36.537
Then all tps features from the old Tails version are active 1.450
And Tails is running from USB drive "to_upgrade" 0.285
And the boot device has safe access rights 3.160
And the expected persistent files created with the old Tails version are present in the filesystem 1.225
And all persistent directories from the old Tails version have safe access rights 2.202
After features/support/hooks.rb:331 0.858
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:51.925
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 12.208
And no SquashFS delta is installed 0.087
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.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.263
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.496
When the network is plugged 0.103
And Tor is ready 12.983
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.934
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.823
Given I shutdown Tails and wait for the computer to power off 11.082
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:42.301
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.199
And the file system changes introduced in version 6.2~testoverlayfs are present 0.280
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.162
# 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.261
When the network is plugged 0.056
And Tor is ready 12.304
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.621
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.342
Given I shutdown Tails and wait for the computer to power off 4.927
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:36.606
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.094
And the file system changes introduced in version 6.3~testoverlayfs are present 0.435
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.157
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.209
When the network is plugged 0.056
And Tor is ready 11.527
Then the Upgrader considers the system as up-to-date 0.201
# 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.288
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.438
After features/support/hooks.rb:331 1.183
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
23.092
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 10.282
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.241
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.060
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 11.727
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.649
After features/support/hooks.rb:331 1.220
After features/support/hooks.rb:100 0.000