Project Number Date
test_Tails_ISO_stable 5492 04 Mar 2025, 15:39

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:58.487 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:24.318
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.188
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 32.052
When I start Tails from USB drive "old" with network unplugged 1:46.760
Then the boot device has safe access rights 3.178
And Tails is running from USB drive "old" 0.317
And there is no persistence partition on USB drive "old" 0.089
And process "udev-watchdog" is running 0.111
And udev-watchdog is monitoring the correct device 0.343
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:330 3.798
After features/support/hooks.rb:100 0.009
Tags: @product
2:17.632
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login 1:33.913
Then Tails is running from USB drive "old" 0.331
And I create a persistent partition 32.074
And I take note of which tps features are available 1.497
Then a Tails persistence partition exists on USB drive "old" 0.888
And I shutdown Tails and wait for the computer to power off 8.739
After features/support/hooks.rb:330 0.255
After features/support/hooks.rb:100 0.011
Tags: @product
2:54.494
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.566
Then Tails is running from USB drive "old" 0.387
And all tps features are active 1.933
When I write some files expected to persist 2.360
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.222
And all persistence configuration files have safe access rights 0.358
And all persistent directories from the old Tails version have safe access rights 2.433
And I take note of which tps features are available 0.417
And I shutdown Tails and wait for the computer to power off 4.413
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.223
After features/support/hooks.rb:330 0.131
After features/support/hooks.rb:100 0.009
Tags: @product
2:35.461
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.909
And I log in to a new session 19.007
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.157
And I plug USB drive "to_upgrade" 2.386
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.516
Then the running Tails is installed on USB drive "to_upgrade" 26.025
And I unplug USB drive "to_upgrade" 0.234
And I unplug USB drive "__internal" 0.223
After features/support/hooks.rb:330 2.113
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.591
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.199
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.427
Then all tps features from the old Tails version are active 1.602
And Tails is running from USB drive "to_upgrade" 0.342
And the boot device has safe access rights 3.119
And the expected persistent files created with the old Tails version are present in the filesystem 1.490
And all persistent directories from the old Tails version have safe access rights 2.410
After features/support/hooks.rb:330 1.378
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:46.087
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 15.264
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.302
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.340
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.472
When the network is plugged 0.069
And Tor is ready 23.710
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.814
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.017
Given I shutdown Tails and wait for the computer to power off 8.870
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.459
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.548
And the file system changes introduced in version 6.2~testoverlayfs are present 0.355
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.287
# 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.295
When the network is plugged 0.063
And Tor is ready 19.467
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.628
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.908
Given I shutdown Tails and wait for the computer to power off 4.220
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.170
Then Tails is running version 6.3~testoverlayfs 0.024
And all tps features are active 2.254
And the file system changes introduced in version 6.3~testoverlayfs are present 0.494
And only the 6.3~testoverlayfs SquashFS delta is installed 0.084
# 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.322
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.367
When the network is plugged 0.103
And Tor is ready 18.447
Then the Upgrader considers the system as up-to-date 0.324
# 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.158
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.006
After features/support/hooks.rb:330 0.742
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
40.901
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 12.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.370
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.074
But a current signing key is available on our website 0.000
When the network is plugged 0.067
And Tor is ready 21.658
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.596
After features/support/hooks.rb:330 0.741
After features/support/hooks.rb:100 0.000