Project Number Date
test_Tails_ISO_stable 5549 03 Apr 2025, 14: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 20:41.628 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:11.187
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given a computer 0.203
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 31.655
When I start Tails from USB drive "old" with network unplugged 1:34.034
Then the boot device has safe access rights 3.223
And Tails is running from USB drive "old" 0.314
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.309
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:330 7.144
After features/support/hooks.rb:100 0.007
Tags: @product
2:17.547
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login 1:33.692
Then Tails is running from USB drive "old" 0.353
And I create a persistent partition 32.509
And I take note of which tps features are available 1.631
Then a Tails persistence partition exists on USB drive "old" 0.901
And I shutdown Tails and wait for the computer to power off 8.272
After features/support/hooks.rb:330 0.218
After features/support/hooks.rb:100 0.008
Tags: @product
2:58.881
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.584
Then Tails is running from USB drive "old" 0.404
And all tps features are active 2.715
When I write some files expected to persist 1.973
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 1.220
And all persistence configuration files have safe access rights 0.383
And all persistent directories from the old Tails version have safe access rights 3.428
And I take note of which tps features are available 1.326
And I shutdown Tails and wait for the computer to power off 6.199
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.460
After features/support/hooks.rb:330 0.132
After features/support/hooks.rb:100 0.013
Tags: @product
2:39.962
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.087
And I log in to a new session 19.326
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.569
And I plug USB drive "to_upgrade" 2.401
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.392
Then the running Tails is installed on USB drive "to_upgrade" 27.725
And I unplug USB drive "to_upgrade" 0.248
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:330 3.863
After features/support/hooks.rb:100 0.000
Tags: @product
2:33.881
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.211
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:23.364
Then all tps features from the old Tails version are active 1.824
And Tails is running from USB drive "to_upgrade" 0.352
And the boot device has safe access rights 3.904
And the expected persistent files created with the old Tails version are present in the filesystem 1.528
And all persistent directories from the old Tails version have safe access rights 2.695
After features/support/hooks.rb:330 1.311
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
7:17.925
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 12.178
And no SquashFS delta is installed 0.473
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.407
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.317
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.442
When the network is plugged 0.088
And Tor is ready 22.234
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.506
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.503
Given I shutdown Tails and wait for the computer to power off 8.805
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:22.998
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.497
And the file system changes introduced in version 6.2~testoverlayfs are present 0.378
And only the 6.2~testoverlayfs SquashFS delta is installed 0.108
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.400
# 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.293
When the network is plugged 0.069
And Tor is ready 18.984
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.094
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.711
Given I shutdown Tails and wait for the computer to power off 7.014
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.879
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 3.025
And the file system changes introduced in version 6.3~testoverlayfs are present 0.553
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.305
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.308
When the network is plugged 0.104
And Tor is ready 19.282
Then the Upgrader considers the system as up-to-date 0.429
# 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.732
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.620
After features/support/hooks.rb:330 0.975
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
42.243
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 with a persistent partition enabled and logged in 11.966
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.578
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the signing key used by the Upgrader is outdated 0.090
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 20.687
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.764
After features/support/hooks.rb:330 0.730
After features/support/hooks.rb:100 0.000