Project Number Date
test_Tails_ISO_stable 6681 17 Sep 2026, 16:23

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.333 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:4.664
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.123
And I create a 7200 MiB disk named "old" 0.475
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 14.497
When I start Tails from USB drive "old" with network unplugged 45.127
Then the boot device has safe access rights 2.241
And Tails is running from USB drive "old" 0.415
And there is no persistence partition on USB drive "old" 0.092
And process "udev-watchdog" is running 0.109
And udev-watchdog is monitoring the correct device 0.357
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:339 3.446
After features/support/hooks.rb:108 0.006
Tags: @product
1:25.245
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login 48.888
Then Tails is running from USB drive "old" 0.257
And I create a persistent partition 24.129
And I take note of which tps features are available 7.191
Then a Tails persistence partition exists on USB drive "old" 0.550
And I shutdown Tails and wait for the computer to power off 4.140
After features/support/hooks.rb:339 0.587
After features/support/hooks.rb:108 0.005
Tags: @product
1:40.544
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.100
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.132
Then Tails is running from USB drive "old" 0.237
And all tps features are active 7.681
When I write some files expected to persist 1.401
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.179
And all persistence configuration files have safe access rights 0.303
And all persistent directories from the old Tails version have safe access rights 2.183
And I take note of which tps features are available 7.323
And I shutdown Tails and wait for the computer to power off 2.612
# 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.388
After features/support/hooks.rb:339 0.276
After features/support/hooks.rb:108 0.006
Tags: @product
2:14.801
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 without a persistent partition and stopped at Tails Greeter's login screen 8.664
And I log in to a new session 12.145
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.676
And I plug USB drive "to_upgrade" 2.302
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.127
Then the running Tails is installed on USB drive "to_upgrade" 19.614
And I unplug USB drive "to_upgrade" 0.122
And I unplug USB drive "__internal" 0.147
After features/support/hooks.rb:339 2.011
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.214
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.099
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.622
Then all tps features from the old Tails version are active 1.105
And Tails is running from USB drive "to_upgrade" 0.208
And the boot device has safe access rights 2.371
And the expected persistent files created with the old Tails version are present in the filesystem 1.038
And all persistent directories from the old Tails version have safe access rights 1.770
After features/support/hooks.rb:339 1.024
After features/support/hooks.rb:108 0.040
Tags: @product @automatic_upgrade
3:52.249
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.861
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.207
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.306
When the network is plugged 0.027
And Tor is ready 12.409
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.749
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.288
Given I shutdown Tails and wait for the computer to power off 5.427
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.589
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.647
And the file system changes introduced in version 6.2~testoverlayfs are present 0.217
And only the 6.2~testoverlayfs SquashFS delta is installed 0.053
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.105
# 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.170
When the network is plugged 0.026
And Tor is ready 9.904
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.795
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.992
Given I shutdown Tails and wait for the computer to power off 4.172
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.726
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 8.802
And the file system changes introduced in version 6.3~testoverlayfs are present 0.369
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.115
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.206
When the network is plugged 0.031
And Tor is ready 10.337
Then the Upgrader considers the system as up-to-date 10.512
# 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.446
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.321
After features/support/hooks.rb:339 0.595
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
20.613
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.160
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.228
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
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.048
And Tor is ready 9.939
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.133
After features/support/hooks.rb:339 0.534
After features/support/hooks.rb:108 0.000