Project Number Date
test_Tails_ISO_stable 5720 18 Jun 2025, 08:42

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 28:13.765 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:51.982
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.205
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 45.231
When I start Tails from USB drive "old" with network unplugged 1:55.018
Then the boot device has safe access rights 8.495
And Tails is running from USB drive "old" 1.013
And there is no persistence partition on USB drive "old" 0.121
And process "udev-watchdog" is running 0.130
And udev-watchdog is monitoring the correct device 0.437
And I unplug USB drive "old" 0.229
After features/support/hooks.rb:330 4.187
After features/support/hooks.rb:100 0.010
Tags: @product
3:12.847
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login 2:4.658
Then Tails is running from USB drive "old" 0.392
And I create a persistent partition 53.281
And I take note of which tps features are available 3.262
Then a Tails persistence partition exists on USB drive "old" 1.131
And I shutdown Tails and wait for the computer to power off 9.922
After features/support/hooks.rb:330 0.275
After features/support/hooks.rb:100 0.014
Tags: @product
4:25.233
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given a computer 0.468
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:24.873
Then Tails is running from USB drive "old" 0.596
And all tps features are active 2.219
When I write some files expected to persist 2.547
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.349
And all persistence configuration files have safe access rights 0.435
And all persistent directories from the old Tails version have safe access rights 9.309
And I take note of which tps features are available 0.618
And I shutdown Tails and wait for the computer to power off 6.737
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 37.076
After features/support/hooks.rb:330 0.137
After features/support/hooks.rb:100 0.010
Tags: @product
3:17.954
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.677
And I log in to a new session 27.343
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.021
And I plug USB drive "to_upgrade" 3.004
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:55.489
Then the running Tails is installed on USB drive "to_upgrade" 36.742
And I unplug USB drive "to_upgrade" 0.388
And I unplug USB drive "__internal" 0.287
After features/support/hooks.rb:330 2.457
After features/support/hooks.rb:100 0.000
Tags: @product
3:24.979
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.221
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:6.278
Then all tps features from the old Tails version are active 6.797
And Tails is running from USB drive "to_upgrade" 0.968
And the boot device has safe access rights 5.268
And the expected persistent files created with the old Tails version are present in the filesystem 1.636
And all persistent directories from the old Tails version have safe access rights 3.808
After features/support/hooks.rb:330 1.495
After features/support/hooks.rb:100 0.075
Tags: @product @automatic_upgrade
10:11.288
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.042
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 21.694
And no SquashFS delta is installed 0.765
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.279
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.302
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.855
And the file system changes introduced in version 6.3~testoverlayfs are not present 1.090
When the network is plugged 0.344
And Tor is ready 28.754
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 13.037
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 20.393
Given I shutdown Tails and wait for the computer to power off 20.197
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:21.857
Then Tails is running version 6.2~testoverlayfs 0.027
And all tps features are active 2.485
And the file system changes introduced in version 6.2~testoverlayfs are present 0.357
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.314
# 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.288
When the network is plugged 0.098
And Tor is ready 20.879
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 13.907
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 17.670
Given I shutdown Tails and wait for the computer to power off 7.011
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:59.704
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.421
And the file system changes introduced in version 6.3~testoverlayfs are present 0.664
And only the 6.3~testoverlayfs SquashFS delta is installed 0.094
# 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.446
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.519
When the network is plugged 0.071
And Tor is ready 22.030
Then the Upgrader considers the system as up-to-date 2.413
# 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 27.259
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.957
After features/support/hooks.rb:330 0.798
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
49.478
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 15.229
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.154
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.159
And the signing key used by the Upgrader is outdated 0.163
But a current signing key is available on our website 0.000
When the network is plugged 0.317
And Tor is ready 22.119
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 10.334
After features/support/hooks.rb:330 3.695
After features/support/hooks.rb:100 0.000