Project Number Date
test_Tails_ISO_stable 6569 10 Aug 2026, 12:48

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:52.840 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.039
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.109
And I create a 7200 MiB disk named "old" 0.031
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 13.701
When I start Tails from USB drive "old" with network unplugged 44.823
Then the boot device has safe access rights 2.693
And Tails is running from USB drive "old" 0.242
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.063
And udev-watchdog is monitoring the correct device 0.195
And I unplug USB drive "old" 0.114
After features/support/hooks.rb:339 3.531
After features/support/hooks.rb:108 0.007
Tags: @product
1:27.562
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.104
And I start Tails from USB drive "old" with network unplugged and I login 51.317
Then Tails is running from USB drive "old" 0.207
And I create a persistent partition 24.306
And I take note of which tps features are available 7.125
Then a Tails persistence partition exists on USB drive "old" 0.549
And I shutdown Tails and wait for the computer to power off 3.950
After features/support/hooks.rb:339 0.298
After features/support/hooks.rb:108 0.005
Tags: @product
1:37.902
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.094
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.267
Then Tails is running from USB drive "old" 0.284
And all tps features are active 8.519
When I write some files expected to persist 1.157
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.139
And all persistence configuration files have safe access rights 0.316
And all persistent directories from the old Tails version have safe access rights 1.502
And I take note of which tps features are available 6.118
And I shutdown Tails and wait for the computer to power off 3.859
# 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.642
After features/support/hooks.rb:339 0.383
After features/support/hooks.rb:108 0.007
Tags: @product
2:13.252
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.693
And I log in to a new session 11.627
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.676
And I plug USB drive "to_upgrade" 2.208
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.489
Then the running Tails is installed on USB drive "to_upgrade" 18.323
And I unplug USB drive "to_upgrade" 0.111
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:339 1.715
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.973
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.115
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.227
Then all tps features from the old Tails version are active 1.142
And Tails is running from USB drive "to_upgrade" 0.261
And the boot device has safe access rights 2.386
And the expected persistent files created with the old Tails version are present in the filesystem 1.153
And all persistent directories from the old Tails version have safe access rights 1.686
After features/support/hooks.rb:339 0.958
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:47.490
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.815
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.265
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.270
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.370
When the network is plugged 0.025
And Tor is ready 12.671
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.252
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.810
Given I shutdown Tails and wait for the computer to power off 5.423
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.401
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 8.144
And the file system changes introduced in version 6.2~testoverlayfs are present 0.205
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.099
# 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.196
When the network is plugged 0.039
And Tor is ready 15.042
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.175
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.607
Given I shutdown Tails and wait for the computer to power off 4.112
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.180
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.917
And the file system changes introduced in version 6.3~testoverlayfs are present 0.338
And only the 6.3~testoverlayfs SquashFS delta is installed 0.053
# 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.179
When the network is plugged 0.038
And Tor is ready 11.446
Then the Upgrader considers the system as up-to-date 0.085
# 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.572
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.431
After features/support/hooks.rb:339 0.770
After features/support/hooks.rb:108 0.051
Tags: @product @automatic_upgrade
32.619
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 21.402
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.223
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 9.774
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.094
After features/support/hooks.rb:339 0.542
After features/support/hooks.rb:108 0.000