Project Number Date
test_Tails_ISO_codespell 2 18 Jun 2025, 02:48

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 27:37.189 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:58.431
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given a computer 0.245
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 40.629
When I start Tails from USB drive "old" with network unplugged 2:7.783
Then the boot device has safe access rights 7.428
And Tails is running from USB drive "old" 0.533
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.344
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:330 7.507
After features/support/hooks.rb:100 0.010
Tags: @product
3:9.859
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login 2:10.682
Then Tails is running from USB drive "old" 0.684
And I create a persistent partition 42.158
And I take note of which tps features are available 2.547
Then a Tails persistence partition exists on USB drive "old" 1.088
And I shutdown Tails and wait for the computer to power off 12.503
After features/support/hooks.rb:330 0.153
After features/support/hooks.rb:100 0.011
Tags: @product
4:8.626
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.279
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:6.193
Then Tails is running from USB drive "old" 0.474
And all tps features are active 2.568
When I write some files expected to persist 3.761
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.632
And all persistence configuration files have safe access rights 1.020
And all persistent directories from the old Tails version have safe access rights 5.805
And I take note of which tps features are available 0.694
And I shutdown Tails and wait for the computer to power off 7.120
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 40.077
After features/support/hooks.rb:330 0.242
After features/support/hooks.rb:100 0.013
Tags: @product
3:27.290
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 without a persistent partition and stopped at Tails Greeter's login screen 15.023
And I log in to a new session 26.082
And I clone USB drive "old" to a new USB drive "to_upgrade" 8.646
And I plug USB drive "to_upgrade" 4.123
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:51.777
Then the running Tails is installed on USB drive "to_upgrade" 38.666
And I unplug USB drive "to_upgrade" 2.609
And I unplug USB drive "__internal" 0.361
After features/support/hooks.rb:330 3.458
After features/support/hooks.rb:100 0.000
Tags: @product
3:6.920
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.263
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:49.833
Then all tps features from the old Tails version are active 7.863
And Tails is running from USB drive "to_upgrade" 0.383
And the boot device has safe access rights 4.515
And the expected persistent files created with the old Tails version are present in the filesystem 1.352
And all persistent directories from the old Tails version have safe access rights 2.707
After features/support/hooks.rb:330 1.996
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
9:55.035
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 21.758
And no SquashFS delta is installed 1.218
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 3.999
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.509
And the file system changes introduced in version 6.2~testoverlayfs are not present 1.235
And the file system changes introduced in version 6.3~testoverlayfs are not present 1.204
When the network is plugged 0.205
And Tor is ready 24.320
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 14.180
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.445
Given I shutdown Tails and wait for the computer to power off 15.396
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:55.116
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 3.138
And the file system changes introduced in version 6.2~testoverlayfs are present 0.356
And only the 6.2~testoverlayfs SquashFS delta is installed 0.090
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.332
# 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.331
When the network is plugged 0.061
And Tor is ready 32.071
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.894
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 19.357
Given I shutdown Tails and wait for the computer to power off 6.876
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:12.020
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 2.343
And the file system changes introduced in version 6.3~testoverlayfs are present 0.655
And only the 6.3~testoverlayfs SquashFS delta is installed 0.083
# 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.750
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.479
When the network is plugged 0.125
And Tor is ready 27.919
Then the Upgrader considers the system as up-to-date 1.054
# 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 25.934
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.523
After features/support/hooks.rb:330 0.744
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
51.025
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 13.637
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.903
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.097
And the signing key used by the Upgrader is outdated 0.139
But a current signing key is available on our website 0.000
When the network is plugged 0.101
And Tor is ready 22.605
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 13.542
After features/support/hooks.rb:330 1.850
After features/support/hooks.rb:100 0.000