Project Number Date
test_Tails_ISO_devel 3831 23 May 2025, 09:48

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:11.119 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:15.414
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.202
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 33.091
When I start Tails from USB drive "old" with network unplugged 1:36.737
Then the boot device has safe access rights 3.234
And Tails is running from USB drive "old" 0.346
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.329
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:330 3.766
After features/support/hooks.rb:100 0.011
Tags: @product
2:23.284
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login 1:33.842
Then Tails is running from USB drive "old" 0.334
And I create a persistent partition 36.337
And I take note of which tps features are available 2.658
Then a Tails persistence partition exists on USB drive "old" 0.930
And I shutdown Tails and wait for the computer to power off 8.975
After features/support/hooks.rb:330 0.274
After features/support/hooks.rb:100 0.010
Tags: @product
2:57.935
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.262
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.836
Then Tails is running from USB drive "old" 0.329
And all tps features are active 2.158
When I write some files expected to persist 2.535
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.227
And all persistence configuration files have safe access rights 0.405
And all persistent directories from the old Tails version have safe access rights 3.042
And I take note of which tps features are available 0.514
And I shutdown Tails and wait for the computer to power off 4.165
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.458
After features/support/hooks.rb:330 0.125
After features/support/hooks.rb:100 0.010
Tags: @product
2:37.163
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 without a persistent partition and stopped at Tails Greeter's login screen 11.196
And I log in to a new session 22.065
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.847
And I plug USB drive "to_upgrade" 2.459
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.926
Then the running Tails is installed on USB drive "to_upgrade" 25.226
And I unplug USB drive "to_upgrade" 0.224
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:330 2.376
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.301
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.217
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.463
Then all tps features from the old Tails version are active 1.678
And Tails is running from USB drive "to_upgrade" 0.348
And the boot device has safe access rights 3.646
And the expected persistent files created with the old Tails version are present in the filesystem 1.546
And all persistent directories from the old Tails version have safe access rights 2.400
After features/support/hooks.rb:330 0.961
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:56.248
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 12.499
And no SquashFS delta is installed 0.128
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.392
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.122
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.345
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.526
When the network is plugged 0.074
And Tor is ready 20.795
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.949
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.720
Given I shutdown Tails and wait for the computer to power off 11.026
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.543
Then Tails is running version 6.2~testoverlayfs 0.028
And all tps features are active 2.220
And the file system changes introduced in version 6.2~testoverlayfs are present 0.326
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.299
# 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.308
When the network is plugged 0.085
And Tor is ready 19.685
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.069
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.915
Given I shutdown Tails and wait for the computer to power off 4.371
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.348
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.072
And the file system changes introduced in version 6.3~testoverlayfs are present 0.491
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.307
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.350
When the network is plugged 0.349
And Tor is ready 19.199
Then the Upgrader considers the system as up-to-date 10.833
# 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.070
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.628
After features/support/hooks.rb:330 0.669
After features/support/hooks.rb:100 0.049
Tags: @product @automatic_upgrade
40.770
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 11.506
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.338
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.084
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 19.727
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.981
After features/support/hooks.rb:330 0.909
After features/support/hooks.rb:100 0.000