Project Number Date
test_Tails_ISO_stable 5671 23 May 2025, 08:57

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 20:5.816 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
1:58.529
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.220
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 30.298
When I start Tails from USB drive "old" with network unplugged 1:22.614
Then the boot device has safe access rights 3.286
And Tails is running from USB drive "old" 0.317
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.318
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:330 3.579
After features/support/hooks.rb:100 0.010
Tags: @product
2:16.887
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login 1:33.473
Then Tails is running from USB drive "old" 0.348
And I create a persistent partition 31.287
And I take note of which tps features are available 2.233
Then a Tails persistence partition exists on USB drive "old" 0.849
And I shutdown Tails and wait for the computer to power off 8.485
After features/support/hooks.rb:330 0.178
After features/support/hooks.rb:100 0.008
Tags: @product
2:52.461
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.933
Then Tails is running from USB drive "old" 0.604
And all tps features are active 2.093
When I write some files expected to persist 1.682
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.243
And all persistence configuration files have safe access rights 0.395
And all persistent directories from the old Tails version have safe access rights 3.194
And I take note of which tps features are available 0.401
And I shutdown Tails and wait for the computer to power off 6.388
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.316
After features/support/hooks.rb:330 0.148
After features/support/hooks.rb:100 0.007
Tags: @product
2:29.251
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 without a persistent partition and stopped at Tails Greeter's login screen 10.383
And I log in to a new session 17.628
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.540
And I plug USB drive "to_upgrade" 2.569
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.283
Then the running Tails is installed on USB drive "to_upgrade" 22.429
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:330 3.612
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.856
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.325
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.756
Then all tps features from the old Tails version are active 2.173
And Tails is running from USB drive "to_upgrade" 0.404
And the boot device has safe access rights 4.038
And the expected persistent files created with the old Tails version are present in the filesystem 1.551
And all persistent directories from the old Tails version have safe access rights 2.606
After features/support/hooks.rb:330 1.393
After features/support/hooks.rb:100 0.008
7:33.179
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.099
And no SquashFS delta is installed 0.096
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.592
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.105
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.442
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.466
When the network is plugged 0.070
And Tor is ready 47.659
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.618
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.910
Given I shutdown Tails and wait for the computer to power off 10.949
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.827
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.329
And the file system changes introduced in version 6.2~testoverlayfs are present 0.362
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.360
# 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.354
When the network is plugged 0.239
And Tor is ready 48.451
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.585
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.265
Given I shutdown Tails and wait for the computer to power off 4.315
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.826
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.090
And the file system changes introduced in version 6.3~testoverlayfs are present 0.617
And only the 6.3~testoverlayfs SquashFS delta is installed 0.124
# 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.331
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.357
When the network is plugged 0.065
And Tor is ready 19.378
Then the Upgrader considers the system as up-to-date 0.314
# 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.341
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.526
After features/support/hooks.rb:330 0.715
After features/support/hooks.rb:100 0.031
39.649
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.444
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.487
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the signing key used by the Upgrader is outdated 0.083
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 19.075
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.416
After features/support/hooks.rb:330 0.777
After features/support/hooks.rb:100 0.000