Project Number Date
test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution 18 16 Apr 2025, 23:01

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:34.786 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:8.337
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.179
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 28.203
When I start Tails from USB drive "old" with network unplugged 1:34.617
Then the boot device has safe access rights 3.175
And Tails is running from USB drive "old" 0.356
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.335
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:330 1.198
After features/support/hooks.rb:100 0.008
Tags: @product
2:10.875
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.238
And I start Tails from USB drive "old" with network unplugged and I login 1:24.876
Then Tails is running from USB drive "old" 0.393
And I create a persistent partition 29.965
And I take note of which tps features are available 4.190
Then a Tails persistence partition exists on USB drive "old" 1.590
And I shutdown Tails and wait for the computer to power off 9.620
After features/support/hooks.rb:330 0.190
After features/support/hooks.rb:100 0.010
Tags: @product
2:57.459
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.368
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.563
Then Tails is running from USB drive "old" 0.359
And all tps features are active 2.062
When I write some files expected to persist 1.999
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.232
And all persistence configuration files have safe access rights 0.374
And all persistent directories from the old Tails version have safe access rights 2.473
And I take note of which tps features are available 0.455
And I shutdown Tails and wait for the computer to power off 6.344
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.224
After features/support/hooks.rb:330 0.159
After features/support/hooks.rb:100 0.011
Tags: @product
2:38.951
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.773
And I log in to a new session 21.407
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.869
And I plug USB drive "to_upgrade" 2.569
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.585
Then the running Tails is installed on USB drive "to_upgrade" 27.303
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.234
After features/support/hooks.rb:330 2.299
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.841
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.185
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.682
Then all tps features from the old Tails version are active 1.491
And Tails is running from USB drive "to_upgrade" 0.390
And the boot device has safe access rights 3.278
And the expected persistent files created with the old Tails version are present in the filesystem 1.377
And all persistent directories from the old Tails version have safe access rights 2.436
After features/support/hooks.rb:330 0.713
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:45.677
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 16.745
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.570
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.370
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.547
When the network is plugged 0.064
And Tor is ready 17.768
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.825
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.751
Given I shutdown Tails and wait for the computer to power off 9.022
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.254
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.281
And the file system changes introduced in version 6.2~testoverlayfs are present 0.322
And only the 6.2~testoverlayfs SquashFS delta is installed 0.091
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.377
# 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.302
When the network is plugged 0.081
And Tor is ready 21.015
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.662
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.761
Given I shutdown Tails and wait for the computer to power off 4.484
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.217
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.110
And the file system changes introduced in version 6.3~testoverlayfs are present 0.525
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.320
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.341
When the network is plugged 0.101
And Tor is ready 18.198
Then the Upgrader considers the system as up-to-date 10.870
# 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.659
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.783
After features/support/hooks.rb:330 0.844
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
34.642
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.307
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.678
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.109
And the signing key used by the Upgrader is outdated 0.112
But a current signing key is available on our website 0.000
When the network is plugged 0.107
And Tor is ready 16.612
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.713
After features/support/hooks.rb:330 2.157
After features/support/hooks.rb:100 0.000