Project Number Date
test_Tails_ISO_devel 3889 27 Jun 2025, 14:19

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 26:34.961 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:57.869
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.286
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 38.697
When I start Tails from USB drive "old" with network unplugged 2:12.089
Then the boot device has safe access rights 4.636
And Tails is running from USB drive "old" 0.397
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.312
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:330 3.816
After features/support/hooks.rb:100 0.044
Tags: @product
3:6.305
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.306
And I start Tails from USB drive "old" with network unplugged and I login 2:11.634
Then Tails is running from USB drive "old" 1.193
And I create a persistent partition 40.213
And I take note of which tps features are available 2.662
Then a Tails persistence partition exists on USB drive "old" 0.796
And I shutdown Tails and wait for the computer to power off 9.498
After features/support/hooks.rb:330 0.552
After features/support/hooks.rb:100 0.031
Tags: @product
4:11.856
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.026
Given a computer 2.145
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:10.296
Then Tails is running from USB drive "old" 0.481
And all tps features are active 2.456
When I write some files expected to persist 5.530
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.662
And all persistence configuration files have safe access rights 0.720
And all persistent directories from the old Tails version have safe access rights 4.954
And I take note of which tps features are available 0.484
And I shutdown Tails and wait for the computer to power off 6.682
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 37.440
After features/support/hooks.rb:330 0.205
After features/support/hooks.rb:100 0.011
Tags: @product
3:14.104
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 without a persistent partition and stopped at Tails Greeter's login screen 17.991
And I log in to a new session 22.905
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.447
And I plug USB drive "to_upgrade" 5.675
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.758
Then the running Tails is installed on USB drive "to_upgrade" 35.596
And I unplug USB drive "to_upgrade" 0.331
And I unplug USB drive "__internal" 0.397
After features/support/hooks.rb:330 7.223
After features/support/hooks.rb:100 0.000
Tags: @product
3:12.325
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.058
Given a computer 0.246
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:53.540
Then all tps features from the old Tails version are active 2.185
And Tails is running from USB drive "to_upgrade" 0.381
And the boot device has safe access rights 4.819
And the expected persistent files created with the old Tails version are present in the filesystem 2.175
And all persistent directories from the old Tails version have safe access rights 8.976
After features/support/hooks.rb:330 1.534
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
8:58.262
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 17.243
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.398
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.134
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.639
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.615
When the network is plugged 0.108
And Tor is ready 27.008
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 11.429
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 18.780
Given I shutdown Tails and wait for the computer to power off 9.041
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:46.311
Then Tails is running version 6.2~testoverlayfs 0.219
And all tps features are active 4.523
And the file system changes introduced in version 6.2~testoverlayfs are present 0.422
And only the 6.2~testoverlayfs SquashFS delta is installed 0.102
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.461
# 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.324
When the network is plugged 0.078
And Tor is ready 22.460
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.513
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 14.324
Given I shutdown Tails and wait for the computer to power off 7.047
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:48.483
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 3.475
And the file system changes introduced in version 6.3~testoverlayfs are present 0.547
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.346
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.315
When the network is plugged 0.070
And Tor is ready 26.212
Then the Upgrader considers the system as up-to-date 0.742
# 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 26.014
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.695
After features/support/hooks.rb:330 0.784
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
54.237
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 11.285
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 2.782
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.391
And the signing key used by the Upgrader is outdated 0.265
But a current signing key is available on our website 0.000
When the network is plugged 0.137
And Tor is ready 27.332
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 12.042
After features/support/hooks.rb:330 1.862
After features/support/hooks.rb:100 0.000