Project Number Date
test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution 26 24 Apr 2025, 23:16

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:6.199 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:23.735
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.187
And I create a 7200 MiB disk named "old" 0.057
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 36.691
When I start Tails from USB drive "old" with network unplugged 1:41.393
Then the boot device has safe access rights 3.263
And Tails is running from USB drive "old" 0.394
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.307
And I unplug USB drive "old" 0.225
After features/support/hooks.rb:330 3.761
After features/support/hooks.rb:100 0.010
Tags: @product
2:12.478
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login 1:27.133
Then Tails is running from USB drive "old" 0.350
And I create a persistent partition 31.777
And I take note of which tps features are available 3.829
Then a Tails persistence partition exists on USB drive "old" 0.790
And I shutdown Tails and wait for the computer to power off 8.366
After features/support/hooks.rb:330 0.188
After features/support/hooks.rb:100 0.008
Tags: @product
3:9.189
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.077
Then Tails is running from USB drive "old" 2.326
And all tps features are active 3.363
When I write some files expected to persist 3.513
# 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.525
And all persistent directories from the old Tails version have safe access rights 3.481
And I take note of which tps features are available 1.113
And I shutdown Tails and wait for the computer to power off 6.538
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.834
After features/support/hooks.rb:330 0.143
After features/support/hooks.rb:100 0.010
Tags: @product
2:36.263
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 12.172
And I log in to a new session 20.034
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.807
And I plug USB drive "to_upgrade" 2.414
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.147
Then the running Tails is installed on USB drive "to_upgrade" 25.190
And I unplug USB drive "to_upgrade" 0.280
And I unplug USB drive "__internal" 0.215
After features/support/hooks.rb:330 0.837
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.462
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.197
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.539
Then all tps features from the old Tails version are active 1.736
And Tails is running from USB drive "to_upgrade" 0.322
And the boot device has safe access rights 3.417
And the expected persistent files created with the old Tails version are present in the filesystem 1.396
And all persistent directories from the old Tails version have safe access rights 2.852
After features/support/hooks.rb:330 1.378
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:39.426
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.505
And no SquashFS delta is installed 0.131
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.400
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
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.521
When the network is plugged 0.068
And Tor is ready 18.961
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.047
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.411
Given I shutdown Tails and wait for the computer to power off 8.913
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.553
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.262
And the file system changes introduced in version 6.2~testoverlayfs are present 0.296
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.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.248
When the network is plugged 0.080
And Tor is ready 16.629
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.923
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.147
Given I shutdown Tails and wait for the computer to power off 5.454
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.971
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.989
And the file system changes introduced in version 6.3~testoverlayfs are present 0.457
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.405
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.245
When the network is plugged 0.096
And Tor is ready 19.331
Then the Upgrader considers the system as up-to-date 0.301
# 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 16.652
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.607
After features/support/hooks.rb:330 0.747
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
37.643
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 with a persistent partition enabled and logged in 9.817
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.410
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.180
And the signing key used by the Upgrader is outdated 0.104
But a current signing key is available on our website 0.000
When the network is plugged 0.089
And Tor is ready 20.049
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.991
After features/support/hooks.rb:330 0.875
After features/support/hooks.rb:100 0.000