Project Number Date
test_Tails_ISO_devel 3855 05 Jun 2025, 13:26

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 23:19.983 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:14.515
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.246
And I create a 7200 MiB disk named "old" 0.065
And I plug USB drive "old" 1.086
And I write an old version of the Tails USB image to disk "old" 1:7.134
When I start Tails from USB drive "old" with network unplugged 2:0.114
Then the boot device has safe access rights 4.521
And Tails is running from USB drive "old" 0.485
And there is no persistence partition on USB drive "old" 0.086
And process "udev-watchdog" is running 0.112
And udev-watchdog is monitoring the correct device 0.419
And I unplug USB drive "old" 0.241
After features/support/hooks.rb:330 3.780
After features/support/hooks.rb:100 0.013
Tags: @product
2:35.146
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.332
And I start Tails from USB drive "old" with network unplugged and I login 1:46.377
Then Tails is running from USB drive "old" 0.442
And I create a persistent partition 34.945
And I take note of which tps features are available 2.812
Then a Tails persistence partition exists on USB drive "old" 1.221
And I shutdown Tails and wait for the computer to power off 9.014
After features/support/hooks.rb:330 0.246
After features/support/hooks.rb:100 0.008
Tags: @product
3:14.974
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 1.289
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:31.016
Then Tails is running from USB drive "old" 0.378
And all tps features are active 2.653
When I write some files expected to persist 2.051
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.848
And all persistence configuration files have safe access rights 0.430
And all persistent directories from the old Tails version have safe access rights 3.075
And I take note of which tps features are available 0.697
And I shutdown Tails and wait for the computer to power off 6.601
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.931
After features/support/hooks.rb:330 0.165
After features/support/hooks.rb:100 0.010
Tags: @product
3:7.623
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 30.531
And I log in to a new session 21.757
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.990
And I plug USB drive "to_upgrade" 2.466
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.642
Then the running Tails is installed on USB drive "to_upgrade" 30.768
And I unplug USB drive "to_upgrade" 0.245
And I unplug USB drive "__internal" 0.222
After features/support/hooks.rb:330 2.192
After features/support/hooks.rb:100 0.000
Tags: @product
2:39.578
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.228
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:28.564
Then all tps features from the old Tails version are active 1.968
And Tails is running from USB drive "to_upgrade" 0.400
And the boot device has safe access rights 3.768
And the expected persistent files created with the old Tails version are present in the filesystem 1.924
And all persistent directories from the old Tails version have safe access rights 2.723
After features/support/hooks.rb:330 2.442
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:45.615
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 32.093
And no SquashFS delta is installed 0.134
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.665
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.084
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.434
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.721
When the network is plugged 0.145
And Tor is ready 22.632
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.379
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 18.025
Given I shutdown Tails and wait for the computer to power off 11.943
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:21.410
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.778
And the file system changes introduced in version 6.2~testoverlayfs are present 0.402
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# 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.300
When the network is plugged 0.081
And Tor is ready 18.993
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.455
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.910
Given I shutdown Tails and wait for the computer to power off 4.643
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.841
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.023
And the file system changes introduced in version 6.3~testoverlayfs are present 0.522
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.348
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.429
When the network is plugged 0.147
And Tor is ready 20.943
Then the Upgrader considers the system as up-to-date 0.342
# 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 16.532
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.759
After features/support/hooks.rb:330 0.829
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
42.530
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 12.491
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.476
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.134
And the signing key used by the Upgrader is outdated 0.136
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 21.102
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.112
After features/support/hooks.rb:330 0.868
After features/support/hooks.rb:100 0.000