Project Number Date
test_Tails_ISO_stable 5725 19 Jun 2025, 02:32

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 28:27.812 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:34.111
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.198
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 43.476
When I start Tails from USB drive "old" with network unplugged 2:36.850
Then the boot device has safe access rights 5.736
And Tails is running from USB drive "old" 4.381
And there is no persistence partition on USB drive "old" 0.665
And process "udev-watchdog" is running 0.225
And udev-watchdog is monitoring the correct device 1.099
And I unplug USB drive "old" 0.380
After features/support/hooks.rb:330 4.088
After features/support/hooks.rb:100 0.037
Tags: @product
3:7.281
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.234
And I start Tails from USB drive "old" with network unplugged and I login 2:6.326
Then Tails is running from USB drive "old" 0.437
And I create a persistent partition 46.640
And I take note of which tps features are available 3.071
Then a Tails persistence partition exists on USB drive "old" 1.608
And I shutdown Tails and wait for the computer to power off 8.962
After features/support/hooks.rb:330 1.631
After features/support/hooks.rb:100 0.066
Tags: @product
4:20.125
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.113
Given a computer 1.829
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:23.600
Then Tails is running from USB drive "old" 2.177
And all tps features are active 2.856
When I write some files expected to persist 2.075
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.260
And all persistence configuration files have safe access rights 0.520
And all persistent directories from the old Tails version have safe access rights 3.467
And I take note of which tps features are available 0.556
And I shutdown Tails and wait for the computer to power off 8.834
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 33.945
After features/support/hooks.rb:330 1.046
After features/support/hooks.rb:100 0.035
Tags: @product
3:30.539
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 15.538
And I log in to a new session 33.201
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.524
And I plug USB drive "to_upgrade" 2.541
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:58.778
Then the running Tails is installed on USB drive "to_upgrade" 38.531
And I unplug USB drive "to_upgrade" 0.187
And I unplug USB drive "__internal" 0.235
After features/support/hooks.rb:330 2.720
After features/support/hooks.rb:100 0.000
Tags: @product
3:19.331
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.314
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:1.062
Then all tps features from the old Tails version are active 3.677
And Tails is running from USB drive "to_upgrade" 2.924
And the boot device has safe access rights 6.747
And the expected persistent files created with the old Tails version are present in the filesystem 1.557
And all persistent directories from the old Tails version have safe access rights 3.048
After features/support/hooks.rb:330 1.694
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
9:39.507
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 18.350
And no SquashFS delta is installed 0.309
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.504
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.130
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.701
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.742
When the network is plugged 0.138
And Tor is ready 31.510
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.216
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 20.054
Given I shutdown Tails and wait for the computer to power off 15.320
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:56.041
Then Tails is running version 6.2~testoverlayfs 0.023
And all tps features are active 3.354
And the file system changes introduced in version 6.2~testoverlayfs are present 0.372
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.295
# 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.607
When the network is plugged 0.075
And Tor is ready 28.771
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 9.116
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 18.029
Given I shutdown Tails and wait for the computer to power off 7.036
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:0.555
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 5.970
And the file system changes introduced in version 6.3~testoverlayfs are present 2.065
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.674
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 1.075
When the network is plugged 0.302
And Tor is ready 24.141
Then the Upgrader considers the system as up-to-date 0.328
# 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.877
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.636
After features/support/hooks.rb:330 0.947
After features/support/hooks.rb:100 0.033
Tags: @product @automatic_upgrade
56.914
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 17.711
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.464
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.196
And the signing key used by the Upgrader is outdated 0.260
But a current signing key is available on our website 0.000
When the network is plugged 0.116
And Tor is ready 30.590
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.574
After features/support/hooks.rb:330 1.223
After features/support/hooks.rb:100 0.000