Project Number Date
test_Tails_ISO_stable 5923 31 Oct 2025, 14:23

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:45.702 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:58.251
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.209
And I create a 7200 MiB disk named "old" 0.066
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 25.540
When I start Tails from USB drive "old" with network unplugged 1:27.170
Then the boot device has safe access rights 3.229
And Tails is running from USB drive "old" 0.334
And there is no persistence partition on USB drive "old" 0.114
And process "udev-watchdog" is running 0.071
And udev-watchdog is monitoring the correct device 0.253
And I unplug USB drive "old" 0.213
After features/support/hooks.rb:331 3.473
After features/support/hooks.rb:100 0.009
Tags: @product
2:5.150
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login 1:25.326
Then Tails is running from USB drive "old" 0.305
And I create a persistent partition 29.602
And I take note of which tps features are available 1.264
Then a Tails persistence partition exists on USB drive "old" 0.803
And I shutdown Tails and wait for the computer to power off 7.642
After features/support/hooks.rb:331 0.308
After features/support/hooks.rb:100 0.009
Tags: @product
2:14.629
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.222
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:40.213
Then Tails is running from USB drive "old" 0.262
And all tps features are active 2.015
When I write some files expected to persist 1.649
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.239
And all persistence configuration files have safe access rights 0.326
And all persistent directories from the old Tails version have safe access rights 2.666
And I take note of which tps features are available 0.564
And I shutdown Tails and wait for the computer to power off 7.855
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.613
After features/support/hooks.rb:331 0.333
After features/support/hooks.rb:100 0.009
Tags: @product
2:23.950
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 9.713
And I log in to a new session 16.154
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.038
And I plug USB drive "to_upgrade" 2.342
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.588
Then the running Tails is installed on USB drive "to_upgrade" 19.675
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.233
After features/support/hooks.rb:331 3.969
After features/support/hooks.rb:100 0.000
Tags: @product
1:48.094
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.240
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:38.801
Then all tps features from the old Tails version are active 1.494
And Tails is running from USB drive "to_upgrade" 0.283
And the boot device has safe access rights 3.334
And the expected persistent files created with the old Tails version are present in the filesystem 1.539
And all persistent directories from the old Tails version have safe access rights 2.400
After features/support/hooks.rb:331 0.794
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
4:52.093
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.993
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.304
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.110
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.280
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.413
When the network is plugged 0.064
And Tor is ready 13.842
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.705
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.346
Given I shutdown Tails and wait for the computer to power off 8.051
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:39.353
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.151
And the file system changes introduced in version 6.2~testoverlayfs are present 0.285
And only the 6.2~testoverlayfs SquashFS delta is installed 0.088
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.206
# 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.209
When the network is plugged 0.072
And Tor is ready 11.341
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.755
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.368
Given I shutdown Tails and wait for the computer to power off 7.639
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:39.120
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 2.195
And the file system changes introduced in version 6.3~testoverlayfs are present 0.400
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.166
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.399
When the network is plugged 0.096
And Tor is ready 12.116
Then the Upgrader considers the system as up-to-date 0.204
# 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.146
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.497
After features/support/hooks.rb:331 1.053
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
23.532
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 9.937
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.317
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.135
But a current signing key is available on our website 0.000
When the network is plugged 0.094
And Tor is ready 11.098
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.892
After features/support/hooks.rb:331 1.074
After features/support/hooks.rb:100 0.000