Project Number Date
test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution 3 09 Apr 2025, 22:48

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:36.641 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:12.825
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.203
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 37.445
When I start Tails from USB drive "old" with network unplugged 1:29.874
Then the boot device has safe access rights 3.120
And Tails is running from USB drive "old" 0.330
And there is no persistence partition on USB drive "old" 0.083
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.349
And I unplug USB drive "old" 0.211
After features/support/hooks.rb:330 7.035
After features/support/hooks.rb:100 0.008
Tags: @product
2:19.906
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login 1:36.509
Then Tails is running from USB drive "old" 0.394
And I create a persistent partition 31.341
And I take note of which tps features are available 1.979
Then a Tails persistence partition exists on USB drive "old" 0.845
And I shutdown Tails and wait for the computer to power off 8.622
After features/support/hooks.rb:330 0.189
After features/support/hooks.rb:100 0.012
Tags: @product
2:59.239
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.256
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.458
Then Tails is running from USB drive "old" 1.323
And all tps features are active 2.096
When I write some files expected to persist 1.880
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.229
And all persistence configuration files have safe access rights 0.403
And all persistent directories from the old Tails version have safe access rights 4.354
And I take note of which tps features are available 0.484
And I shutdown Tails and wait for the computer to power off 6.328
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.422
After features/support/hooks.rb:330 0.129
After features/support/hooks.rb:100 0.019
Tags: @product
2:37.505
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 11.552
And I log in to a new session 21.903
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.655
And I plug USB drive "to_upgrade" 2.482
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.928
Then the running Tails is installed on USB drive "to_upgrade" 22.459
And I unplug USB drive "to_upgrade" 0.230
And I unplug USB drive "__internal" 0.291
After features/support/hooks.rb:330 0.996
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.130
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.332
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.188
Then all tps features from the old Tails version are active 1.800
And Tails is running from USB drive "to_upgrade" 0.407
And the boot device has safe access rights 3.401
And the expected persistent files created with the old Tails version are present in the filesystem 1.496
And all persistent directories from the old Tails version have safe access rights 2.502
After features/support/hooks.rb:330 1.258
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
6:57.623
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 with a persistent partition enabled and logged in 14.632
And no SquashFS delta is installed 0.123
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.609
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.251
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.485
When the network is plugged 0.073
And Tor is ready 23.377
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.144
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.290
Given I shutdown Tails and wait for the computer to power off 10.758
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.645
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.573
And the file system changes introduced in version 6.2~testoverlayfs are present 0.442
And only the 6.2~testoverlayfs SquashFS delta is installed 0.137
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.325
# 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.342
When the network is plugged 0.094
And Tor is ready 17.535
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.743
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 13.952
Given I shutdown Tails and wait for the computer to power off 4.380
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.428
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.127
And the file system changes introduced in version 6.3~testoverlayfs are present 0.443
And only the 6.3~testoverlayfs SquashFS delta is installed 0.088
# 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.309
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.359
When the network is plugged 0.067
And Tor is ready 20.570
Then the Upgrader considers the system as up-to-date 0.321
# 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.535
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.345
After features/support/hooks.rb:330 0.672
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
1:3.410
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.722
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.549
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.078
But a current signing key is available on our website 0.000
When the network is plugged 0.066
And Tor is ready 52.322
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.613
After features/support/hooks.rb:330 0.970
After features/support/hooks.rb:100 0.000