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

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 20:17.952 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:8.166
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.454
And I create a 7200 MiB disk named "old" 0.074
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 32.634
When I start Tails from USB drive "old" with network unplugged 1:29.707
Then the boot device has safe access rights 3.152
And Tails is running from USB drive "old" 0.354
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.370
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:330 3.945
After features/support/hooks.rb:100 0.009
Tags: @product
2:13.869
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.297
And I start Tails from USB drive "old" with network unplugged and I login 1:28.886
Then Tails is running from USB drive "old" 0.339
And I create a persistent partition 32.649
And I take note of which tps features are available 2.291
Then a Tails persistence partition exists on USB drive "old" 0.775
And I shutdown Tails and wait for the computer to power off 8.628
After features/support/hooks.rb:330 0.203
After features/support/hooks.rb:100 0.009
Tags: @product
3:2.123
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.899
Then Tails is running from USB drive "old" 1.202
And all tps features are active 2.400
When I write some files expected to persist 2.630
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.339
And all persistence configuration files have safe access rights 0.447
And all persistent directories from the old Tails version have safe access rights 2.829
And I take note of which tps features are available 0.510
And I shutdown Tails and wait for the computer to power off 4.563
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.121
After features/support/hooks.rb:330 0.145
After features/support/hooks.rb:100 0.010
Tags: @product
2:43.797
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 11.979
And I log in to a new session 20.210
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.917
And I plug USB drive "to_upgrade" 2.520
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.829
Then the running Tails is installed on USB drive "to_upgrade" 29.871
And I unplug USB drive "to_upgrade" 0.261
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:330 1.622
After features/support/hooks.rb:100 0.000
Tags: @product
2:28.931
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.310
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.938
Then all tps features from the old Tails version are active 1.799
And Tails is running from USB drive "to_upgrade" 0.499
And the boot device has safe access rights 3.706
And the expected persistent files created with the old Tails version are present in the filesystem 2.053
And all persistent directories from the old Tails version have safe access rights 2.624
After features/support/hooks.rb:330 1.104
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:3.933
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 13.155
And no SquashFS delta is installed 0.250
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.423
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.361
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.560
When the network is plugged 0.075
And Tor is ready 19.459
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.345
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.351
Given I shutdown Tails and wait for the computer to power off 11.047
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:25.064
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.260
And the file system changes introduced in version 6.2~testoverlayfs are present 0.304
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.369
# 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.293
When the network is plugged 0.137
And Tor is ready 15.917
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.469
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.240
Given I shutdown Tails and wait for the computer to power off 5.017
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.949
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.141
And the file system changes introduced in version 6.3~testoverlayfs are present 0.503
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.314
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.252
When the network is plugged 0.092
And Tor is ready 20.060
Then the Upgrader considers the system as up-to-date 0.493
# 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.312
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.445
After features/support/hooks.rb:330 0.764
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
37.131
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 12.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.308
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.092
And the signing key used by the Upgrader is outdated 0.177
But a current signing key is available on our website 0.000
When the network is plugged 0.117
And Tor is ready 17.372
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.996
After features/support/hooks.rb:330 1.312
After features/support/hooks.rb:100 0.000