Project Number Date
test_Tails_ISO_devel 3876 19 Jun 2025, 11:30

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 27:46.926 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.563
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.032
Given a computer 0.426
And I create a 7200 MiB disk named "old" 0.084
And I plug USB drive "old" 1.146
And I write an old version of the Tails USB image to disk "old" 42.164
When I start Tails from USB drive "old" with network unplugged 2:1.589
Then the boot device has safe access rights 3.668
And Tails is running from USB drive "old" 0.581
And there is no persistence partition on USB drive "old" 0.161
And process "udev-watchdog" is running 0.162
And udev-watchdog is monitoring the correct device 0.362
And I unplug USB drive "old" 0.217
After features/support/hooks.rb:330 6.670
After features/support/hooks.rb:100 0.032
Tags: @product
2:49.585
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.021
Given a computer 0.366
And I start Tails from USB drive "old" with network unplugged and I login 1:51.434
Then Tails is running from USB drive "old" 0.588
And I create a persistent partition 42.281
And I take note of which tps features are available 3.663
Then a Tails persistence partition exists on USB drive "old" 1.981
And I shutdown Tails and wait for the computer to power off 9.268
After features/support/hooks.rb:330 0.263
After features/support/hooks.rb:100 0.022
Tags: @product
4:8.709
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given a computer 0.402
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:11.848
Then Tails is running from USB drive "old" 1.290
And all tps features are active 2.737
When I write some files expected to persist 1.702
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.274
And all persistence configuration files have safe access rights 0.419
And all persistent directories from the old Tails version have safe access rights 3.144
And I take note of which tps features are available 0.469
And I shutdown Tails and wait for the computer to power off 8.497
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 37.922
After features/support/hooks.rb:330 1.186
After features/support/hooks.rb:100 0.033
Tags: @product
3:8.350
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.022
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.435
And I log in to a new session 27.796
And I clone USB drive "old" to a new USB drive "to_upgrade" 4.165
And I plug USB drive "to_upgrade" 2.377
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.983
Then the running Tails is installed on USB drive "to_upgrade" 31.188
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:330 2.108
After features/support/hooks.rb:100 0.000
Tags: @product
3:13.790
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.057
Given a computer 0.248
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:56.597
Then all tps features from the old Tails version are active 1.833
And Tails is running from USB drive "to_upgrade" 0.371
And the boot device has safe access rights 4.375
And the expected persistent files created with the old Tails version are present in the filesystem 4.332
And all persistent directories from the old Tails version have safe access rights 6.030
After features/support/hooks.rb:330 1.673
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
10:40.027
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 17.016
And no SquashFS delta is installed 0.175
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.500
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.140
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.435
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.556
When the network is plugged 0.163
And Tor is ready 29.484
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 11.006
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 19.183
Given I shutdown Tails and wait for the computer to power off 9.601
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:51.765
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.246
And the file system changes introduced in version 6.2~testoverlayfs are present 0.320
And only the 6.2~testoverlayfs SquashFS delta is installed 0.096
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.312
# 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.299
When the network is plugged 0.068
And Tor is ready 50.725
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.992
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.400
Given I shutdown Tails and wait for the computer to power off 1:30.125
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:45.617
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.476
And the file system changes introduced in version 6.3~testoverlayfs are present 0.737
And only the 6.3~testoverlayfs SquashFS delta is installed 0.142
# 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.413
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.295
When the network is plugged 0.183
And Tor is ready 27.082
Then the Upgrader considers the system as up-to-date 0.458
# 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 24.020
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.949
After features/support/hooks.rb:330 0.718
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
55.899
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.771
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.672
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.248
And the signing key used by the Upgrader is outdated 0.215
But a current signing key is available on our website 0.000
When the network is plugged 0.239
And Tor is ready 26.576
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 12.174
After features/support/hooks.rb:330 2.663
After features/support/hooks.rb:100 0.000