Project Number Date
test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution 19 17 Apr 2025, 23:31

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:50.882 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:6.801
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.194
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 31.820
When I start Tails from USB drive "old" with network unplugged 1:29.497
Then the boot device has safe access rights 3.152
And Tails is running from USB drive "old" 0.338
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.326
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:330 3.765
After features/support/hooks.rb:100 0.009
Tags: @product
2:11.603
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login 1:27.493
Then Tails is running from USB drive "old" 0.440
And I create a persistent partition 32.404
And I take note of which tps features are available 1.697
Then a Tails persistence partition exists on USB drive "old" 0.809
And I shutdown Tails and wait for the computer to power off 8.567
After features/support/hooks.rb:330 0.209
After features/support/hooks.rb:100 0.011
Tags: @product
2:51.518
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.230
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.886
Then Tails is running from USB drive "old" 0.519
And all tps features are active 2.144
When I write some files expected to persist 1.772
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.237
And all persistence configuration files have safe access rights 0.531
And all persistent directories from the old Tails version have safe access rights 2.556
And I take note of which tps features are available 0.404
And I shutdown Tails and wait for the computer to power off 6.522
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.712
After features/support/hooks.rb:330 0.109
After features/support/hooks.rb:100 0.011
Tags: @product
2:35.198
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.687
And I log in to a new session 20.794
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.805
And I plug USB drive "to_upgrade" 2.426
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.358
Then the running Tails is installed on USB drive "to_upgrade" 23.639
And I unplug USB drive "to_upgrade" 0.241
And I unplug USB drive "__internal" 0.244
After features/support/hooks.rb:330 1.163
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.603
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.328
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.768
Then all tps features from the old Tails version are active 1.666
And Tails is running from USB drive "to_upgrade" 0.375
And the boot device has safe access rights 3.419
And the expected persistent files created with the old Tails version are present in the filesystem 1.576
And all persistent directories from the old Tails version have safe access rights 2.467
After features/support/hooks.rb:330 1.371
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:44.619
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.214
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.473
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.334
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.472
When the network is plugged 0.066
And Tor is ready 23.059
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.919
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.947
Given I shutdown Tails and wait for the computer to power off 8.809
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.916
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.523
And the file system changes introduced in version 6.2~testoverlayfs are present 0.328
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.381
# 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.245
When the network is plugged 0.095
And Tor is ready 18.365
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.757
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.347
Given I shutdown Tails and wait for the computer to power off 4.475
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.434
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.088
And the file system changes introduced in version 6.3~testoverlayfs are present 0.503
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.309
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.281
When the network is plugged 0.062
And Tor is ready 19.184
Then the Upgrader considers the system as up-to-date 0.316
# 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.522
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.824
After features/support/hooks.rb:330 0.712
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
1:0.537
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 9.672
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.324
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the signing key used by the Upgrader is outdated 0.139
But a current signing key is available on our website 0.000
When the network is plugged 0.235
And Tor is ready 49.447
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.642
After features/support/hooks.rb:330 1.010
After features/support/hooks.rb:100 0.000