Project Number Date
test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution 28 26 Apr 2025, 22:25

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:8.094 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.394
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.176
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 30.322
When I start Tails from USB drive "old" with network unplugged 1:33.591
Then the boot device has safe access rights 3.143
And Tails is running from USB drive "old" 0.356
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.116
And udev-watchdog is monitoring the correct device 0.307
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:330 3.752
After features/support/hooks.rb:100 0.008
Tags: @product
2:3.653
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login 1:21.587
Then Tails is running from USB drive "old" 0.341
And I create a persistent partition 30.698
And I take note of which tps features are available 1.636
Then a Tails persistence partition exists on USB drive "old" 0.774
And I shutdown Tails and wait for the computer to power off 8.440
After features/support/hooks.rb:330 0.192
After features/support/hooks.rb:100 0.007
Tags: @product
2:47.227
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.141
Then Tails is running from USB drive "old" 0.378
And all tps features are active 1.916
When I write some files expected to persist 1.578
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.217
And all persistence configuration files have safe access rights 0.366
And all persistent directories from the old Tails version have safe access rights 2.668
And I take note of which tps features are available 0.420
And I shutdown Tails and wait for the computer to power off 4.671
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.685
After features/support/hooks.rb:330 0.107
After features/support/hooks.rb:100 0.009
Tags: @product
2:29.403
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 10.243
And I log in to a new session 17.902
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.494
And I plug USB drive "to_upgrade" 2.467
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.748
Then the running Tails is installed on USB drive "to_upgrade" 19.068
And I unplug USB drive "to_upgrade" 0.247
And I unplug USB drive "__internal" 0.231
After features/support/hooks.rb:330 2.258
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.625
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.186
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.237
Then all tps features from the old Tails version are active 1.860
And Tails is running from USB drive "to_upgrade" 0.380
And the boot device has safe access rights 3.815
And the expected persistent files created with the old Tails version are present in the filesystem 1.610
And all persistent directories from the old Tails version have safe access rights 2.533
After features/support/hooks.rb:330 1.342
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:37.616
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 13.076
And no SquashFS delta is installed 0.310
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.397
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.681
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.532
When the network is plugged 0.089
And Tor is ready 18.460
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.272
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.803
Given I shutdown Tails and wait for the computer to power off 8.511
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.973
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.235
And the file system changes introduced in version 6.2~testoverlayfs are present 0.453
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.329
# 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.289
When the network is plugged 0.073
And Tor is ready 21.442
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.291
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.993
Given I shutdown Tails and wait for the computer to power off 4.527
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.824
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.182
And the file system changes introduced in version 6.3~testoverlayfs are present 0.502
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.294
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.267
When the network is plugged 0.088
And Tor is ready 20.521
Then the Upgrader considers the system as up-to-date 0.322
# 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.034
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.587
After features/support/hooks.rb:330 0.747
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
38.172
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.712
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.491
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.095
And the signing key used by the Upgrader is outdated 0.110
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 19.823
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.865
After features/support/hooks.rb:330 0.981
After features/support/hooks.rb:100 0.000