Project Number Date
test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution 16 14 Apr 2025, 22:47

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:37.122 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:4.803
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.047
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 33.239
When I start Tails from USB drive "old" with network unplugged 1:26.293
Then the boot device has safe access rights 3.028
And Tails is running from USB drive "old" 0.306
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.282
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:330 3.548
After features/support/hooks.rb:100 0.007
Tags: @product
2:12.990
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.173
And I start Tails from USB drive "old" with network unplugged and I login 1:29.533
Then Tails is running from USB drive "old" 0.394
And I create a persistent partition 31.711
And I take note of which tps features are available 1.648
Then a Tails persistence partition exists on USB drive "old" 0.749
And I shutdown Tails and wait for the computer to power off 8.778
After features/support/hooks.rb:330 0.254
After features/support/hooks.rb:100 0.009
Tags: @product
2:53.711
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.532
Then Tails is running from USB drive "old" 0.475
And all tps features are active 2.244
When I write some files expected to persist 1.723
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.238
And all persistence configuration files have safe access rights 0.418
And all persistent directories from the old Tails version have safe access rights 2.828
And I take note of which tps features are available 0.494
And I shutdown Tails and wait for the computer to power off 4.756
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.817
After features/support/hooks.rb:330 0.155
After features/support/hooks.rb:100 0.008
Tags: @product
2:34.366
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.506
And I log in to a new session 19.334
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.597
And I plug USB drive "to_upgrade" 2.420
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.748
Then the running Tails is installed on USB drive "to_upgrade" 25.340
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:330 1.036
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.823
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.181
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.624
Then all tps features from the old Tails version are active 1.510
And Tails is running from USB drive "to_upgrade" 0.333
And the boot device has safe access rights 3.376
And the expected persistent files created with the old Tails version are present in the filesystem 1.429
And all persistent directories from the old Tails version have safe access rights 2.368
After features/support/hooks.rb:330 1.304
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
7:58.678
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.606
And no SquashFS delta is installed 0.098
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.511
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.306
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.534
When the network is plugged 0.184
And Tor is ready 22.288
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.089
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.732
Given I shutdown Tails and wait for the computer to power off 1:32.674
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.770
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.238
And the file system changes introduced in version 6.2~testoverlayfs are present 0.358
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.333
# 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.291
When the network is plugged 0.068
And Tor is ready 18.820
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.898
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.722
Given I shutdown Tails and wait for the computer to power off 4.335
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.934
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.007
And the file system changes introduced in version 6.3~testoverlayfs are present 0.485
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.347
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.340
When the network is plugged 0.076
And Tor is ready 18.061
Then the Upgrader considers the system as up-to-date 0.353
# 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.876
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.089
After features/support/hooks.rb:330 0.851
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
37.749
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.224
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.369
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.117
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 19.600
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.302
After features/support/hooks.rb:330 0.798
After features/support/hooks.rb:100 0.000