Project Number Date
test_Tails_ISO_stable 5481 26 Feb 2025, 12:37

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:22.164 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:18.938
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.211
And I create a 7200 MiB disk named "old" 0.076
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 30.857
When I start Tails from USB drive "old" with network unplugged 1:42.404
Then the boot device has safe access rights 3.209
And Tails is running from USB drive "old" 0.347
And there is no persistence partition on USB drive "old" 0.102
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.371
And I unplug USB drive "old" 0.207
After features/support/hooks.rb:330 3.754
After features/support/hooks.rb:100 0.009
Tags: @product
2:14.454
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login 1:28.086
Then Tails is running from USB drive "old" 0.412
And I create a persistent partition 32.402
And I take note of which tps features are available 1.764
Then a Tails persistence partition exists on USB drive "old" 0.861
And I shutdown Tails and wait for the computer to power off 10.714
After features/support/hooks.rb:330 0.271
After features/support/hooks.rb:100 0.010
Tags: @product
3:6.943
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.819
Then Tails is running from USB drive "old" 1.214
And all tps features are active 2.156
When I write some files expected to persist 1.819
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.253
And all persistence configuration files have safe access rights 0.517
And all persistent directories from the old Tails version have safe access rights 2.846
And I take note of which tps features are available 1.505
And I shutdown Tails and wait for the computer to power off 6.462
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.128
After features/support/hooks.rb:330 0.130
After features/support/hooks.rb:100 0.010
Tags: @product
2:29.686
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 10.888
And I log in to a new session 19.641
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.669
And I plug USB drive "to_upgrade" 2.414
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.641
Then the running Tails is installed on USB drive "to_upgrade" 20.931
And I unplug USB drive "to_upgrade" 0.287
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:330 8.423
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.205
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.735
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.040
Then all tps features from the old Tails version are active 2.089
And Tails is running from USB drive "to_upgrade" 0.413
And the boot device has safe access rights 3.661
And the expected persistent files created with the old Tails version are present in the filesystem 1.491
And all persistent directories from the old Tails version have safe access rights 2.773
After features/support/hooks.rb:330 1.356
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:14.499
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.731
And no SquashFS delta is installed 0.185
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.617
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.411
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.469
When the network is plugged 0.080
And Tor is ready 21.153
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.189
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.614
Given I shutdown Tails and wait for the computer to power off 8.671
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:20.953
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.509
And the file system changes introduced in version 6.2~testoverlayfs are present 0.335
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.320
# 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.078
And Tor is ready 46.037
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.582
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.261
Given I shutdown Tails and wait for the computer to power off 4.236
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.205
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.278
And the file system changes introduced in version 6.3~testoverlayfs are present 0.502
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.301
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.280
When the network is plugged 0.092
And Tor is ready 15.288
Then the Upgrader considers the system as up-to-date 10.773
# 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 14.643
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.102
After features/support/hooks.rb:330 0.838
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
37.434
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 10.604
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.579
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.089
And the signing key used by the Upgrader is outdated 0.120
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 19.630
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.338
After features/support/hooks.rb:330 1.158
After features/support/hooks.rb:100 0.000