Project Number Date
test_Tails_ISO_devel 3883 24 Jun 2025, 13:33

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 21:1.037 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:19.993
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.323
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.063
And I write an old version of the Tails USB image to disk "old" 32.210
When I start Tails from USB drive "old" with network unplugged 1:41.220
Then the boot device has safe access rights 3.892
And Tails is running from USB drive "old" 0.373
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.161
And udev-watchdog is monitoring the correct device 0.379
And I unplug USB drive "old" 0.255
After features/support/hooks.rb:330 3.669
After features/support/hooks.rb:100 0.023
Tags: @product
2:19.236
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 1:32.570
Then Tails is running from USB drive "old" 0.537
And I create a persistent partition 33.616
And I take note of which tps features are available 2.199
Then a Tails persistence partition exists on USB drive "old" 0.898
And I shutdown Tails and wait for the computer to power off 9.222
After features/support/hooks.rb:330 0.246
After features/support/hooks.rb:100 0.011
Tags: @product
3:18.433
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.228
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:37.551
Then Tails is running from USB drive "old" 0.348
And all tps features are active 2.245
When I write some files expected to persist 2.313
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.239
And all persistence configuration files have safe access rights 0.418
And all persistent directories from the old Tails version have safe access rights 2.608
And I take note of which tps features are available 0.469
And I shutdown Tails and wait for the computer to power off 4.241
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 27.767
After features/support/hooks.rb:330 0.102
After features/support/hooks.rb:100 0.010
Tags: @product
2:43.490
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.271
And I log in to a new session 19.897
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.489
And I plug USB drive "to_upgrade" 2.877
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.123
Then the running Tails is installed on USB drive "to_upgrade" 28.225
And I unplug USB drive "to_upgrade" 0.275
And I unplug USB drive "__internal" 0.329
After features/support/hooks.rb:330 1.967
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.003
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.187
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.720
Then all tps features from the old Tails version are active 1.771
And Tails is running from USB drive "to_upgrade" 0.371
And the boot device has safe access rights 3.746
And the expected persistent files created with the old Tails version are present in the filesystem 1.563
And all persistent directories from the old Tails version have safe access rights 2.644
After features/support/hooks.rb:330 1.654
After features/support/hooks.rb:100 0.040
Tags: @product @automatic_upgrade
7:13.158
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 15.085
And no SquashFS delta is installed 0.147
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.449
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.124
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.517
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.564
When the network is plugged 0.095
And Tor is ready 20.980
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.314
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.985
Given I shutdown Tails and wait for the computer to power off 10.674
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.394
Then Tails is running version 6.2~testoverlayfs 0.159
And all tps features are active 2.560
And the file system changes introduced in version 6.2~testoverlayfs are present 0.489
And only the 6.2~testoverlayfs SquashFS delta is installed 0.131
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.355
# 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.450
When the network is plugged 0.096
And Tor is ready 20.646
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.768
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.456
Given I shutdown Tails and wait for the computer to power off 6.138
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.692
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.671
And the file system changes introduced in version 6.3~testoverlayfs are present 0.632
And only the 6.3~testoverlayfs SquashFS delta is installed 0.099
# 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.662
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.456
When the network is plugged 0.074
And Tor is ready 23.631
Then the Upgrader considers the system as up-to-date 0.309
# 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 18.304
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.022
After features/support/hooks.rb:330 0.770
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
42.721
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.892
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.484
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.182
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 21.157
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.877
After features/support/hooks.rb:330 1.462
After features/support/hooks.rb:100 0.000