Project Number Date
test_Tails_ISO_stable 5712 12 Jun 2025, 12:59

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 20:18.817 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:15.893
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.224
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.090
And I write an old version of the Tails USB image to disk "old" 34.490
When I start Tails from USB drive "old" with network unplugged 1:35.784
Then the boot device has safe access rights 3.230
And Tails is running from USB drive "old" 0.356
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.119
And udev-watchdog is monitoring the correct device 0.291
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:330 7.064
After features/support/hooks.rb:100 0.014
Tags: @product
2:15.175
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login 1:32.268
Then Tails is running from USB drive "old" 0.338
And I create a persistent partition 31.367
And I take note of which tps features are available 1.825
Then a Tails persistence partition exists on USB drive "old" 0.769
And I shutdown Tails and wait for the computer to power off 8.403
After features/support/hooks.rb:330 0.126
After features/support/hooks.rb:100 0.008
Tags: @product
3:13.919
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.226
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:35.000
Then Tails is running from USB drive "old" 1.003
And all tps features are active 2.100
When I write some files expected to persist 2.167
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.244
And all persistence configuration files have safe access rights 0.442
And all persistent directories from the old Tails version have safe access rights 2.665
And I take note of which tps features are available 0.479
And I shutdown Tails and wait for the computer to power off 4.688
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.902
After features/support/hooks.rb:330 0.186
After features/support/hooks.rb:100 0.013
Tags: @product
2:37.791
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.064
And I log in to a new session 20.365
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.702
And I plug USB drive "to_upgrade" 2.442
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.579
Then the running Tails is installed on USB drive "to_upgrade" 24.210
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.229
After features/support/hooks.rb:330 2.229
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.613
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.215
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.644
Then all tps features from the old Tails version are active 1.583
And Tails is running from USB drive "to_upgrade" 0.346
And the boot device has safe access rights 3.448
And the expected persistent files created with the old Tails version are present in the filesystem 1.700
And all persistent directories from the old Tails version have safe access rights 2.675
After features/support/hooks.rb:330 1.546
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:57.022
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 12.758
And no SquashFS delta is installed 0.336
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.344
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.124
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.350
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.494
When the network is plugged 0.075
And Tor is ready 19.790
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.487
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.437
Given I shutdown Tails and wait for the computer to power off 11.615
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.209
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.188
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.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.343
# 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.256
When the network is plugged 0.062
And Tor is ready 18.668
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.066
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.055
Given I shutdown Tails and wait for the computer to power off 4.655
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.808
Then Tails is running version 6.3~testoverlayfs 0.027
And all tps features are active 2.360
And the file system changes introduced in version 6.3~testoverlayfs are present 0.561
And only the 6.3~testoverlayfs SquashFS delta is installed 0.095
# 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.351
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.284
When the network is plugged 0.073
And Tor is ready 18.815
Then the Upgrader considers the system as up-to-date 0.297
# 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 15.277
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.343
After features/support/hooks.rb:330 1.469
After features/support/hooks.rb:100 0.068
Tags: @product @automatic_upgrade
37.400
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.167
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.409
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.072
But a current signing key is available on our website 0.000
When the network is plugged 0.065
And Tor is ready 19.655
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.971
After features/support/hooks.rb:330 0.682
After features/support/hooks.rb:100 0.000