Project Number Date
test_Tails_ISO_stable 5610 29 Apr 2025, 18: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:27.971 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:31.656
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.182
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 36.494
When I start Tails from USB drive "old" with network unplugged 1:49.933
Then the boot device has safe access rights 2.989
And Tails is running from USB drive "old" 0.344
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.282
And I unplug USB drive "old" 0.180
After features/support/hooks.rb:330 3.543
After features/support/hooks.rb:100 0.067
Tags: @product
2:17.241
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 1:34.521
Then Tails is running from USB drive "old" 0.385
And I create a persistent partition 31.195
And I take note of which tps features are available 1.782
Then a Tails persistence partition exists on USB drive "old" 0.729
And I shutdown Tails and wait for the computer to power off 8.434
After features/support/hooks.rb:330 0.140
After features/support/hooks.rb:100 0.007
Tags: @product
2:55.772
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.786
Then Tails is running from USB drive "old" 0.413
And all tps features are active 2.312
When I write some files expected to persist 2.037
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.197
And all persistence configuration files have safe access rights 0.405
And all persistent directories from the old Tails version have safe access rights 2.409
And I take note of which tps features are available 0.447
And I shutdown Tails and wait for the computer to power off 4.362
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.203
After features/support/hooks.rb:330 0.088
After features/support/hooks.rb:100 0.008
Tags: @product
2:39.077
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 without a persistent partition and stopped at Tails Greeter's login screen 11.420
And I log in to a new session 19.212
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.742
And I plug USB drive "to_upgrade" 2.395
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.042
Then the running Tails is installed on USB drive "to_upgrade" 28.594
And I unplug USB drive "to_upgrade" 0.273
And I unplug USB drive "__internal" 0.397
After features/support/hooks.rb:330 2.290
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.499
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.107
Then all tps features from the old Tails version are active 1.648
And Tails is running from USB drive "to_upgrade" 0.327
And the boot device has safe access rights 3.453
And the expected persistent files created with the old Tails version are present in the filesystem 1.424
And all persistent directories from the old Tails version have safe access rights 2.347
After features/support/hooks.rb:330 1.111
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
7:9.216
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.084
And no SquashFS delta is installed 0.356
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.269
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.090
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.276
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.513
When the network is plugged 0.226
And Tor is ready 22.509
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.107
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.778
Given I shutdown Tails and wait for the computer to power off 10.864
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.442
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.434
And the file system changes introduced in version 6.2~testoverlayfs are present 0.403
And only the 6.2~testoverlayfs SquashFS delta is installed 0.092
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.362
# 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.343
When the network is plugged 0.080
And Tor is ready 49.121
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.857
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.504
Given I shutdown Tails and wait for the computer to power off 6.576
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.303
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.630
And the file system changes introduced in version 6.3~testoverlayfs are present 0.504
And only the 6.3~testoverlayfs SquashFS delta is installed 0.088
# 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.347
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.309
When the network is plugged 0.095
And Tor is ready 17.553
Then the Upgrader considers the system as up-to-date 0.328
# 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.417
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.307
After features/support/hooks.rb:330 0.893
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
38.508
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 11.963
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.445
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.115
But a current signing key is available on our website 0.000
When the network is plugged 0.112
And Tor is ready 19.089
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.715
After features/support/hooks.rb:330 0.683
After features/support/hooks.rb:100 0.000