Project Number Date
test_Tails_ISO_stable 6300 14 Apr 2026, 19:49

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:47.012 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:1.024
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.990
When I start Tails from USB drive "old" with network unplugged 41.883
Then the boot device has safe access rights 3.331
And Tails is running from USB drive "old" 0.255
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.211
And I unplug USB drive "old" 0.170
After features/support/hooks.rb:331 1.280
After features/support/hooks.rb:100 0.006
Tags: @product
1:30.465
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.085
And I start Tails from USB drive "old" with network unplugged and I login 55.147
Then Tails is running from USB drive "old" 0.227
And I create a persistent partition 25.290
And I take note of which tps features are available 0.775
Then a Tails persistence partition exists on USB drive "old" 0.701
And I shutdown Tails and wait for the computer to power off 8.236
After features/support/hooks.rb:331 0.490
After features/support/hooks.rb:100 0.007
Tags: @product
1:29.086
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.133
Then Tails is running from USB drive "old" 0.247
And all tps features are active 1.140
When I write some files expected to persist 1.227
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.281
And all persistence configuration files have safe access rights 0.684
And all persistent directories from the old Tails version have safe access rights 2.111
And I take note of which tps features are available 0.197
And I shutdown Tails and wait for the computer to power off 8.152
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.850
After features/support/hooks.rb:331 0.279
After features/support/hooks.rb:100 0.006
Tags: @product
2:17.786
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.350
And I log in to a new session 16.897
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.880
And I plug USB drive "to_upgrade" 2.221
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.365
Then the running Tails is installed on USB drive "to_upgrade" 16.702
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.227
After features/support/hooks.rb:331 2.843
After features/support/hooks.rb:100 0.000
Tags: @product
1:14.418
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.071
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.322
Then all tps features from the old Tails version are active 1.002
And Tails is running from USB drive "to_upgrade" 0.238
And the boot device has safe access rights 2.520
And the expected persistent files created with the old Tails version are present in the filesystem 1.235
And all persistent directories from the old Tails version have safe access rights 2.028
After features/support/hooks.rb:331 0.993
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:46.928
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.950
And no SquashFS delta is installed 0.121
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.269
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.275
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.395
When the network is plugged 0.020
And Tor is ready 25.099
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.429
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.088
Given I shutdown Tails and wait for the computer to power off 20.844
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.684
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.253
And the file system changes introduced in version 6.2~testoverlayfs are present 0.214
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.156
# 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.222
When the network is plugged 0.015
And Tor is ready 22.502
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.619
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.652
Given I shutdown Tails and wait for the computer to power off 18.097
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.894
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 1.460
And the file system changes introduced in version 6.3~testoverlayfs are present 0.344
And only the 6.3~testoverlayfs SquashFS delta is installed 0.039
# 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.139
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.233
When the network is plugged 0.017
And Tor is ready 20.553
Then the Upgrader considers the system as up-to-date 0.113
# 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.732
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.374
After features/support/hooks.rb:331 0.792
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
27.304
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.601
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.300
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.050
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 18.873
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.405
After features/support/hooks.rb:331 0.993
After features/support/hooks.rb:100 0.000