Project Number Date
test_Tails_ISO_stable 5629 06 May 2025, 23:50

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 19:40.859 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:4.976
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.167
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 30.976
When I start Tails from USB drive "old" with network unplugged 1:28.511
Then the boot device has safe access rights 3.224
And Tails is running from USB drive "old" 0.322
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.304
And I unplug USB drive "old" 0.225
After features/support/hooks.rb:330 6.892
After features/support/hooks.rb:100 0.009
Tags: @product
2:25.170
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login 1:29.083
Then Tails is running from USB drive "old" 0.306
And I create a persistent partition 44.075
And I take note of which tps features are available 2.243
Then a Tails persistence partition exists on USB drive "old" 0.782
And I shutdown Tails and wait for the computer to power off 8.487
After features/support/hooks.rb:330 0.170
After features/support/hooks.rb:100 0.011
Tags: @product
3:6.973
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 "old" with network unplugged and I login with persistence enabled 2:24.823
Then Tails is running from USB drive "old" 0.362
And all tps features are active 2.104
When I write some files expected to persist 4.268
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.268
And all persistence configuration files have safe access rights 0.455
And all persistent directories from the old Tails version have safe access rights 3.605
And I take note of which tps features are available 0.417
And I shutdown Tails and wait for the computer to power off 6.489
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.998
After features/support/hooks.rb:330 0.222
After features/support/hooks.rb:100 0.014
Tags: @product
2:30.883
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 11.303
And I log in to a new session 18.777
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.025
And I plug USB drive "to_upgrade" 2.389
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.302
Then the running Tails is installed on USB drive "to_upgrade" 23.665
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.216
After features/support/hooks.rb:330 2.072
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.394
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.168
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.191
Then all tps features from the old Tails version are active 1.474
And Tails is running from USB drive "to_upgrade" 0.334
And the boot device has safe access rights 3.169
And the expected persistent files created with the old Tails version are present in the filesystem 1.509
And all persistent directories from the old Tails version have safe access rights 2.545
After features/support/hooks.rb:330 2.756
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
6:39.408
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 12.313
And no SquashFS delta is installed 0.175
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.466
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.326
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.544
When the network is plugged 0.060
And Tor is ready 19.098
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.173
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.819
Given I shutdown Tails and wait for the computer to power off 9.026
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.367
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.817
And the file system changes introduced in version 6.2~testoverlayfs are present 0.342
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.307
# 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.347
When the network is plugged 0.086
And Tor is ready 21.304
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.225
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.123
Given I shutdown Tails and wait for the computer to power off 4.399
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.312
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.830
And the file system changes introduced in version 6.3~testoverlayfs are present 0.625
And only the 6.3~testoverlayfs SquashFS delta is installed 0.089
# 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.374
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.320
When the network is plugged 0.070
And Tor is ready 19.212
Then the Upgrader considers the system as up-to-date 0.308
# 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.225
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.555
After features/support/hooks.rb:330 0.792
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
36.052
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 10.117
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.494
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.076
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 18.322
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.909
After features/support/hooks.rb:330 0.709
After features/support/hooks.rb:100 0.000