Project Number Date
test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution 4 10 Apr 2025, 17:06

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:12.177 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:21.209
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.241
And I create a 7200 MiB disk named "old" 0.117
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 36.146
When I start Tails from USB drive "old" with network unplugged 1:39.218
Then the boot device has safe access rights 3.319
And Tails is running from USB drive "old" 0.346
And there is no persistence partition on USB drive "old" 0.084
And process "udev-watchdog" is running 0.111
And udev-watchdog is monitoring the correct device 0.304
And I unplug USB drive "old" 0.256
After features/support/hooks.rb:330 7.101
After features/support/hooks.rb:100 0.010
Tags: @product
2:15.916
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.994
And I start Tails from USB drive "old" with network unplugged and I login 1:33.593
Then Tails is running from USB drive "old" 0.359
And I create a persistent partition 31.525
And I take note of which tps features are available 2.025
Then a Tails persistence partition exists on USB drive "old" 0.791
And I shutdown Tails and wait for the computer to power off 6.625
After features/support/hooks.rb:330 0.135
After features/support/hooks.rb:100 0.010
Tags: @product
2:57.839
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.467
Then Tails is running from USB drive "old" 0.373
And all tps features are active 2.346
When I write some files expected to persist 2.739
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.224
And all persistence configuration files have safe access rights 0.409
And all persistent directories from the old Tails version have safe access rights 2.754
And I take note of which tps features are available 0.490
And I shutdown Tails and wait for the computer to power off 6.601
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.215
After features/support/hooks.rb:330 0.174
After features/support/hooks.rb:100 0.012
Tags: @product
2:35.340
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.024
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.785
And I log in to a new session 20.282
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.552
And I plug USB drive "to_upgrade" 2.397
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.200
Then the running Tails is installed on USB drive "to_upgrade" 22.698
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.214
After features/support/hooks.rb:330 2.419
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.570
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.223
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.039
Then all tps features from the old Tails version are active 1.790
And Tails is running from USB drive "to_upgrade" 0.325
And the boot device has safe access rights 3.891
And the expected persistent files created with the old Tails version are present in the filesystem 1.641
And all persistent directories from the old Tails version have safe access rights 2.657
After features/support/hooks.rb:330 1.148
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:53.413
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.531
And no SquashFS delta is installed 0.348
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.597
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.092
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.368
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.474
When the network is plugged 0.089
And Tor is ready 23.747
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.023
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.911
Given I shutdown Tails and wait for the computer to power off 8.857
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.789
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.348
And the file system changes introduced in version 6.2~testoverlayfs are present 0.385
And only the 6.2~testoverlayfs SquashFS delta is installed 0.126
# 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.312
When the network is plugged 0.083
And Tor is ready 16.868
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.238
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.230
Given I shutdown Tails and wait for the computer to power off 4.393
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.534
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 3.838
And the file system changes introduced in version 6.3~testoverlayfs are present 0.564
And only the 6.3~testoverlayfs SquashFS delta is installed 0.083
# 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.420
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.325
When the network is plugged 0.103
And Tor is ready 18.702
Then the Upgrader considers the system as up-to-date 0.343
# 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.768
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.516
After features/support/hooks.rb:330 0.797
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
45.888
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.567
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.125
And the signing key used by the Upgrader is outdated 0.148
But a current signing key is available on our website 0.000
When the network is plugged 0.118
And Tor is ready 20.824
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.003
After features/support/hooks.rb:330 0.828
After features/support/hooks.rb:100 0.000