Project Number Date
test_Tails_ISO_devel 3810 13 May 2025, 23:26

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:8.080 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:14.909
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.189
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 31.554
When I start Tails from USB drive "old" with network unplugged 1:37.898
Then the boot device has safe access rights 3.141
And Tails is running from USB drive "old" 0.378
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.274
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:330 3.589
After features/support/hooks.rb:100 0.029
Tags: @product
2:17.751
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 1:32.720
Then Tails is running from USB drive "old" 0.368
And I create a persistent partition 33.324
And I take note of which tps features are available 1.646
Then a Tails persistence partition exists on USB drive "old" 0.974
And I shutdown Tails and wait for the computer to power off 8.524
After features/support/hooks.rb:330 0.171
After features/support/hooks.rb:100 0.011
Tags: @product
3:3.913
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.219
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.849
Then Tails is running from USB drive "old" 0.391
And all tps features are active 4.107
When I write some files expected to persist 2.028
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.269
And all persistence configuration files have safe access rights 0.484
And all persistent directories from the old Tails version have safe access rights 3.009
And I take note of which tps features are available 1.321
And I shutdown Tails and wait for the computer to power off 6.806
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 27.424
After features/support/hooks.rb:330 0.217
After features/support/hooks.rb:100 0.011
Tags: @product
2:35.905
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 12.607
And I log in to a new session 21.363
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.575
And I plug USB drive "to_upgrade" 2.403
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.975
Then the running Tails is installed on USB drive "to_upgrade" 22.500
And I unplug USB drive "to_upgrade" 0.265
And I unplug USB drive "__internal" 0.214
After features/support/hooks.rb:330 3.590
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.334
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.223
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.071
Then all tps features from the old Tails version are active 1.818
And Tails is running from USB drive "to_upgrade" 0.340
And the boot device has safe access rights 3.850
And the expected persistent files created with the old Tails version are present in the filesystem 1.492
And all persistent directories from the old Tails version have safe access rights 2.537
After features/support/hooks.rb:330 1.363
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:57.580
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.803
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.314
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.096
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.348
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.598
When the network is plugged 0.066
And Tor is ready 23.096
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.863
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.380
Given I shutdown Tails and wait for the computer to power off 11.019
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.156
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.391
And the file system changes introduced in version 6.2~testoverlayfs are present 0.294
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.314
# 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.292
When the network is plugged 0.071
And Tor is ready 21.099
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.709
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.733
Given I shutdown Tails and wait for the computer to power off 6.580
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.278
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.287
And the file system changes introduced in version 6.3~testoverlayfs are present 0.585
And only the 6.3~testoverlayfs SquashFS delta is installed 0.168
# 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.422
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.383
When the network is plugged 0.072
And Tor is ready 19.692
Then the Upgrader considers the system as up-to-date 0.359
# 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 16.070
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.830
After features/support/hooks.rb:330 0.722
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
37.686
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 9.910
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.391
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.071
But a current signing key is available on our website 0.000
When the network is plugged 0.089
And Tor is ready 20.207
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.952
After features/support/hooks.rb:330 1.446
After features/support/hooks.rb:100 0.000