Project Number Date
test_Tails_ISO_devel 4591 03 Sep 2026, 15:24

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:46.120 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.599
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.107
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.603
When I start Tails from USB drive "old" with network unplugged 50.016
Then the boot device has safe access rights 2.178
And Tails is running from USB drive "old" 0.239
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.035
And udev-watchdog is monitoring the correct device 0.208
And I unplug USB drive "old" 0.126
After features/support/hooks.rb:339 1.739
After features/support/hooks.rb:108 0.006
Tags: @product
1:25.942
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.112
And I start Tails from USB drive "old" with network unplugged and I login 50.090
Then Tails is running from USB drive "old" 0.231
And I create a persistent partition 23.929
And I take note of which tps features are available 6.621
Then a Tails persistence partition exists on USB drive "old" 0.713
And I shutdown Tails and wait for the computer to power off 4.242
After features/support/hooks.rb:339 0.381
After features/support/hooks.rb:108 0.006
Tags: @product
1:36.308
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.939
Then Tails is running from USB drive "old" 0.202
And all tps features are active 7.143
When I write some files expected to persist 1.111
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.183
And all persistence configuration files have safe access rights 0.250
And all persistent directories from the old Tails version have safe access rights 1.640
And I take note of which tps features are available 6.388
And I shutdown Tails and wait for the computer to power off 4.083
# 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" 12.281
After features/support/hooks.rb:339 0.504
After features/support/hooks.rb:108 0.006
Tags: @product
2:16.048
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 without a persistent partition and stopped at Tails Greeter's login screen 8.903
And I log in to a new session 12.352
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.799
And I plug USB drive "to_upgrade" 2.209
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.912
Then the running Tails is installed on USB drive "to_upgrade" 19.612
And I unplug USB drive "to_upgrade" 0.129
And I unplug USB drive "__internal" 0.129
After features/support/hooks.rb:339 1.996
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.630
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.081
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.687
Then all tps features from the old Tails version are active 1.237
And Tails is running from USB drive "to_upgrade" 0.192
And the boot device has safe access rights 2.574
And the expected persistent files created with the old Tails version are present in the filesystem 1.135
And all persistent directories from the old Tails version have safe access rights 1.721
After features/support/hooks.rb:339 0.572
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:47.688
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 8.931
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.232
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.308
When the network is plugged 0.037
And Tor is ready 12.071
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.170
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.037
Given I shutdown Tails and wait for the computer to power off 7.174
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.322
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 10.143
And the file system changes introduced in version 6.2~testoverlayfs are present 0.241
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.151
# 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.243
When the network is plugged 0.030
And Tor is ready 10.681
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.018
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.954
Given I shutdown Tails and wait for the computer to power off 4.092
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.012
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.967
And the file system changes introduced in version 6.3~testoverlayfs are present 0.363
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.137
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.228
When the network is plugged 0.024
And Tor is ready 10.415
Then the Upgrader considers the system as up-to-date 0.079
# 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.759
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.332
After features/support/hooks.rb:339 0.722
After features/support/hooks.rb:108 0.033
Tags: @product @automatic_upgrade
18.902
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 7.970
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.205
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.041
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 9.655
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.959
After features/support/hooks.rb:339 0.801
After features/support/hooks.rb:108 0.000