Project Number Date
test_Tails_ISO_test-suite-options 9 25 Jun 2025, 22:19

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 30:29.616 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:16.004
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.340
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.083
And I write an old version of the Tails USB image to disk "old" 50.910
When I start Tails from USB drive "old" with network unplugged 2:15.096
Then the boot device has safe access rights 7.370
And Tails is running from USB drive "old" 0.390
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.118
And udev-watchdog is monitoring the correct device 0.321
And I unplug USB drive "old" 0.240
After features/support/hooks.rb:330 16.003
After features/support/hooks.rb:100 0.024
Tags: @product
3:28.777
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.282
And I start Tails from USB drive "old" with network unplugged and I login 2:19.571
Then Tails is running from USB drive "old" 0.926
And I create a persistent partition 49.786
And I take note of which tps features are available 5.346
Then a Tails persistence partition exists on USB drive "old" 2.716
And I shutdown Tails and wait for the computer to power off 10.147
After features/support/hooks.rb:330 0.216
After features/support/hooks.rb:100 0.013
Tags: @product
4:47.697
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given a computer 0.239
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:38.149
Then Tails is running from USB drive "old" 0.920
And all tps features are active 3.940
When I write some files expected to persist 9.430
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.689
And all persistence configuration files have safe access rights 0.707
And all persistent directories from the old Tails version have safe access rights 3.454
And I take note of which tps features are available 0.723
And I shutdown Tails and wait for the computer to power off 12.008
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 37.433
After features/support/hooks.rb:330 0.546
After features/support/hooks.rb:100 0.036
Tags: @product
3:45.938
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 without a persistent partition and stopped at Tails Greeter's login screen 12.662
And I log in to a new session 38.249
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.018
And I plug USB drive "to_upgrade" 5.262
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:7.483
Then the running Tails is installed on USB drive "to_upgrade" 39.797
And I unplug USB drive "to_upgrade" 0.233
And I unplug USB drive "__internal" 0.230
After features/support/hooks.rb:330 1.921
After features/support/hooks.rb:100 0.000
Tags: @product
4:3.529
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.216
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:41.373
Then all tps features from the old Tails version are active 2.848
And Tails is running from USB drive "to_upgrade" 0.415
And the boot device has safe access rights 13.598
And the expected persistent files created with the old Tails version are present in the filesystem 1.606
And all persistent directories from the old Tails version have safe access rights 3.470
After features/support/hooks.rb:330 0.950
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
10:12.844
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 30.378
And no SquashFS delta is installed 0.869
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.222
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.128
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.524
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.647
When the network is plugged 0.083
And Tor is ready 41.572
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.958
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 32.105
Given I shutdown Tails and wait for the computer to power off 20.441
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:15.707
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 3.713
And the file system changes introduced in version 6.2~testoverlayfs are present 0.314
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.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.309
When the network is plugged 0.081
And Tor is ready 25.139
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 9.496
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 21.299
Given I shutdown Tails and wait for the computer to power off 6.958
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:33.643
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 3.353
And the file system changes introduced in version 6.3~testoverlayfs are present 0.476
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.333
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.235
When the network is plugged 0.072
And Tor is ready 22.882
Then the Upgrader considers the system as up-to-date 11.697
# 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 21.532
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.134
After features/support/hooks.rb:330 0.729
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
54.823
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 16.274
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.417
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.069
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 26.019
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 10.909
After features/support/hooks.rb:330 1.716
After features/support/hooks.rb:100 0.000