Project Number Date
test_Tails_ISO_devel 4624 17 Sep 2026, 14:17

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:34.007 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
58.682
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.111
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 14.410
When I start Tails from USB drive "old" with network unplugged 40.098
Then the boot device has safe access rights 2.377
And Tails is running from USB drive "old" 0.241
And there is no persistence partition on USB drive "old" 0.036
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.178
And I unplug USB drive "old" 0.122
After features/support/hooks.rb:339 3.401
After features/support/hooks.rb:108 0.007
Tags: @product
1:23.798
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.102
And I start Tails from USB drive "old" with network unplugged and I login 49.557
Then Tails is running from USB drive "old" 0.247
And I create a persistent partition 23.387
And I take note of which tps features are available 6.053
Then a Tails persistence partition exists on USB drive "old" 0.520
And I shutdown Tails and wait for the computer to power off 3.928
After features/support/hooks.rb:339 0.594
After features/support/hooks.rb:108 0.008
Tags: @product
1:37.016
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given a computer 0.171
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.636
Then Tails is running from USB drive "old" 0.277
And all tps features are active 8.094
When I write some files expected to persist 1.112
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.170
And all persistence configuration files have safe access rights 0.283
And all persistent directories from the old Tails version have safe access rights 1.723
And I take note of which tps features are available 6.677
And I shutdown Tails and wait for the computer to power off 4.106
# 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.764
After features/support/hooks.rb:339 0.338
After features/support/hooks.rb:108 0.006
Tags: @product
2:15.660
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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.883
And I log in to a new session 12.271
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.726
And I plug USB drive "to_upgrade" 2.316
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.656
Then the running Tails is installed on USB drive "to_upgrade" 19.559
And I unplug USB drive "to_upgrade" 0.125
And I unplug USB drive "__internal" 0.120
After features/support/hooks.rb:339 0.605
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.586
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.082
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.654
Then all tps features from the old Tails version are active 1.149
And Tails is running from USB drive "to_upgrade" 0.204
And the boot device has safe access rights 2.442
And the expected persistent files created with the old Tails version are present in the filesystem 1.139
And all persistent directories from the old Tails version have safe access rights 1.913
After features/support/hooks.rb:339 0.666
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:48.972
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.530
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.320
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.085
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.215
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.331
When the network is plugged 0.030
And Tor is ready 13.386
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.717
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.075
Given I shutdown Tails and wait for the computer to power off 5.364
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.518
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 8.104
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.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.131
# 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.181
When the network is plugged 0.029
And Tor is ready 10.956
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.911
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.783
Given I shutdown Tails and wait for the computer to power off 2.563
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.819
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 8.128
And the file system changes introduced in version 6.3~testoverlayfs are present 0.318
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.114
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.189
When the network is plugged 0.023
And Tor is ready 10.207
Then the Upgrader considers the system as up-to-date 10.596
# 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.572
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.354
After features/support/hooks.rb:339 0.830
After features/support/hooks.rb:108 0.042
Tags: @product @automatic_upgrade
19.291
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.134
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.221
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.133
And the signing key used by the Upgrader is outdated 0.119
But a current signing key is available on our website 0.000
When the network is plugged 0.057
And Tor is ready 8.577
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.047
After features/support/hooks.rb:339 0.918
After features/support/hooks.rb:108 0.000