Project Number Date
test_Tails_ISO_devel 4325 07 Apr 2026, 11:14

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 12:33.997 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
1:3.338
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.088
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.909
When I start Tails from USB drive "old" with network unplugged 44.948
Then the boot device has safe access rights 2.637
And Tails is running from USB drive "old" 0.268
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.210
And I unplug USB drive "old" 0.137
After features/support/hooks.rb:331 1.229
After features/support/hooks.rb:100 0.007
Tags: @product
1:31.311
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login 55.749
Then Tails is running from USB drive "old" 0.404
And I create a persistent partition 25.439
And I take note of which tps features are available 0.653
Then a Tails persistence partition exists on USB drive "old" 0.608
And I shutdown Tails and wait for the computer to power off 8.400
After features/support/hooks.rb:331 0.602
After features/support/hooks.rb:100 0.006
Tags: @product
1:31.490
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.274
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.185
Then Tails is running from USB drive "old" 0.320
And all tps features are active 1.221
When I write some files expected to persist 1.286
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.185
And all persistence configuration files have safe access rights 0.458
And all persistent directories from the old Tails version have safe access rights 2.090
And I take note of which tps features are available 0.781
And I shutdown Tails and wait for the computer to power off 8.369
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.315
After features/support/hooks.rb:331 0.373
After features/support/hooks.rb:100 0.007
Tags: @product
2:11.565
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.360
And I log in to a new session 11.650
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.933
And I plug USB drive "to_upgrade" 2.218
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.001
Then the running Tails is installed on USB drive "to_upgrade" 16.122
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.141
After features/support/hooks.rb:331 0.761
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.315
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.059
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.557
Then all tps features from the old Tails version are active 1.088
And Tails is running from USB drive "to_upgrade" 0.212
And the boot device has safe access rights 2.722
And the expected persistent files created with the old Tails version are present in the filesystem 1.088
And all persistent directories from the old Tails version have safe access rights 2.586
After features/support/hooks.rb:331 1.024
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:37.970
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 8.492
And no SquashFS delta is installed 0.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.244
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.263
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.413
When the network is plugged 0.016
And Tor is ready 20.756
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.345
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.467
Given I shutdown Tails and wait for the computer to power off 20.145
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.468
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.100
And the file system changes introduced in version 6.2~testoverlayfs are present 0.263
And only the 6.2~testoverlayfs SquashFS delta is installed 0.037
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.154
# 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.205
When the network is plugged 0.016
And Tor is ready 21.983
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.383
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.648
Given I shutdown Tails and wait for the computer to power off 17.295
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.830
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 1.125
And the file system changes introduced in version 6.3~testoverlayfs are present 0.342
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.126
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.222
When the network is plugged 0.015
And Tor is ready 21.212
Then the Upgrader considers the system as up-to-date 0.099
# 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 4.650
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.436
After features/support/hooks.rb:331 0.903
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
26.005
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.624
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.251
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.022
And Tor is ready 17.628
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.365
After features/support/hooks.rb:331 0.963
After features/support/hooks.rb:100 0.000