Project Number Date
test_Tails_ISO_devel 3820 19 May 2025, 10:50

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:47.380 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:25.357
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.230
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 38.679
When I start Tails from USB drive "old" with network unplugged 1:40.849
Then the boot device has safe access rights 3.332
And Tails is running from USB drive "old" 0.367
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.357
And I unplug USB drive "old" 0.259
After features/support/hooks.rb:330 3.845
After features/support/hooks.rb:100 0.014
Tags: @product
2:16.970
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.257
And I start Tails from USB drive "old" with network unplugged and I login 1:32.413
Then Tails is running from USB drive "old" 0.377
And I create a persistent partition 31.477
And I take note of which tps features are available 2.711
Then a Tails persistence partition exists on USB drive "old" 0.854
And I shutdown Tails and wait for the computer to power off 8.878
After features/support/hooks.rb:330 0.193
After features/support/hooks.rb:100 0.011
Tags: @product
3:9.814
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:29.963
Then Tails is running from USB drive "old" 0.326
And all tps features are active 2.355
When I write some files expected to persist 1.950
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.238
And all persistence configuration files have safe access rights 0.403
And all persistent directories from the old Tails version have safe access rights 2.587
And I take note of which tps features are available 0.480
And I shutdown Tails and wait for the computer to power off 6.381
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.908
After features/support/hooks.rb:330 0.137
After features/support/hooks.rb:100 0.008
Tags: @product
2:48.562
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.737
And I log in to a new session 26.405
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.809
And I plug USB drive "to_upgrade" 2.451
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.384
Then the running Tails is installed on USB drive "to_upgrade" 25.274
And I unplug USB drive "to_upgrade" 0.271
And I unplug USB drive "__internal" 0.229
After features/support/hooks.rb:330 3.145
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.931
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.230
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.933
Then all tps features from the old Tails version are active 5.313
And Tails is running from USB drive "to_upgrade" 0.397
And the boot device has safe access rights 3.818
And the expected persistent files created with the old Tails version are present in the filesystem 1.596
And all persistent directories from the old Tails version have safe access rights 2.641
After features/support/hooks.rb:330 2.185
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
8:2.291
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 32.051
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.525
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.177
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.353
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.478
When the network is plugged 0.079
And Tor is ready 51.502
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.633
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.271
Given I shutdown Tails and wait for the computer to power off 8.465
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.082
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.619
And the file system changes introduced in version 6.2~testoverlayfs are present 0.340
And only the 6.2~testoverlayfs SquashFS delta is installed 0.091
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.321
# 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.279
When the network is plugged 0.079
And Tor is ready 48.733
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.665
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.088
Given I shutdown Tails and wait for the computer to power off 4.776
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.435
Then Tails is running version 6.3~testoverlayfs 0.043
And all tps features are active 2.313
And the file system changes introduced in version 6.3~testoverlayfs are present 0.492
And only the 6.3~testoverlayfs SquashFS delta is installed 0.099
# 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.314
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.306
When the network is plugged 0.067
And Tor is ready 17.192
Then the Upgrader considers the system as up-to-date 0.325
# 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.267
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.718
After features/support/hooks.rb:330 1.060
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
37.451
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 9.486
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.676
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.087
And the signing key used by the Upgrader is outdated 0.085
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 20.126
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.919
After features/support/hooks.rb:330 0.760
After features/support/hooks.rb:100 0.000