Project Number Date
test_Tails_ISO_devel 3708 24 Feb 2025, 12:42

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:39.641 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:6.587
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.207
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 31.690
When I start Tails from USB drive "old" with network unplugged 1:29.253
Then the boot device has safe access rights 3.279
And Tails is running from USB drive "old" 0.341
And there is no persistence partition on USB drive "old" 0.086
And process "udev-watchdog" is running 0.113
And udev-watchdog is monitoring the correct device 0.322
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:330 3.565
After features/support/hooks.rb:100 0.010
Tags: @product
2:3.071
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login 1:20.244
Then Tails is running from USB drive "old" 0.374
And I create a persistent partition 31.157
And I take note of which tps features are available 1.334
Then a Tails persistence partition exists on USB drive "old" 0.987
And I shutdown Tails and wait for the computer to power off 8.749
After features/support/hooks.rb:330 0.298
After features/support/hooks.rb:100 0.009
Tags: @product
2:51.893
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.413
Then Tails is running from USB drive "old" 0.815
And all tps features are active 2.136
When I write some files expected to persist 1.722
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.213
And all persistence configuration files have safe access rights 0.346
And all persistent directories from the old Tails version have safe access rights 2.817
And I take note of which tps features are available 0.591
And I shutdown Tails and wait for the computer to power off 6.317
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.288
After features/support/hooks.rb:330 0.119
After features/support/hooks.rb:100 0.009
Tags: @product
2:30.145
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.697
And I log in to a new session 19.360
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.520
And I plug USB drive "to_upgrade" 2.465
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.651
Then the running Tails is installed on USB drive "to_upgrade" 21.030
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:330 2.453
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.225
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.217
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.046
Then all tps features from the old Tails version are active 1.628
And Tails is running from USB drive "to_upgrade" 0.307
And the boot device has safe access rights 3.430
And the expected persistent files created with the old Tails version are present in the filesystem 1.852
And all persistent directories from the old Tails version have safe access rights 2.741
After features/support/hooks.rb:330 1.110
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
7:12.289
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 13.590
And no SquashFS delta is installed 0.100
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.383
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.087
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.373
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.599
When the network is plugged 0.071
And Tor is ready 49.381
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.581
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.936
Given I shutdown Tails and wait for the computer to power off 10.835
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.057
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.267
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.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.304
# 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.245
When the network is plugged 0.083
And Tor is ready 17.588
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.023
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.343
Given I shutdown Tails and wait for the computer to power off 4.427
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.968
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.452
And the file system changes introduced in version 6.3~testoverlayfs are present 0.485
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.319
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.356
When the network is plugged 0.074
And Tor is ready 17.715
Then the Upgrader considers the system as up-to-date 0.390
# 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.810
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.975
After features/support/hooks.rb:330 1.059
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
33.428
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.676
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.057
And the signing key used by the Upgrader is outdated 0.078
But a current signing key is available on our website 0.000
When the network is plugged 0.101
And Tor is ready 18.130
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.046
After features/support/hooks.rb:330 1.915
After features/support/hooks.rb:100 0.000