Project Number Date
test_Tails_ISO_stable 5532 26 Mar 2025, 16:01

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 22:55.541 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:56.939
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.033
Given a computer 0.305
And I create a 7200 MiB disk named "old" 0.077
And I plug USB drive "old" 1.067
And I write an old version of the Tails USB image to disk "old" 1:7.801
When I start Tails from USB drive "old" with network unplugged 1:43.025
Then the boot device has safe access rights 3.479
And Tails is running from USB drive "old" 0.418
And there is no persistence partition on USB drive "old" 0.101
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.370
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:330 7.387
After features/support/hooks.rb:100 0.009
Tags: @product
2:18.210
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.303
And I start Tails from USB drive "old" with network unplugged and I login 1:32.023
Then Tails is running from USB drive "old" 0.415
And I create a persistent partition 33.469
And I take note of which tps features are available 2.272
Then a Tails persistence partition exists on USB drive "old" 0.984
And I shutdown Tails and wait for the computer to power off 8.742
After features/support/hooks.rb:330 0.220
After features/support/hooks.rb:100 0.010
Tags: @product
3:30.691
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.243
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:48.758
Then Tails is running from USB drive "old" 0.426
And all tps features are active 2.862
When I write some files expected to persist 2.092
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.254
And all persistence configuration files have safe access rights 0.509
And all persistent directories from the old Tails version have safe access rights 2.989
And I take note of which tps features are available 0.544
And I shutdown Tails and wait for the computer to power off 6.746
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.263
After features/support/hooks.rb:330 0.169
After features/support/hooks.rb:100 0.009
Tags: @product
2:54.120
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 13.669
And I log in to a new session 20.694
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.753
And I plug USB drive "to_upgrade" 2.485
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.396
Then the running Tails is installed on USB drive "to_upgrade" 32.533
And I unplug USB drive "to_upgrade" 0.243
And I unplug USB drive "__internal" 0.344
After features/support/hooks.rb:330 2.536
After features/support/hooks.rb:100 0.000
Tags: @product
2:45.938
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.314
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:34.972
Then all tps features from the old Tails version are active 2.097
And Tails is running from USB drive "to_upgrade" 0.354
And the boot device has safe access rights 3.687
And the expected persistent files created with the old Tails version are present in the filesystem 1.570
And all persistent directories from the old Tails version have safe access rights 2.941
After features/support/hooks.rb:330 1.721
After features/support/hooks.rb:100 0.021
7:49.971
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.025
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 23.342
And no SquashFS delta is installed 0.185
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.468
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.315
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.535
When the network is plugged 0.103
And Tor is ready 19.882
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.294
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 17.832
Given I shutdown Tails and wait for the computer to power off 11.741
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:21.134
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.634
And the file system changes introduced in version 6.2~testoverlayfs are present 0.366
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.299
# 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.282
When the network is plugged 0.090
And Tor is ready 19.985
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.546
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.139
Given I shutdown Tails and wait for the computer to power off 6.663
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:30.285
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 8.713
And the file system changes introduced in version 6.3~testoverlayfs are present 0.626
And only the 6.3~testoverlayfs SquashFS delta is installed 0.104
# 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.446
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.345
When the network is plugged 0.229
And Tor is ready 20.674
Then the Upgrader considers the system as up-to-date 0.372
# 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.567
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.592
After features/support/hooks.rb:330 0.720
After features/support/hooks.rb:100 0.020
39.668
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.596
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.419
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.525
But a current signing key is available on our website 0.000
When the network is plugged 1.304
And Tor is ready 17.375
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.384
After features/support/hooks.rb:330 1.964
After features/support/hooks.rb:100 0.000