Project Number Date
test_Tails_ISO_devel 4398 15 May 2026, 11: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 11:7.631 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:7.554
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.056
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 12.975
When I start Tails from USB drive "old" with network unplugged 50.780
Then the boot device has safe access rights 2.056
And Tails is running from USB drive "old" 0.239
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.203
And I unplug USB drive "old" 0.128
After features/support/hooks.rb:335 1.659
After features/support/hooks.rb:104 0.006
Tags: @product
1:23.205
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.046
And I start Tails from USB drive "old" with network unplugged and I login 50.939
Then Tails is running from USB drive "old" 0.208
And I create a persistent partition 23.320
And I take note of which tps features are available 0.313
Then a Tails persistence partition exists on USB drive "old" 0.498
And I shutdown Tails and wait for the computer to power off 7.877
After features/support/hooks.rb:335 0.179
After features/support/hooks.rb:104 0.006
Tags: @product
1:24.569
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.007
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.718
Then Tails is running from USB drive "old" 0.206
And all tps features are active 1.164
When I write some files expected to persist 1.433
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.138
And all persistence configuration files have safe access rights 0.302
And all persistent directories from the old Tails version have safe access rights 1.852
And I take note of which tps features are available 0.153
And I shutdown Tails and wait for the computer to power off 7.896
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 11.626
After features/support/hooks.rb:335 0.274
After features/support/hooks.rb:104 0.006
Tags: @product
2:8.701
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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 7.671
And I log in to a new session 11.988
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.650
And I plug USB drive "to_upgrade" 2.204
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.886
Then the running Tails is installed on USB drive "to_upgrade" 15.027
And I unplug USB drive "to_upgrade" 0.143
And I unplug USB drive "__internal" 0.129
After features/support/hooks.rb:335 3.427
After features/support/hooks.rb:104 0.000
Tags: @product
1:6.138
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.053
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.479
Then all tps features from the old Tails version are active 0.968
And Tails is running from USB drive "to_upgrade" 0.244
And the boot device has safe access rights 2.309
And the expected persistent files created with the old Tails version are present in the filesystem 1.143
And all persistent directories from the old Tails version have safe access rights 1.940
After features/support/hooks.rb:335 0.581
After features/support/hooks.rb:104 0.006
3:36.839
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.389
And no SquashFS delta is installed 0.056
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.223
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.200
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.352
When the network is plugged 0.012
And Tor is ready 12.520
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.076
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.130
Given I shutdown Tails and wait for the computer to power off 10.642
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.661
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.154
And the file system changes introduced in version 6.2~testoverlayfs are present 0.198
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.142
# 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.173
When the network is plugged 0.015
And Tor is ready 10.959
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.448
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.566
Given I shutdown Tails and wait for the computer to power off 7.869
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.454
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.043
And the file system changes introduced in version 6.3~testoverlayfs are present 0.406
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.187
When the network is plugged 0.012
And Tor is ready 10.016
Then the Upgrader considers the system as up-to-date 10.531
# 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 3.698
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.400
After features/support/hooks.rb:335 1.068
After features/support/hooks.rb:104 0.023
20.622
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.379
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.246
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 9.739
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.118
After features/support/hooks.rb:335 0.582
After features/support/hooks.rb:104 0.000