Project Number Date
test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution 22 20 Apr 2025, 22:30

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:56.845 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
1:59.447
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.182
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 28.655
When I start Tails from USB drive "old" with network unplugged 1:25.633
Then the boot device has safe access rights 2.923
And Tails is running from USB drive "old" 0.293
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.298
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:330 7.084
After features/support/hooks.rb:100 0.012
Tags: @product
2:8.597
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.638
And I start Tails from USB drive "old" with network unplugged and I login 1:25.443
Then Tails is running from USB drive "old" 0.332
And I create a persistent partition 31.320
And I take note of which tps features are available 1.681
Then a Tails persistence partition exists on USB drive "old" 0.746
And I shutdown Tails and wait for the computer to power off 8.434
After features/support/hooks.rb:330 0.178
After features/support/hooks.rb:100 0.010
Tags: @product
3:0.736
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.858
Then Tails is running from USB drive "old" 1.038
And all tps features are active 2.009
When I write some files expected to persist 1.922
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.212
And all persistence configuration files have safe access rights 1.258
And all persistent directories from the old Tails version have safe access rights 2.777
And I take note of which tps features are available 0.445
And I shutdown Tails and wait for the computer to power off 6.301
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.713
After features/support/hooks.rb:330 0.149
After features/support/hooks.rb:100 0.012
Tags: @product
2:38.182
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 without a persistent partition and stopped at Tails Greeter's login screen 11.950
And I log in to a new session 18.359
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.609
And I plug USB drive "to_upgrade" 2.430
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.509
Then the running Tails is installed on USB drive "to_upgrade" 28.836
And I unplug USB drive "to_upgrade" 0.241
And I unplug USB drive "__internal" 0.244
After features/support/hooks.rb:330 0.795
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.294
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.321
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.132
Then all tps features from the old Tails version are active 1.654
And Tails is running from USB drive "to_upgrade" 0.324
And the boot device has safe access rights 3.865
And the expected persistent files created with the old Tails version are present in the filesystem 1.544
And all persistent directories from the old Tails version have safe access rights 2.451
After features/support/hooks.rb:330 1.291
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:11.899
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 16.309
And no SquashFS delta is installed 0.156
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.470
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.262
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.538
When the network is plugged 0.075
And Tor is ready 22.368
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.224
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.302
Given I shutdown Tails and wait for the computer to power off 12.941
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.073
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.176
And the file system changes introduced in version 6.2~testoverlayfs are present 0.331
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.305
# 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.281
When the network is plugged 0.083
And Tor is ready 47.443
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.582
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.443
Given I shutdown Tails and wait for the computer to power off 4.231
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.771
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 1.996
And the file system changes introduced in version 6.3~testoverlayfs are present 0.507
And only the 6.3~testoverlayfs SquashFS delta is installed 0.087
# 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.399
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.299
When the network is plugged 0.087
And Tor is ready 19.828
Then the Upgrader considers the system as up-to-date 0.319
# 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.369
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.454
After features/support/hooks.rb:330 0.694
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
42.688
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 11.406
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.722
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.073
But a current signing key is available on our website 0.000
When the network is plugged 0.116
And Tor is ready 22.857
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.447
After features/support/hooks.rb:330 1.007
After features/support/hooks.rb:100 0.000