Project Number Date
test_Tails_ISO_devel 4577 30 Aug 2026, 11:13

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:28.087 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.002
Given a computer 0.074
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.302
When I start Tails from USB drive "old" with network unplugged 50.562
Then the boot device has safe access rights 2.032
And Tails is running from USB drive "old" 0.206
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.161
And I unplug USB drive "old" 0.111
After features/support/hooks.rb:339 1.626
After features/support/hooks.rb:108 0.006
Tags: @product
1:22.180
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.098
And I start Tails from USB drive "old" with network unplugged and I login 46.886
Then Tails is running from USB drive "old" 0.235
And I create a persistent partition 23.909
And I take note of which tps features are available 6.539
Then a Tails persistence partition exists on USB drive "old" 0.504
And I shutdown Tails and wait for the computer to power off 4.006
After features/support/hooks.rb:339 0.202
After features/support/hooks.rb:108 0.005
Tags: @product
1:32.327
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.330
Then Tails is running from USB drive "old" 0.174
And all tps features are active 6.833
When I write some files expected to persist 1.221
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.122
And all persistence configuration files have safe access rights 0.329
And all persistent directories from the old Tails version have safe access rights 1.764
And I take note of which tps features are available 6.091
And I shutdown Tails and wait for the computer to power off 3.920
# 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.457
After features/support/hooks.rb:339 0.542
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.964
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.904
And I log in to a new session 12.366
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.703
And I plug USB drive "to_upgrade" 2.225
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.952
Then the running Tails is installed on USB drive "to_upgrade" 18.531
And I unplug USB drive "to_upgrade" 0.123
And I unplug USB drive "__internal" 0.154
After features/support/hooks.rb:339 1.598
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.472
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.122
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.937
Then all tps features from the old Tails version are active 1.139
And Tails is running from USB drive "to_upgrade" 0.181
And the boot device has safe access rights 2.334
And the expected persistent files created with the old Tails version are present in the filesystem 1.052
And all persistent directories from the old Tails version have safe access rights 1.705
After features/support/hooks.rb:339 0.687
After features/support/hooks.rb:108 0.022
Tags: @product @automatic_upgrade
3:44.201
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.149
And no SquashFS delta is installed 0.060
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.284
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.229
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.325
When the network is plugged 0.027
And Tor is ready 13.111
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.889
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.711
Given I shutdown Tails and wait for the computer to power off 5.536
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.045
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 7.423
And the file system changes introduced in version 6.2~testoverlayfs are present 0.223
And only the 6.2~testoverlayfs SquashFS delta is installed 0.040
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.102
# 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.165
When the network is plugged 0.033
And Tor is ready 10.692
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.926
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.034
Given I shutdown Tails and wait for the computer to power off 5.136
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.310
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.637
And the file system changes introduced in version 6.3~testoverlayfs are present 0.339
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.087
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.188
When the network is plugged 0.035
And Tor is ready 10.136
Then the Upgrader considers the system as up-to-date 10.428
# 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.449
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.328
After features/support/hooks.rb:339 0.620
After features/support/hooks.rb:108 0.021
Tags: @product @automatic_upgrade
19.341
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.834
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.227
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.027
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 9.774
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.397
After features/support/hooks.rb:339 0.810
After features/support/hooks.rb:108 0.000