Project Number Date
test_Tails_ISO_stable 6642 07 Sep 2026, 11:30

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:42.605 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
52.472
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.083
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 12.994
When I start Tails from USB drive "old" with network unplugged 35.860
Then the boot device has safe access rights 1.964
And Tails is running from USB drive "old" 0.138
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.036
And udev-watchdog is monitoring the correct device 0.150
And I unplug USB drive "old" 0.142
After features/support/hooks.rb:339 1.691
After features/support/hooks.rb:108 0.011
Tags: @product
1:19.170
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.006
Given a computer 0.114
And I start Tails from USB drive "old" with network unplugged and I login 46.980
Then Tails is running from USB drive "old" 0.211
And I create a persistent partition 22.664
And I take note of which tps features are available 6.087
Then a Tails persistence partition exists on USB drive "old" 0.523
And I shutdown Tails and wait for the computer to power off 2.588
After features/support/hooks.rb:339 0.157
After features/support/hooks.rb:108 0.005
Tags: @product
1:26.858
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.566
Then Tails is running from USB drive "old" 0.158
And all tps features are active 6.866
When I write some files expected to persist 0.913
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.130
And all persistence configuration files have safe access rights 0.203
And all persistent directories from the old Tails version have safe access rights 1.415
And I take note of which tps features are available 5.991
And I shutdown Tails and wait for the computer to power off 2.592
# 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.940
After features/support/hooks.rb:339 0.414
After features/support/hooks.rb:108 0.005
Tags: @product
2:10.609
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.109
And I log in to a new session 11.417
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.559
And I plug USB drive "to_upgrade" 2.201
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.585
Then the running Tails is installed on USB drive "to_upgrade" 17.445
And I unplug USB drive "to_upgrade" 0.137
And I unplug USB drive "__internal" 0.153
After features/support/hooks.rb:339 1.668
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.858
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.932
Then all tps features from the old Tails version are active 1.004
And Tails is running from USB drive "to_upgrade" 0.160
And the boot device has safe access rights 2.113
And the expected persistent files created with the old Tails version are present in the filesystem 0.974
And all persistent directories from the old Tails version have safe access rights 1.593
After features/support/hooks.rb:339 0.780
After features/support/hooks.rb:108 0.005
3:18.054
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.943
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.259
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.033
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.242
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.325
When the network is plugged 0.034
And Tor is ready 12.944
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.899
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.482
Given I shutdown Tails and wait for the computer to power off 5.452
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.274
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.110
And the file system changes introduced in version 6.2~testoverlayfs are present 0.180
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.098
# 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.030
And Tor is ready 10.069
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.387
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.590
Given I shutdown Tails and wait for the computer to power off 3.948
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.033
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 6.970
And the file system changes introduced in version 6.3~testoverlayfs are present 0.285
And only the 6.3~testoverlayfs SquashFS delta is installed 0.034
# 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.103
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.166
When the network is plugged 0.033
And Tor is ready 10.202
Then the Upgrader considers the system as up-to-date 0.076
# 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.154
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.380
After features/support/hooks.rb:339 0.758
After features/support/hooks.rb:108 0.009
30.580
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 20.835
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.201
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.059
But a current signing key is available on our website 0.000
When the network is plugged 0.026
And Tor is ready 9.125
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.281
After features/support/hooks.rb:339 0.562
After features/support/hooks.rb:108 0.000