Project Number Date
test_Tails_ISO_devel 3798 01 May 2025, 13:44

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 24:40.040 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:0.686
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.624
And I create a 7200 MiB disk named "old" 0.223
And I plug USB drive "old" 1.162
And I write an old version of the Tails USB image to disk "old" 41.149
When I start Tails from USB drive "old" with network unplugged 2:12.503
Then the boot device has safe access rights 3.708
And Tails is running from USB drive "old" 0.487
And there is no persistence partition on USB drive "old" 0.109
And process "udev-watchdog" is running 0.127
And udev-watchdog is monitoring the correct device 0.341
And I unplug USB drive "old" 0.249
After features/support/hooks.rb:330 7.122
After features/support/hooks.rb:100 0.019
Tags: @product
2:43.968
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.812
And I start Tails from USB drive "old" with network unplugged and I login 1:42.736
Then Tails is running from USB drive "old" 0.483
And I create a persistent partition 44.213
And I take note of which tps features are available 6.040
Then a Tails persistence partition exists on USB drive "old" 0.936
And I shutdown Tails and wait for the computer to power off 8.745
After features/support/hooks.rb:330 0.178
After features/support/hooks.rb:100 0.008
Tags: @product
4:5.781
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 1.061
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:12.806
Then Tails is running from USB drive "old" 0.793
And all tps features are active 7.635
When I write some files expected to persist 2.346
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.452
And all persistence configuration files have safe access rights 0.440
And all persistent directories from the old Tails version have safe access rights 3.206
And I take note of which tps features are available 2.339
And I shutdown Tails and wait for the computer to power off 6.493
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 28.205
After features/support/hooks.rb:330 0.202
After features/support/hooks.rb:100 0.011
Tags: @product
3:11.398
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 26.508
And I log in to a new session 24.564
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.455
And I plug USB drive "to_upgrade" 2.492
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.455
Then the running Tails is installed on USB drive "to_upgrade" 31.339
And I unplug USB drive "to_upgrade" 0.326
And I unplug USB drive "__internal" 0.256
After features/support/hooks.rb:330 3.058
After features/support/hooks.rb:100 0.000
Tags: @product
2:45.561
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.761
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:32.529
Then all tps features from the old Tails version are active 1.927
And Tails is running from USB drive "to_upgrade" 0.387
And the boot device has safe access rights 3.856
And the expected persistent files created with the old Tails version are present in the filesystem 1.711
And all persistent directories from the old Tails version have safe access rights 4.387
After features/support/hooks.rb:330 1.676
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
8:10.734
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 18.353
And no SquashFS delta is installed 0.192
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.467
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.480
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.533
When the network is plugged 0.104
And Tor is ready 22.639
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.903
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.920
Given I shutdown Tails and wait for the computer to power off 11.692
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:34.266
Then Tails is running version 6.2~testoverlayfs 0.035
And all tps features are active 2.992
And the file system changes introduced in version 6.2~testoverlayfs are present 0.413
And only the 6.2~testoverlayfs SquashFS delta is installed 0.089
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.339
# 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.429
When the network is plugged 0.099
And Tor is ready 21.021
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.763
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.471
Given I shutdown Tails and wait for the computer to power off 6.583
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:41.475
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 3.905
And the file system changes introduced in version 6.3~testoverlayfs are present 0.714
And only the 6.3~testoverlayfs SquashFS delta is installed 0.109
# 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.530
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.441
When the network is plugged 0.300
And Tor is ready 24.006
Then the Upgrader considers the system as up-to-date 0.375
# 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.322
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.681
After features/support/hooks.rb:330 0.836
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
41.909
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.421
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.359
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.120
But a current signing key is available on our website 0.000
When the network is plugged 0.137
And Tor is ready 21.196
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.610
After features/support/hooks.rb:330 0.880
After features/support/hooks.rb:100 0.000