Project Number Date
test_Tails_ISO_stable 5764 09 Jul 2025, 14:22

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 23:36.603 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
2:46.414
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.209
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 40.255
When I start Tails from USB drive "old" with network unplugged 1:59.715
Then the boot device has safe access rights 3.970
And Tails is running from USB drive "old" 0.393
And there is no persistence partition on USB drive "old" 0.088
And process "udev-watchdog" is running 0.114
And udev-watchdog is monitoring the correct device 0.387
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:330 5.511
After features/support/hooks.rb:100 0.036
Tags: @product
2:50.175
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Given a computer 0.607
And I start Tails from USB drive "old" with network unplugged and I login 1:51.948
Then Tails is running from USB drive "old" 0.544
And I create a persistent partition 39.929
And I take note of which tps features are available 4.084
Then a Tails persistence partition exists on USB drive "old" 3.639
And I shutdown Tails and wait for the computer to power off 9.420
After features/support/hooks.rb:330 0.255
After features/support/hooks.rb:100 0.007
Tags: @product
4:1.996
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:9.611
Then Tails is running from USB drive "old" 0.921
And all tps features are active 3.413
When I write some files expected to persist 2.271
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.270
And all persistence configuration files have safe access rights 0.405
And all persistent directories from the old Tails version have safe access rights 2.524
And I take note of which tps features are available 0.618
And I shutdown Tails and wait for the computer to power off 9.940
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 31.824
After features/support/hooks.rb:330 0.279
After features/support/hooks.rb:100 0.010
Tags: @product
3:17.285
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 16.339
And I log in to a new session 26.081
And I clone USB drive "old" to a new USB drive "to_upgrade" 8.336
And I plug USB drive "to_upgrade" 2.434
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:54.999
Then the running Tails is installed on USB drive "to_upgrade" 28.641
And I unplug USB drive "to_upgrade" 0.222
And I unplug USB drive "__internal" 0.230
After features/support/hooks.rb:330 1.304
After features/support/hooks.rb:100 0.000
Tags: @product
2:37.234
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.204
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:25.994
Then all tps features from the old Tails version are active 2.094
And Tails is running from USB drive "to_upgrade" 0.529
And the boot device has safe access rights 4.412
And the expected persistent files created with the old Tails version are present in the filesystem 1.632
And all persistent directories from the old Tails version have safe access rights 2.368
After features/support/hooks.rb:330 1.152
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
7:21.579
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.022
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.469
And no SquashFS delta is installed 0.213
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.400
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.532
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.516
When the network is plugged 0.078
And Tor is ready 33.075
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.244
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.272
Given I shutdown Tails and wait for the computer to power off 10.074
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.114
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.234
And the file system changes introduced in version 6.2~testoverlayfs are present 0.312
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.402
# 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.455
When the network is plugged 0.096
And Tor is ready 21.749
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.698
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.631
Given I shutdown Tails and wait for the computer to power off 8.920
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.182
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.151
And the file system changes introduced in version 6.3~testoverlayfs are present 0.644
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.575
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.549
When the network is plugged 0.075
And Tor is ready 19.239
Then the Upgrader considers the system as up-to-date 0.300
# 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 17.336
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.781
After features/support/hooks.rb:330 0.673
After features/support/hooks.rb:100 0.060
Tags: @product @automatic_upgrade
41.917
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.154
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.411
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.110
But a current signing key is available on our website 0.000
When the network is plugged 0.085
And Tor is ready 21.765
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.327
After features/support/hooks.rb:330 1.085
After features/support/hooks.rb:100 0.000