Project Number Date
test_Tails_ISO_stable 5483 27 Feb 2025, 12:33

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:37.615 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:10.141
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.232
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 31.490
When I start Tails from USB drive "old" with network unplugged 1:32.887
Then the boot device has safe access rights 3.340
And Tails is running from USB drive "old" 0.348
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.335
And I unplug USB drive "old" 0.228
After features/support/hooks.rb:330 3.570
After features/support/hooks.rb:100 0.014
Tags: @product
2:16.076
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login 1:31.818
Then Tails is running from USB drive "old" 0.326
And I create a persistent partition 32.696
And I take note of which tps features are available 1.461
Then a Tails persistence partition exists on USB drive "old" 0.915
And I shutdown Tails and wait for the computer to power off 8.652
After features/support/hooks.rb:330 0.246
After features/support/hooks.rb:100 0.011
Tags: @product
3:3.780
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.228
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.846
Then Tails is running from USB drive "old" 0.571
And all tps features are active 3.211
When I write some files expected to persist 1.930
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.217
And all persistence configuration files have safe access rights 0.371
And all persistent directories from the old Tails version have safe access rights 2.363
And I take note of which tps features are available 0.509
And I shutdown Tails and wait for the computer to power off 6.597
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.932
After features/support/hooks.rb:330 0.127
After features/support/hooks.rb:100 0.009
Tags: @product
2:29.961
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 10.624
And I log in to a new session 19.280
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.689
And I plug USB drive "to_upgrade" 2.485
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.491
Then the running Tails is installed on USB drive "to_upgrade" 21.907
And I unplug USB drive "to_upgrade" 0.233
And I unplug USB drive "__internal" 0.248
After features/support/hooks.rb:330 2.797
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.917
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.244
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.512
Then all tps features from the old Tails version are active 1.969
And Tails is running from USB drive "to_upgrade" 0.406
And the boot device has safe access rights 3.707
And the expected persistent files created with the old Tails version are present in the filesystem 1.646
And all persistent directories from the old Tails version have safe access rights 2.430
After features/support/hooks.rb:330 1.448
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:43.543
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.823
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.395
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.385
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.419
When the network is plugged 0.417
And Tor is ready 20.982
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.371
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.360
Given I shutdown Tails and wait for the computer to power off 8.837
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.986
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.111
And the file system changes introduced in version 6.2~testoverlayfs are present 0.287
And only the 6.2~testoverlayfs SquashFS delta is installed 0.086
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.416
# 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.330
When the network is plugged 0.066
And Tor is ready 19.726
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.951
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.145
Given I shutdown Tails and wait for the computer to power off 4.327
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.371
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 2.125
And the file system changes introduced in version 6.3~testoverlayfs are present 0.552
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.388
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.272
When the network is plugged 0.076
And Tor is ready 19.428
Then the Upgrader considers the system as up-to-date 0.307
# 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.378
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.958
After features/support/hooks.rb:330 0.711
After features/support/hooks.rb:100 0.036
Tags: @product @automatic_upgrade
34.194
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 10.574
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.485
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.133
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 16.062
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.817
After features/support/hooks.rb:330 1.172
After features/support/hooks.rb:100 0.000