Project Number Date
test_Tails_ISO_devel 4594 03 Sep 2026, 20:20

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:26.490 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:5.777
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given a computer 0.107
And I create a 7200 MiB disk named "old" 0.029
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.612
When I start Tails from USB drive "old" with network unplugged 47.715
Then the boot device has safe access rights 2.647
And Tails is running from USB drive "old" 0.230
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.064
And udev-watchdog is monitoring the correct device 0.178
And I unplug USB drive "old" 0.129
After features/support/hooks.rb:339 3.760
After features/support/hooks.rb:108 0.066
Tags: @product
1:25.372
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login 49.058
Then Tails is running from USB drive "old" 0.299
And I create a persistent partition 24.333
And I take note of which tps features are available 7.091
Then a Tails persistence partition exists on USB drive "old" 0.449
And I shutdown Tails and wait for the computer to power off 4.058
After features/support/hooks.rb:339 0.485
After features/support/hooks.rb:108 0.006
Tags: @product
1:37.181
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.096
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.590
Then Tails is running from USB drive "old" 0.268
And all tps features are active 9.362
When I write some files expected to persist 1.223
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.146
And all persistence configuration files have safe access rights 0.280
And all persistent directories from the old Tails version have safe access rights 1.661
And I take note of which tps features are available 5.642
And I shutdown Tails and wait for the computer to power off 2.733
# 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" 12.174
After features/support/hooks.rb:339 0.156
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.921
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.214
And I log in to a new session 12.466
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.603
And I plug USB drive "to_upgrade" 2.194
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.199
Then the running Tails is installed on USB drive "to_upgrade" 18.980
And I unplug USB drive "to_upgrade" 0.116
And I unplug USB drive "__internal" 0.144
After features/support/hooks.rb:339 1.616
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.642
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.080
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.959
Then all tps features from the old Tails version are active 1.224
And Tails is running from USB drive "to_upgrade" 0.272
And the boot device has safe access rights 2.382
And the expected persistent files created with the old Tails version are present in the filesystem 0.984
And all persistent directories from the old Tails version have safe access rights 1.739
After features/support/hooks.rb:339 0.544
After features/support/hooks.rb:108 0.007
3:35.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 8.222
And no SquashFS delta is installed 0.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.242
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.226
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.415
When the network is plugged 0.029
And Tor is ready 14.124
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.237
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.702
Given I shutdown Tails and wait for the computer to power off 5.456
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.589
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.448
And the file system changes introduced in version 6.2~testoverlayfs are present 0.239
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.143
# 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.247
When the network is plugged 0.026
And Tor is ready 10.762
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.989
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.111
Given I shutdown Tails and wait for the computer to power off 3.982
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.278
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.692
And the file system changes introduced in version 6.3~testoverlayfs are present 0.331
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.140
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.185
When the network is plugged 0.034
And Tor is ready 10.828
Then the Upgrader considers the system as up-to-date 0.095
# 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.236
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.334
After features/support/hooks.rb:339 0.830
After features/support/hooks.rb:108 0.012
19.014
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 7.897
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.297
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the signing key used by the Upgrader is outdated 0.055
But a current signing key is available on our website 0.000
When the network is plugged 0.043
And Tor is ready 9.818
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.865
After features/support/hooks.rb:339 0.689
After features/support/hooks.rb:108 0.000