Project Number Date
test_Tails_ISO_devel 4048 02 Nov 2025, 12:12

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:7.373 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:52.732
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.187
And I create a 7200 MiB disk named "old" 0.062
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 31.444
When I start Tails from USB drive "old" with network unplugged 1:16.160
Then the boot device has safe access rights 2.893
And Tails is running from USB drive "old" 0.324
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.281
And I unplug USB drive "old" 0.204
After features/support/hooks.rb:331 3.529
After features/support/hooks.rb:100 0.009
Tags: @product
2:4.771
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.158
And I start Tails from USB drive "old" with network unplugged and I login 1:26.002
Then Tails is running from USB drive "old" 0.299
And I create a persistent partition 28.843
And I take note of which tps features are available 1.146
Then a Tails persistence partition exists on USB drive "old" 0.706
And I shutdown Tails and wait for the computer to power off 7.613
After features/support/hooks.rb:331 0.213
After features/support/hooks.rb:100 0.010
Tags: @product
2:7.078
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.173
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:34.271
Then Tails is running from USB drive "old" 0.282
And all tps features are active 1.704
When I write some files expected to persist 1.415
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.181
And all persistence configuration files have safe access rights 0.416
And all persistent directories from the old Tails version have safe access rights 2.336
And I take note of which tps features are available 0.485
And I shutdown Tails and wait for the computer to power off 7.896
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.914
After features/support/hooks.rb:331 0.336
After features/support/hooks.rb:100 0.009
Tags: @product
2:49.635
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 without a persistent partition and stopped at Tails Greeter's login screen 12.177
And I log in to a new session 16.709
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.506
And I plug USB drive "to_upgrade" 2.412
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:56.439
Then the running Tails is installed on USB drive "to_upgrade" 19.969
And I unplug USB drive "to_upgrade" 0.199
And I unplug USB drive "__internal" 0.221
After features/support/hooks.rb:331 4.002
After features/support/hooks.rb:100 0.000
Tags: @product
1:46.011
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.166
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:37.094
Then all tps features from the old Tails version are active 1.485
And Tails is running from USB drive "to_upgrade" 0.330
And the boot device has safe access rights 3.145
And the expected persistent files created with the old Tails version are present in the filesystem 1.370
And all persistent directories from the old Tails version have safe access rights 2.416
After features/support/hooks.rb:331 0.952
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
5:4.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 12.056
And no SquashFS delta is installed 0.057
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.240
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.283
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.407
When the network is plugged 0.081
And Tor is ready 13.437
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.656
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.648
Given I shutdown Tails and wait for the computer to power off 10.841
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:40.032
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 1.974
And the file system changes introduced in version 6.2~testoverlayfs are present 0.313
And only the 6.2~testoverlayfs SquashFS delta is installed 0.053
# 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.267
When the network is plugged 0.051
And Tor is ready 12.288
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.624
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.865
Given I shutdown Tails and wait for the computer to power off 7.909
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:37.744
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.075
And the file system changes introduced in version 6.3~testoverlayfs are present 0.452
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.155
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.253
When the network is plugged 0.052
And Tor is ready 10.600
Then the Upgrader considers the system as up-to-date 10.771
# 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.642
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.480
After features/support/hooks.rb:331 0.999
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
22.539
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.108
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.330
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.069
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 11.327
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.578
After features/support/hooks.rb:331 0.807
After features/support/hooks.rb:100 0.000