Project Number Date
test_Tails_ISO_stable 5687 29 May 2025, 15:30

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 21:18.019 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:21.800
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.273
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 33.733
When I start Tails from USB drive "old" with network unplugged 1:41.762
Then the boot device has safe access rights 3.730
And Tails is running from USB drive "old" 0.416
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.389
And I unplug USB drive "old" 0.216
After features/support/hooks.rb:330 3.831
After features/support/hooks.rb:100 0.009
Tags: @product
2:23.688
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.237
And I start Tails from USB drive "old" with network unplugged and I login 1:37.457
Then Tails is running from USB drive "old" 0.380
And I create a persistent partition 33.424
And I take note of which tps features are available 2.465
Then a Tails persistence partition exists on USB drive "old" 0.817
And I shutdown Tails and wait for the computer to power off 8.905
After features/support/hooks.rb:330 0.199
After features/support/hooks.rb:100 0.010
Tags: @product
3:12.589
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.245
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:31.628
Then Tails is running from USB drive "old" 0.465
And all tps features are active 2.146
When I write some files expected to persist 1.809
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.236
And all persistence configuration files have safe access rights 0.549
And all persistent directories from the old Tails version have safe access rights 3.664
And I take note of which tps features are available 0.477
And I shutdown Tails and wait for the computer to power off 6.404
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.962
After features/support/hooks.rb:330 0.144
After features/support/hooks.rb:100 0.011
Tags: @product
2:48.361
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 15.089
And I log in to a new session 21.467
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.803
And I plug USB drive "to_upgrade" 2.485
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.921
Then the running Tails is installed on USB drive "to_upgrade" 30.134
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.249
After features/support/hooks.rb:330 2.601
After features/support/hooks.rb:100 0.000
Tags: @product
2:29.265
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.584
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:18.636
Then all tps features from the old Tails version are active 1.736
And Tails is running from USB drive "to_upgrade" 0.370
And the boot device has safe access rights 3.827
And the expected persistent files created with the old Tails version are present in the filesystem 1.430
And all persistent directories from the old Tails version have safe access rights 2.678
After features/support/hooks.rb:330 1.577
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
7:21.170
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 13.746
And no SquashFS delta is installed 0.098
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.393
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.313
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.498
When the network is plugged 0.077
And Tor is ready 25.869
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.492
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 15.516
Given I shutdown Tails and wait for the computer to power off 9.129
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.926
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 2.301
And the file system changes introduced in version 6.2~testoverlayfs are present 0.425
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.317
# 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.405
When the network is plugged 0.087
And Tor is ready 19.220
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.603
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.432
Given I shutdown Tails and wait for the computer to power off 4.627
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.918
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.103
And the file system changes introduced in version 6.3~testoverlayfs are present 0.581
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.341
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.340
When the network is plugged 0.119
And Tor is ready 21.155
Then the Upgrader considers the system as up-to-date 11.179
# 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 16.695
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.010
After features/support/hooks.rb:330 0.688
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
41.143
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.827
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.359
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.072
But a current signing key is available on our website 0.000
When the network is plugged 0.083
And Tor is ready 19.789
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.958
After features/support/hooks.rb:330 3.458
After features/support/hooks.rb:100 0.000