Project Number Date
test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution 23 21 Apr 2025, 22:30

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:19.043 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:3.004
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.218
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 31.179
When I start Tails from USB drive "old" with network unplugged 1:26.428
Then the boot device has safe access rights 3.035
And Tails is running from USB drive "old" 0.364
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.113
And udev-watchdog is monitoring the correct device 0.309
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:330 6.960
After features/support/hooks.rb:100 0.049
Tags: @product
2:3.847
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login 1:22.247
Then Tails is running from USB drive "old" 0.342
And I create a persistent partition 30.486
And I take note of which tps features are available 1.648
Then a Tails persistence partition exists on USB drive "old" 0.768
And I shutdown Tails and wait for the computer to power off 8.169
After features/support/hooks.rb:330 0.128
After features/support/hooks.rb:100 0.008
Tags: @product
2:43.535
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:7.622
Then Tails is running from USB drive "old" 0.796
And all tps features are active 1.848
When I write some files expected to persist 1.665
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.278
And all persistence configuration files have safe access rights 0.411
And all persistent directories from the old Tails version have safe access rights 2.230
And I take note of which tps features are available 0.407
And I shutdown Tails and wait for the computer to power off 4.268
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.806
After features/support/hooks.rb:330 0.132
After features/support/hooks.rb:100 0.009
Tags: @product
2:30.296
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 9.551
And I log in to a new session 18.569
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.392
And I plug USB drive "to_upgrade" 2.358
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.875
Then the running Tails is installed on USB drive "to_upgrade" 25.118
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:330 0.641
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.304
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.187
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.634
Then all tps features from the old Tails version are active 1.982
And Tails is running from USB drive "to_upgrade" 0.373
And the boot device has safe access rights 3.773
And the expected persistent files created with the old Tails version are present in the filesystem 1.555
And all persistent directories from the old Tails version have safe access rights 2.797
After features/support/hooks.rb:330 1.288
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
6:57.832
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.749
And no SquashFS delta is installed 0.096
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.327
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.481
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.683
When the network is plugged 0.078
And Tor is ready 22.574
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.220
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.533
Given I shutdown Tails and wait for the computer to power off 10.795
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.791
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.261
And the file system changes introduced in version 6.2~testoverlayfs are present 0.322
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.304
# 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.280
When the network is plugged 0.074
And Tor is ready 17.218
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 9.205
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.428
Given I shutdown Tails and wait for the computer to power off 4.596
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.328
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.023
And the file system changes introduced in version 6.3~testoverlayfs are present 0.495
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.311
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.253
When the network is plugged 0.089
And Tor is ready 45.086
Then the Upgrader considers the system as up-to-date 0.355
# 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.193
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.428
After features/support/hooks.rb:330 0.751
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
41.221
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 9.855
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.680
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.137
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 22.584
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.831
After features/support/hooks.rb:330 0.677
After features/support/hooks.rb:100 0.000