Project Number Date
test_Tails_ISO_stable 5645 13 May 2025, 19:27

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 22:38.171 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:50.604
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.243
And I create a 7200 MiB disk named "old" 0.073
And I plug USB drive "old" 1.078
And I write an old version of the Tails USB image to disk "old" 52.911
When I start Tails from USB drive "old" with network unplugged 1:51.146
Then the boot device has safe access rights 3.824
And Tails is running from USB drive "old" 0.439
And there is no persistence partition on USB drive "old" 0.088
And process "udev-watchdog" is running 0.109
And udev-watchdog is monitoring the correct device 0.384
And I unplug USB drive "old" 0.305
After features/support/hooks.rb:330 4.133
After features/support/hooks.rb:100 0.011
Tags: @product
2:33.028
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.852
And I start Tails from USB drive "old" with network unplugged and I login 1:36.827
Then Tails is running from USB drive "old" 0.380
And I create a persistent partition 40.289
And I take note of which tps features are available 5.000
Then a Tails persistence partition exists on USB drive "old" 0.867
And I shutdown Tails and wait for the computer to power off 8.810
After features/support/hooks.rb:330 0.215
After features/support/hooks.rb:100 0.008
Tags: @product
3:27.137
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 1.246
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:43.872
Then Tails is running from USB drive "old" 0.891
And all tps features are active 2.405
When I write some files expected to persist 1.758
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.298
And all persistence configuration files have safe access rights 1.144
And all persistent directories from the old Tails version have safe access rights 2.669
And I take note of which tps features are available 0.632
And I shutdown Tails and wait for the computer to power off 6.876
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.341
After features/support/hooks.rb:330 0.137
After features/support/hooks.rb:100 0.010
Tags: @product
3:16.283
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 without a persistent partition and stopped at Tails Greeter's login screen 34.533
And I log in to a new session 21.014
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.078
And I plug USB drive "to_upgrade" 2.517
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.647
Then the running Tails is installed on USB drive "to_upgrade" 36.808
And I unplug USB drive "to_upgrade" 0.222
And I unplug USB drive "__internal" 0.460
After features/support/hooks.rb:330 2.397
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.166
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.260
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.849
Then all tps features from the old Tails version are active 1.819
And Tails is running from USB drive "to_upgrade" 0.403
And the boot device has safe access rights 3.603
And the expected persistent files created with the old Tails version are present in the filesystem 1.590
And all persistent directories from the old Tails version have safe access rights 2.639
After features/support/hooks.rb:330 1.421
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:19.834
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 14.926
And no SquashFS delta is installed 0.175
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.462
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.099
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.430
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.557
When the network is plugged 0.073
And Tor is ready 23.865
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 10.842
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.958
Given I shutdown Tails and wait for the computer to power off 11.177
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.462
Then Tails is running version 6.2~testoverlayfs 0.224
And all tps features are active 8.595
And the file system changes introduced in version 6.2~testoverlayfs are present 0.346
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.353
# 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.275
When the network is plugged 0.376
And Tor is ready 19.685
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.967
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.414
Given I shutdown Tails and wait for the computer to power off 7.293
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.774
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.695
And the file system changes introduced in version 6.3~testoverlayfs are present 0.552
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.341
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.355
When the network is plugged 0.086
And Tor is ready 20.950
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 17.263
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.705
After features/support/hooks.rb:330 1.106
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
44.117
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 14.341
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.375
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.074
But a current signing key is available on our website 0.000
When the network is plugged 0.086
And Tor is ready 20.499
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.675
After features/support/hooks.rb:330 0.946
After features/support/hooks.rb:100 0.000