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

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:42.520 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:15.619
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 29.210
When I start Tails from USB drive "old" with network unplugged 1:41.229
Then the boot device has safe access rights 2.932
And Tails is running from USB drive "old" 0.329
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.285
And I unplug USB drive "old" 0.200
After features/support/hooks.rb:330 7.151
After features/support/hooks.rb:100 0.008
Tags: @product
2:18.626
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 1:35.600
Then Tails is running from USB drive "old" 0.377
And I create a persistent partition 31.175
And I take note of which tps features are available 1.894
Then a Tails persistence partition exists on USB drive "old" 0.797
And I shutdown Tails and wait for the computer to power off 8.588
After features/support/hooks.rb:330 0.153
After features/support/hooks.rb:100 0.008
Tags: @product
2:50.866
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 "old" with network unplugged and I login with persistence enabled 2:9.565
Then Tails is running from USB drive "old" 0.536
And all tps features are active 2.926
When I write some files expected to persist 1.935
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.233
And all persistence configuration files have safe access rights 0.457
And all persistent directories from the old Tails version have safe access rights 3.061
And I take note of which tps features are available 1.122
And I shutdown Tails and wait for the computer to power off 6.587
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.258
After features/support/hooks.rb:330 0.136
After features/support/hooks.rb:100 0.008
Tags: @product
2:25.789
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.390
And I log in to a new session 18.097
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.472
And I plug USB drive "to_upgrade" 2.386
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.658
Then the running Tails is installed on USB drive "to_upgrade" 19.338
And I unplug USB drive "to_upgrade" 0.215
And I unplug USB drive "__internal" 0.230
After features/support/hooks.rb:330 0.846
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.871
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.203
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.890
Then all tps features from the old Tails version are active 1.933
And Tails is running from USB drive "to_upgrade" 0.296
And the boot device has safe access rights 2.971
And the expected persistent files created with the old Tails version are present in the filesystem 1.300
And all persistent directories from the old Tails version have safe access rights 2.275
After features/support/hooks.rb:330 1.449
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:39.304
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.951
And no SquashFS delta is installed 0.104
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.451
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.090
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.394
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.597
When the network is plugged 0.139
And Tor is ready 19.509
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.780
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.310
Given I shutdown Tails and wait for the computer to power off 8.360
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.941
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.270
And the file system changes introduced in version 6.2~testoverlayfs are present 0.434
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.362
# 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.317
When the network is plugged 0.121
And Tor is ready 18.893
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.454
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.433
Given I shutdown Tails and wait for the computer to power off 4.324
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.493
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.012
And the file system changes introduced in version 6.3~testoverlayfs are present 0.446
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.290
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.271
When the network is plugged 0.077
And Tor is ready 18.006
Then the Upgrader considers the system as up-to-date 10.875
# 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.032
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.387
After features/support/hooks.rb:330 0.769
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
58.442
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 10.111
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.483
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.112
And the signing key used by the Upgrader is outdated 0.122
But a current signing key is available on our website 0.000
When the network is plugged 0.094
And Tor is ready 46.927
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.589
After features/support/hooks.rb:330 0.742
After features/support/hooks.rb:100 0.000