Project Number Date
test_Tails_ISO_stable 5593 24 Apr 2025, 09:19

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 19:42.465 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:7.402
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.199
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.102
And I write an old version of the Tails USB image to disk "old" 33.152
When I start Tails from USB drive "old" with network unplugged 1:28.514
Then the boot device has safe access rights 3.350
And Tails is running from USB drive "old" 0.307
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.111
And udev-watchdog is monitoring the correct device 0.342
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:330 6.802
After features/support/hooks.rb:100 0.013
Tags: @product
2:10.755
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login 1:27.270
Then Tails is running from USB drive "old" 0.369
And I create a persistent partition 31.429
And I take note of which tps features are available 2.284
Then a Tails persistence partition exists on USB drive "old" 0.833
And I shutdown Tails and wait for the computer to power off 8.342
After features/support/hooks.rb:330 0.168
After features/support/hooks.rb:100 0.010
Tags: @product
2:58.421
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.839
Then Tails is running from USB drive "old" 0.541
And all tps features are active 2.104
When I write some files expected to persist 2.341
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.216
And all persistence configuration files have safe access rights 0.371
And all persistent directories from the old Tails version have safe access rights 2.681
And I take note of which tps features are available 0.499
And I shutdown Tails and wait for the computer to power off 6.419
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.215
After features/support/hooks.rb:330 0.127
After features/support/hooks.rb:100 0.012
Tags: @product
2:35.750
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 10.727
And I log in to a new session 19.901
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.984
And I plug USB drive "to_upgrade" 2.457
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.946
Then the running Tails is installed on USB drive "to_upgrade" 26.284
And I unplug USB drive "to_upgrade" 0.220
And I unplug USB drive "__internal" 0.227
After features/support/hooks.rb:330 0.942
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.190
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.253
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.282
Then all tps features from the old Tails version are active 1.684
And Tails is running from USB drive "to_upgrade" 0.332
And the boot device has safe access rights 3.586
And the expected persistent files created with the old Tails version are present in the filesystem 1.515
And all persistent directories from the old Tails version have safe access rights 2.535
After features/support/hooks.rb:330 1.187
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:50.075
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 13.099
And no SquashFS delta is installed 0.835
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.671
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.751
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.629
When the network is plugged 0.068
And Tor is ready 25.499
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.734
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.009
Given I shutdown Tails and wait for the computer to power off 9.001
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.844
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.371
And the file system changes introduced in version 6.2~testoverlayfs are present 0.290
And only the 6.2~testoverlayfs SquashFS delta is installed 0.092
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.327
# 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.316
When the network is plugged 0.068
And Tor is ready 16.128
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.539
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.407
Given I shutdown Tails and wait for the computer to power off 4.388
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.302
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.382
And the file system changes introduced in version 6.3~testoverlayfs are present 0.511
And only the 6.3~testoverlayfs SquashFS delta is installed 0.083
# 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.288
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.372
When the network is plugged 0.074
And Tor is ready 17.991
Then the Upgrader considers the system as up-to-date 0.353
# 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 15.807
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.736
After features/support/hooks.rb:330 0.899
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
39.869
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 10.659
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.509
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.113
And the signing key used by the Upgrader is outdated 0.133
But a current signing key is available on our website 0.000
When the network is plugged 0.102
And Tor is ready 21.375
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.975
After features/support/hooks.rb:330 0.779
After features/support/hooks.rb:100 0.000