Project Number Date
test_Tails_ISO_devel 4603 08 Sep 2026, 13:09

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:49.485 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:12.048
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.093
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.835
When I start Tails from USB drive "old" with network unplugged 53.882
Then the boot device has safe access rights 2.493
And Tails is running from USB drive "old" 0.275
And there is no persistence partition on USB drive "old" 0.036
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.185
And I unplug USB drive "old" 0.152
After features/support/hooks.rb:339 3.499
After features/support/hooks.rb:108 0.009
Tags: @product
1:29.695
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.108
And I start Tails from USB drive "old" with network unplugged and I login 51.206
Then Tails is running from USB drive "old" 0.239
And I create a persistent partition 26.191
And I take note of which tps features are available 7.291
Then a Tails persistence partition exists on USB drive "old" 0.531
And I shutdown Tails and wait for the computer to power off 4.124
After features/support/hooks.rb:339 0.146
After features/support/hooks.rb:108 0.006
Tags: @product
1:40.612
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.093
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.666
Then Tails is running from USB drive "old" 0.759
And all tps features are active 8.676
When I write some files expected to persist 1.059
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.131
And all persistence configuration files have safe access rights 0.263
And all persistent directories from the old Tails version have safe access rights 1.611
And I take note of which tps features are available 6.539
And I shutdown Tails and wait for the computer to power off 4.051
# 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.758
After features/support/hooks.rb:339 0.259
After features/support/hooks.rb:108 0.007
Tags: @product
2:14.438
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.713
And I log in to a new session 11.188
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.812
And I plug USB drive "to_upgrade" 2.269
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.231
Then the running Tails is installed on USB drive "to_upgrade" 18.978
And I unplug USB drive "to_upgrade" 0.122
And I unplug USB drive "__internal" 0.121
After features/support/hooks.rb:339 1.724
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.736
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.095
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.957
Then all tps features from the old Tails version are active 0.990
And Tails is running from USB drive "to_upgrade" 0.201
And the boot device has safe access rights 2.510
And the expected persistent files created with the old Tails version are present in the filesystem 1.016
And all persistent directories from the old Tails version have safe access rights 1.965
After features/support/hooks.rb:339 0.920
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:39.763
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.475
And no SquashFS delta is installed 0.059
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.243
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.204
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.308
When the network is plugged 0.021
And Tor is ready 13.301
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.991
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.359
Given I shutdown Tails and wait for the computer to power off 5.465
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.133
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.368
And the file system changes introduced in version 6.2~testoverlayfs are present 0.199
And only the 6.2~testoverlayfs SquashFS delta is installed 0.036
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.119
# 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.175
When the network is plugged 0.023
And Tor is ready 10.809
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.413
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.049
Given I shutdown Tails and wait for the computer to power off 4.063
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.525
Then Tails is running version 6.3~testoverlayfs 0.031
And all tps features are active 9.212
And the file system changes introduced in version 6.3~testoverlayfs are present 0.454
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.119
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.247
When the network is plugged 0.026
And Tor is ready 10.630
Then the Upgrader considers the system as up-to-date 0.149
# 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 4.052
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.386
After features/support/hooks.rb:339 0.595
After features/support/hooks.rb:108 0.014
Tags: @product @automatic_upgrade
20.190
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.101
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.186
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.033
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.027
And Tor is ready 10.206
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.595
After features/support/hooks.rb:339 0.951
After features/support/hooks.rb:108 0.000