Project Number Date
test_Tails_ISO_stable 5983 04 Dec 2025, 19:40

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:10.248 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:44.966
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.229
And I create a 7200 MiB disk named "old" 0.060
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 28.565
When I start Tails from USB drive "old" with network unplugged 1:10.207
Then the boot device has safe access rights 3.750
And Tails is running from USB drive "old" 0.444
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.063
And udev-watchdog is monitoring the correct device 0.308
And I unplug USB drive "old" 0.225
After features/support/hooks.rb:331 3.886
After features/support/hooks.rb:100 0.010
Tags: @product
2:9.434
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:26.643
Then Tails is running from USB drive "old" 0.301
And I create a persistent partition 32.253
And I take note of which tps features are available 1.146
Then a Tails persistence partition exists on USB drive "old" 0.771
And I shutdown Tails and wait for the computer to power off 8.128
After features/support/hooks.rb:331 0.645
After features/support/hooks.rb:100 0.012
Tags: @product
2:14.605
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:40.627
Then Tails is running from USB drive "old" 0.310
And all tps features are active 2.021
When I write some files expected to persist 1.544
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.198
And all persistence configuration files have safe access rights 0.387
And all persistent directories from the old Tails version have safe access rights 2.291
And I take note of which tps features are available 0.443
And I shutdown Tails and wait for the computer to power off 7.675
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.902
After features/support/hooks.rb:331 0.427
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.140
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 10.547
And I log in to a new session 10.823
And I clone USB drive "old" to a new USB drive "to_upgrade" 7.971
And I plug USB drive "to_upgrade" 2.473
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.925
Then the running Tails is installed on USB drive "to_upgrade" 20.955
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.238
After features/support/hooks.rb:331 3.748
After features/support/hooks.rb:100 0.000
Tags: @product
1:40.772
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.179
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:20.167
Then all tps features from the old Tails version are active 12.662
And Tails is running from USB drive "to_upgrade" 0.355
And the boot device has safe access rights 3.635
And the expected persistent files created with the old Tails version are present in the filesystem 1.407
And all persistent directories from the old Tails version have safe access rights 2.364
After features/support/hooks.rb:331 0.726
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
4:25.256
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 11.408
And no SquashFS delta is installed 0.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.283
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.085
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.308
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.427
When the network is plugged 0.054
And Tor is ready 14.168
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.643
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.832
Given I shutdown Tails and wait for the computer to power off 7.726
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.346
Then Tails is running version 6.2~testoverlayfs 0.030
And all tps features are active 2.811
And the file system changes introduced in version 6.2~testoverlayfs are present 0.441
And only the 6.2~testoverlayfs SquashFS delta is installed 0.136
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.255
# 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.411
When the network is plugged 0.055
And Tor is ready 12.874
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.049
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.671
Given I shutdown Tails and wait for the computer to power off 5.002
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:26.047
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.527
And the file system changes introduced in version 6.3~testoverlayfs are present 0.445
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.171
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.473
When the network is plugged 0.254
And Tor is ready 12.839
Then the Upgrader considers the system as up-to-date 0.168
# 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 6.625
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.501
After features/support/hooks.rb:331 1.205
After features/support/hooks.rb:100 0.042
Tags: @product @automatic_upgrade
22.072
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.017
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.061
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.296
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.071
But a current signing key is available on our website 0.000
When the network is plugged 0.047
And Tor is ready 10.867
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.675
After features/support/hooks.rb:331 0.840
After features/support/hooks.rb:100 0.000