Project Number Date
test_Tails_ISO_devel 3822 19 May 2025, 18:00

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 23:35.323 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
3:7.300
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.306
And I create a 7200 MiB disk named "old" 0.082
And I plug USB drive "old" 1.070
And I write an old version of the Tails USB image to disk "old" 1:13.160
When I start Tails from USB drive "old" with network unplugged 1:48.183
Then the boot device has safe access rights 3.363
And Tails is running from USB drive "old" 0.400
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.114
And udev-watchdog is monitoring the correct device 0.349
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:330 3.789
After features/support/hooks.rb:100 0.009
Tags: @product
2:22.049
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.286
And I start Tails from USB drive "old" with network unplugged and I login 1:35.282
Then Tails is running from USB drive "old" 0.369
And I create a persistent partition 34.337
And I take note of which tps features are available 2.151
Then a Tails persistence partition exists on USB drive "old" 0.867
And I shutdown Tails and wait for the computer to power off 8.753
After features/support/hooks.rb:330 0.216
After features/support/hooks.rb:100 0.011
Tags: @product
3:23.503
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.264
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:41.503
Then Tails is running from USB drive "old" 0.340
And all tps features are active 2.590
When I write some files expected to persist 2.116
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.233
And all persistence configuration files have safe access rights 0.465
And all persistent directories from the old Tails version have safe access rights 2.836
And I take note of which tps features are available 0.588
And I shutdown Tails and wait for the computer to power off 6.700
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.861
After features/support/hooks.rb:330 0.478
After features/support/hooks.rb:100 0.042
Tags: @product
3:1.388
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.026
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 22.879
And I log in to a new session 22.886
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.126
And I plug USB drive "to_upgrade" 2.583
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.998
Then the running Tails is installed on USB drive "to_upgrade" 29.411
And I unplug USB drive "to_upgrade" 0.239
And I unplug USB drive "__internal" 0.263
After features/support/hooks.rb:330 3.013
After features/support/hooks.rb:100 0.000
Tags: @product
2:31.152
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.273
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:20.804
Then all tps features from the old Tails version are active 2.078
And Tails is running from USB drive "to_upgrade" 0.352
And the boot device has safe access rights 3.365
And the expected persistent files created with the old Tails version are present in the filesystem 1.499
And all persistent directories from the old Tails version have safe access rights 2.779
After features/support/hooks.rb:330 1.298
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
8:29.431
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 with a persistent partition enabled and logged in 38.022
And no SquashFS delta is installed 0.117
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.597
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.086
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.332
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.526
When the network is plugged 0.086
And Tor is ready 18.750
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.719
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.921
Given I shutdown Tails and wait for the computer to power off 9.406
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:31.991
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 3.316
And the file system changes introduced in version 6.2~testoverlayfs are present 0.315
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.290
# 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.295
When the network is plugged 0.095
And Tor is ready 49.101
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.673
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.155
Given I shutdown Tails and wait for the computer to power off 6.670
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:28.311
Then Tails is running version 6.3~testoverlayfs 0.023
And all tps features are active 2.645
And the file system changes introduced in version 6.3~testoverlayfs are present 0.642
And only the 6.3~testoverlayfs SquashFS delta is installed 0.105
# 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.410
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.422
When the network is plugged 0.088
And Tor is ready 22.089
Then the Upgrader considers the system as up-to-date 0.431
# 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 18.463
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.230
After features/support/hooks.rb:330 0.847
After features/support/hooks.rb:100 0.044
Tags: @product @automatic_upgrade
40.497
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.639
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.673
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.092
And the signing key used by the Upgrader is outdated 0.102
But a current signing key is available on our website 0.000
When the network is plugged 0.219
And Tor is ready 20.682
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.087
After features/support/hooks.rb:330 1.518
After features/support/hooks.rb:100 0.000