Project Number Date
test_Tails_ISO_stable 6563 06 Aug 2026, 11:41

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:33.128 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:0.858
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.096
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.032
And I write an old version of the Tails USB image to disk "old" 13.923
When I start Tails from USB drive "old" with network unplugged 42.897
Then the boot device has safe access rights 2.210
And Tails is running from USB drive "old" 0.246
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.188
And I unplug USB drive "old" 0.116
After features/support/hooks.rb:339 3.727
After features/support/hooks.rb:108 0.013
Tags: @product
1:25.590
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.008
Given a computer 0.110
And I start Tails from USB drive "old" with network unplugged and I login 49.492
Then Tails is running from USB drive "old" 0.187
And I create a persistent partition 24.168
And I take note of which tps features are available 6.996
Then a Tails persistence partition exists on USB drive "old" 0.574
And I shutdown Tails and wait for the computer to power off 4.061
After features/support/hooks.rb:339 0.249
After features/support/hooks.rb:108 0.005
Tags: @product
1:34.905
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.103
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.122
Then Tails is running from USB drive "old" 0.263
And all tps features are active 7.164
When I write some files expected to persist 1.172
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.172
And all persistence configuration files have safe access rights 0.246
And all persistent directories from the old Tails version have safe access rights 2.007
And I take note of which tps features are available 6.501
And I shutdown Tails and wait for the computer to power off 2.633
# 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.517
After features/support/hooks.rb:339 0.439
After features/support/hooks.rb:108 0.006
Tags: @product
2:14.733
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 without a persistent partition and stopped at Tails Greeter's login screen 8.614
And I log in to a new session 11.506
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.779
And I plug USB drive "to_upgrade" 2.209
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.193
Then the running Tails is installed on USB drive "to_upgrade" 19.042
And I unplug USB drive "to_upgrade" 0.225
And I unplug USB drive "__internal" 0.161
After features/support/hooks.rb:339 3.964
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.549
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.085
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.994
Then all tps features from the old Tails version are active 1.149
And Tails is running from USB drive "to_upgrade" 0.205
And the boot device has safe access rights 2.450
And the expected persistent files created with the old Tails version are present in the filesystem 1.007
And all persistent directories from the old Tails version have safe access rights 1.656
After features/support/hooks.rb:339 0.626
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:46.028
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.559
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.341
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.253
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.464
When the network is plugged 0.027
And Tor is ready 13.659
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.635
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.338
Given I shutdown Tails and wait for the computer to power off 7.041
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.962
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 9.479
And the file system changes introduced in version 6.2~testoverlayfs are present 0.249
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.156
# 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.219
When the network is plugged 0.044
And Tor is ready 10.979
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.069
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.882
Given I shutdown Tails and wait for the computer to power off 3.921
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.974
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 9.191
And the file system changes introduced in version 6.3~testoverlayfs are present 0.531
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.180
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.209
When the network is plugged 0.027
And Tor is ready 10.475
Then the Upgrader considers the system as up-to-date 0.119
# 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.498
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.276
After features/support/hooks.rb:339 0.949
After features/support/hooks.rb:108 0.038
Tags: @product @automatic_upgrade
19.461
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.316
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.081
And the signing key used by the Upgrader is outdated 0.038
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 9.846
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.900
After features/support/hooks.rb:339 0.825
After features/support/hooks.rb:108 0.000