Project Number Date
test_Tails_ISO_devel 4600 08 Sep 2026, 00:22

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 10:44.793 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.194
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.080
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 12.932
When I start Tails from USB drive "old" with network unplugged 46.759
Then the boot device has safe access rights 1.817
And Tails is running from USB drive "old" 0.201
And there is no persistence partition on USB drive "old" 0.035
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.160
And I unplug USB drive "old" 0.116
After features/support/hooks.rb:339 1.649
After features/support/hooks.rb:108 0.005
Tags: @product
1:18.135
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login 45.239
Then Tails is running from USB drive "old" 0.194
And I create a persistent partition 22.022
And I take note of which tps features are available 6.062
Then a Tails persistence partition exists on USB drive "old" 0.558
And I shutdown Tails and wait for the computer to power off 3.983
After features/support/hooks.rb:339 0.166
After features/support/hooks.rb:108 0.006
Tags: @product
1:27.912
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.092
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.814
Then Tails is running from USB drive "old" 0.162
And all tps features are active 6.614
When I write some files expected to persist 0.928
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.158
And all persistence configuration files have safe access rights 0.269
And all persistent directories from the old Tails version have safe access rights 1.494
And I take note of which tps features are available 5.892
And I shutdown Tails and wait for the computer to power off 2.511
# 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" 10.974
After features/support/hooks.rb:339 0.358
After features/support/hooks.rb:108 0.005
Tags: @product
2:9.952
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.090
And I log in to a new session 10.785
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.576
And I plug USB drive "to_upgrade" 2.186
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.775
Then the running Tails is installed on USB drive "to_upgrade" 17.305
And I unplug USB drive "to_upgrade" 0.109
And I unplug USB drive "__internal" 0.122
After features/support/hooks.rb:339 1.675
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.526
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.076
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.240
Then all tps features from the old Tails version are active 1.013
And Tails is running from USB drive "to_upgrade" 0.155
And the boot device has safe access rights 1.893
And the expected persistent files created with the old Tails version are present in the filesystem 0.786
And all persistent directories from the old Tails version have safe access rights 1.360
After features/support/hooks.rb:339 0.611
After features/support/hooks.rb:108 0.017
3:22.039
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.105
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.206
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.178
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.345
When the network is plugged 0.044
And Tor is ready 13.190
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.863
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.872
Given I shutdown Tails and wait for the computer to power off 5.401
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.143
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.274
And the file system changes introduced in version 6.2~testoverlayfs are present 0.161
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.083
# 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.176
When the network is plugged 0.033
And Tor is ready 10.148
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.848
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.417
Given I shutdown Tails and wait for the computer to power off 2.551
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.006
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.655
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.028
# 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.111
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.191
When the network is plugged 0.033
And Tor is ready 9.982
Then the Upgrader considers the system as up-to-date 0.072
# 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.092
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.313
After features/support/hooks.rb:339 0.762
After features/support/hooks.rb:108 0.015
19.032
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 with a persistent partition enabled and logged in 7.609
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.198
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 9.134
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.976
After features/support/hooks.rb:339 0.618
After features/support/hooks.rb:108 0.000