Project Number Date
test_Tails_ISO_stable 5981 03 Dec 2025, 15:49

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:24.419 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:22.799
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.158
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 35.086
When I start Tails from USB drive "old" with network unplugged 1:41.864
Then the boot device has safe access rights 3.688
And Tails is running from USB drive "old" 0.340
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.252
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:331 3.789
After features/support/hooks.rb:100 0.012
Tags: @product
2:15.169
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login 1:32.829
Then Tails is running from USB drive "old" 0.602
And I create a persistent partition 31.577
And I take note of which tps features are available 1.329
Then a Tails persistence partition exists on USB drive "old" 0.753
And I shutdown Tails and wait for the computer to power off 7.858
After features/support/hooks.rb:331 0.437
After features/support/hooks.rb:100 0.010
Tags: @product
2:22.952
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.166
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:46.071
Then Tails is running from USB drive "old" 0.552
And all tps features are active 2.196
When I write some files expected to persist 1.879
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.210
And all persistence configuration files have safe access rights 0.379
And all persistent directories from the old Tails version have safe access rights 2.605
And I take note of which tps features are available 0.545
And I shutdown Tails and wait for the computer to power off 9.387
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.957
After features/support/hooks.rb:331 0.540
After features/support/hooks.rb:100 0.008
Tags: @product
2:45.055
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 without a persistent partition and stopped at Tails Greeter's login screen 13.509
And I log in to a new session 19.736
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.609
And I plug USB drive "to_upgrade" 2.785
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.028
Then the running Tails is installed on USB drive "to_upgrade" 23.744
And I unplug USB drive "to_upgrade" 0.376
And I unplug USB drive "__internal" 0.264
After features/support/hooks.rb:331 4.216
After features/support/hooks.rb:100 0.000
Tags: @product
1:30.440
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:21.146
Then all tps features from the old Tails version are active 1.947
And Tails is running from USB drive "to_upgrade" 0.331
And the boot device has safe access rights 3.041
And the expected persistent files created with the old Tails version are present in the filesystem 1.385
And all persistent directories from the old Tails version have safe access rights 2.390
After features/support/hooks.rb:331 1.939
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
4:32.113
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 15.093
And no SquashFS delta is installed 0.114
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.293
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.393
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.609
When the network is plugged 0.057
And Tor is ready 15.324
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.805
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.239
Given I shutdown Tails and wait for the computer to power off 11.542
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:23.430
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 2.339
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.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.174
# 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.266
When the network is plugged 0.050
And Tor is ready 12.130
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.805
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.529
Given I shutdown Tails and wait for the computer to power off 8.481
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:22.041
Then Tails is running version 6.3~testoverlayfs 0.023
And all tps features are active 2.584
And the file system changes introduced in version 6.3~testoverlayfs are present 0.482
And only the 6.3~testoverlayfs SquashFS delta is installed 0.087
# 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.169
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.244
When the network is plugged 0.051
And Tor is ready 12.050
Then the Upgrader considers the system as up-to-date 0.117
# 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.694
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.442
After features/support/hooks.rb:331 1.142
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
35.889
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 with a persistent partition enabled and logged in 21.435
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.248
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.057
But a current signing key is available on our website 0.000
When the network is plugged 0.060
And Tor is ready 12.218
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.811
After features/support/hooks.rb:331 0.985
After features/support/hooks.rb:100 0.000