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

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:24.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:9.189
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.198
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.101
And I write an old version of the Tails USB image to disk "old" 31.987
When I start Tails from USB drive "old" with network unplugged 1:31.611
Then the boot device has safe access rights 3.226
And Tails is running from USB drive "old" 0.343
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.335
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:330 3.704
After features/support/hooks.rb:100 0.007
Tags: @product
2:6.783
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login 1:24.929
Then Tails is running from USB drive "old" 0.319
And I create a persistent partition 30.292
And I take note of which tps features are available 1.578
Then a Tails persistence partition exists on USB drive "old" 0.830
And I shutdown Tails and wait for the computer to power off 8.637
After features/support/hooks.rb:330 0.161
After features/support/hooks.rb:100 0.009
Tags: @product
3:6.837
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:29.605
Then Tails is running from USB drive "old" 0.374
And all tps features are active 2.111
When I write some files expected to persist 1.865
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.240
And all persistence configuration files have safe access rights 0.488
And all persistent directories from the old Tails version have safe access rights 2.866
And I take note of which tps features are available 0.421
And I shutdown Tails and wait for the computer to power off 4.275
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.391
After features/support/hooks.rb:330 0.091
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.428
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.207
And I log in to a new session 19.210
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.711
And I plug USB drive "to_upgrade" 2.489
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.332
Then the running Tails is installed on USB drive "to_upgrade" 24.046
And I unplug USB drive "to_upgrade" 0.227
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:330 0.836
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.144
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.169
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.630
Then all tps features from the old Tails version are active 1.604
And Tails is running from USB drive "to_upgrade" 0.429
And the boot device has safe access rights 3.453
And the expected persistent files created with the old Tails version are present in the filesystem 1.411
And all persistent directories from the old Tails version have safe access rights 2.446
After features/support/hooks.rb:330 1.024
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:36.148
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 with a persistent partition enabled and logged in 10.943
And no SquashFS delta is installed 0.122
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.321
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.434
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.668
When the network is plugged 0.070
And Tor is ready 19.958
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.662
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.134
Given I shutdown Tails and wait for the computer to power off 11.306
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.629
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.226
And the file system changes introduced in version 6.2~testoverlayfs are present 0.310
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.307
# 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.286
When the network is plugged 0.087
And Tor is ready 18.195
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.773
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.455
Given I shutdown Tails and wait for the computer to power off 4.350
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.682
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 1.987
And the file system changes introduced in version 6.3~testoverlayfs are present 0.487
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.313
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.270
When the network is plugged 0.067
And Tor is ready 19.895
Then the Upgrader considers the system as up-to-date 0.306
# 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.140
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.512
After features/support/hooks.rb:330 0.718
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
34.082
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.193
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.300
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.067
But a current signing key is available on our website 0.000
When the network is plugged 0.091
And Tor is ready 19.159
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.209
After features/support/hooks.rb:330 0.737
After features/support/hooks.rb:100 0.000