Project Number Date
test_Tails_ISO_stable 6132 10 Feb 2026, 02:07

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:25.571 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:50.922
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.026
And I write an old version of the Tails USB image to disk "old" 13.627
When I start Tails from USB drive "old" with network unplugged 1:33.092
Then the boot device has safe access rights 2.439
And Tails is running from USB drive "old" 0.235
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.188
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:331 3.696
After features/support/hooks.rb:100 0.034
Tags: @product
1:25.700
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login 52.619
Then Tails is running from USB drive "old" 0.316
And I create a persistent partition 23.535
And I take note of which tps features are available 0.693
Then a Tails persistence partition exists on USB drive "old" 0.493
And I shutdown Tails and wait for the computer to power off 7.968
After features/support/hooks.rb:331 0.198
After features/support/hooks.rb:100 0.019
Tags: @product
1:26.528
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.024
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.432
Then Tails is running from USB drive "old" 0.217
And all tps features are active 1.205
When I write some files expected to persist 1.284
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.174
And all persistence configuration files have safe access rights 0.322
And all persistent directories from the old Tails version have safe access rights 1.898
And I take note of which tps features are available 0.153
And I shutdown Tails and wait for the computer to power off 8.272
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.485
After features/support/hooks.rb:331 0.328
After features/support/hooks.rb:100 0.008
Tags: @product
2:21.815
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 without a persistent partition and stopped at Tails Greeter's login screen 8.163
And I log in to a new session 13.146
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.676
And I plug USB drive "to_upgrade" 2.227
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.718
Then the running Tails is installed on USB drive "to_upgrade" 16.617
And I unplug USB drive "to_upgrade" 0.132
And I unplug USB drive "__internal" 0.133
After features/support/hooks.rb:331 3.608
After features/support/hooks.rb:100 0.000
Tags: @product
1:8.815
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.061
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.823
Then all tps features from the old Tails version are active 0.951
And Tails is running from USB drive "to_upgrade" 0.209
And the boot device has safe access rights 2.716
And the expected persistent files created with the old Tails version are present in the filesystem 1.071
And all persistent directories from the old Tails version have safe access rights 1.982
After features/support/hooks.rb:331 0.974
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
3:50.563
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 with a persistent partition enabled and logged in 8.616
And no SquashFS delta is installed 0.113
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.263
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.230
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.331
When the network is plugged 0.021
And Tor is ready 13.590
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.802
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.800
Given I shutdown Tails and wait for the computer to power off 17.037
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.699
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.120
And the file system changes introduced in version 6.2~testoverlayfs are present 0.287
And only the 6.2~testoverlayfs SquashFS delta is installed 0.038
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.133
# 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.263
When the network is plugged 0.015
And Tor is ready 9.813
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.089
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.810
Given I shutdown Tails and wait for the computer to power off 7.968
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.114
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.135
And the file system changes introduced in version 6.3~testoverlayfs are present 0.394
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.176
When the network is plugged 0.020
And Tor is ready 11.251
Then the Upgrader considers the system as up-to-date 10.567
# 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.223
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.363
After features/support/hooks.rb:331 0.960
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
21.224
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.635
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.235
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.032
And the signing key used by the Upgrader is outdated 0.067
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 9.407
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.829
After features/support/hooks.rb:331 0.577
After features/support/hooks.rb:100 0.000