Project Number Date
test_Tails_ISO_stable 5724 18 Jun 2025, 21:01

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 21:0.053 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:6.547
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.182
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 33.964
When I start Tails from USB drive "old" with network unplugged 1:26.688
Then the boot device has safe access rights 3.368
And Tails is running from USB drive "old" 0.322
And there is no persistence partition on USB drive "old" 0.117
And process "udev-watchdog" is running 0.202
And udev-watchdog is monitoring the correct device 0.375
And I unplug USB drive "old" 0.220
After features/support/hooks.rb:330 3.724
After features/support/hooks.rb:100 0.009
Tags: @product
2:18.878
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:33.217
Then Tails is running from USB drive "old" 0.355
And I create a persistent partition 32.548
And I take note of which tps features are available 2.763
Then a Tails persistence partition exists on USB drive "old" 0.830
And I shutdown Tails and wait for the computer to power off 8.970
After features/support/hooks.rb:330 0.311
After features/support/hooks.rb:100 0.008
Tags: @product
3:18.877
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.330
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:33.879
Then Tails is running from USB drive "old" 0.460
And all tps features are active 2.232
When I write some files expected to persist 2.043
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.239
And all persistence configuration files have safe access rights 0.522
And all persistent directories from the old Tails version have safe access rights 3.749
And I take note of which tps features are available 0.588
And I shutdown Tails and wait for the computer to power off 7.084
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 27.745
After features/support/hooks.rb:330 0.112
After features/support/hooks.rb:100 0.011
Tags: @product
2:50.225
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.877
And I log in to a new session 21.254
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.873
And I plug USB drive "to_upgrade" 2.559
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.084
Then the running Tails is installed on USB drive "to_upgrade" 32.014
And I unplug USB drive "to_upgrade" 0.250
And I unplug USB drive "__internal" 0.308
After features/support/hooks.rb:330 2.416
After features/support/hooks.rb:100 0.000
Tags: @product
2:28.920
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.221
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:18.744
Then all tps features from the old Tails version are active 1.924
And Tails is running from USB drive "to_upgrade" 0.396
And the boot device has safe access rights 3.238
And the expected persistent files created with the old Tails version are present in the filesystem 1.781
And all persistent directories from the old Tails version have safe access rights 2.613
After features/support/hooks.rb:330 2.162
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:15.164
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.448
And no SquashFS delta is installed 0.269
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.497
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.115
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.337
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.535
When the network is plugged 0.123
And Tor is ready 23.070
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.969
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.465
Given I shutdown Tails and wait for the computer to power off 11.539
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.949
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.383
And the file system changes introduced in version 6.2~testoverlayfs are present 0.443
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.453
# 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.421
When the network is plugged 0.061
And Tor is ready 20.011
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.188
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.496
Given I shutdown Tails and wait for the computer to power off 4.340
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:20.347
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.237
And the file system changes introduced in version 6.3~testoverlayfs are present 0.624
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.278
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.313
When the network is plugged 0.093
And Tor is ready 17.335
Then the Upgrader considers the system as up-to-date 0.376
# 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.471
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.791
After features/support/hooks.rb:330 0.838
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
41.439
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.345
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.430
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.070
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 17.606
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.850
After features/support/hooks.rb:330 1.012
After features/support/hooks.rb:100 0.000