Project Number Date
test_Tails_ISO_stable 5565 10 Apr 2025, 14:10

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:10.170 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:12.458
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.211
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 30.034
When I start Tails from USB drive "old" with network unplugged 1:36.961
Then the boot device has safe access rights 3.076
And Tails is running from USB drive "old" 0.350
And there is no persistence partition on USB drive "old" 0.109
And process "udev-watchdog" is running 0.126
And udev-watchdog is monitoring the correct device 0.307
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:330 3.747
After features/support/hooks.rb:100 0.010
Tags: @product
2:8.451
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login 1:22.963
Then Tails is running from USB drive "old" 0.357
And I create a persistent partition 33.554
And I take note of which tps features are available 2.090
Then a Tails persistence partition exists on USB drive "old" 0.803
And I shutdown Tails and wait for the computer to power off 8.498
After features/support/hooks.rb:330 0.208
After features/support/hooks.rb:100 0.009
Tags: @product
2:55.721
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.881
Then Tails is running from USB drive "old" 0.371
And all tps features are active 2.203
When I write some files expected to persist 1.654
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.232
And all persistence configuration files have safe access rights 0.423
And all persistent directories from the old Tails version have safe access rights 2.468
And I take note of which tps features are available 0.353
And I shutdown Tails and wait for the computer to power off 4.456
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.484
After features/support/hooks.rb:330 0.190
After features/support/hooks.rb:100 0.010
Tags: @product
2:30.244
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.811
And I log in to a new session 18.586
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.884
And I plug USB drive "to_upgrade" 2.419
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.911
Then the running Tails is installed on USB drive "to_upgrade" 21.152
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.266
After features/support/hooks.rb:330 0.890
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.521
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.250
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.457
Then all tps features from the old Tails version are active 1.600
And Tails is running from USB drive "to_upgrade" 0.433
And the boot device has safe access rights 3.388
And the expected persistent files created with the old Tails version are present in the filesystem 1.791
And all persistent directories from the old Tails version have safe access rights 2.601
After features/support/hooks.rb:330 1.235
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:33.170
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 12.015
And no SquashFS delta is installed 0.347
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.501
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.089
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.497
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.496
When the network is plugged 0.067
And Tor is ready 20.702
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.288
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.438
Given I shutdown Tails and wait for the computer to power off 8.895
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.283
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.098
And the file system changes introduced in version 6.2~testoverlayfs are present 0.291
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.318
# 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.260
When the network is plugged 0.057
And Tor is ready 19.178
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.392
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.617
Given I shutdown Tails and wait for the computer to power off 6.319
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.010
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.092
And the file system changes introduced in version 6.3~testoverlayfs are present 0.518
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.319
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.271
When the network is plugged 0.225
And Tor is ready 19.119
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.460
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.492
After features/support/hooks.rb:330 0.947
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
33.602
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 9.260
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.390
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.115
But a current signing key is available on our website 0.000
When the network is plugged 0.060
And Tor is ready 17.078
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.637
After features/support/hooks.rb:330 1.545
After features/support/hooks.rb:100 0.000