Project Number Date
test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution 29 27 Apr 2025, 22:45

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:14.300 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:1.628
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.167
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 29.100
When I start Tails from USB drive "old" with network unplugged 1:27.287
Then the boot device has safe access rights 3.026
And Tails is running from USB drive "old" 0.292
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.301
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:330 7.177
After features/support/hooks.rb:100 0.016
Tags: @product
2:9.687
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login 1:24.483
Then Tails is running from USB drive "old" 0.326
And I create a persistent partition 33.976
And I take note of which tps features are available 1.622
Then a Tails persistence partition exists on USB drive "old" 0.747
And I shutdown Tails and wait for the computer to power off 8.333
After features/support/hooks.rb:330 0.146
After features/support/hooks.rb:100 0.008
Tags: @product
2:49.597
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.967
Then Tails is running from USB drive "old" 0.454
And all tps features are active 1.848
When I write some files expected to persist 1.928
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.270
And all persistence configuration files have safe access rights 0.369
And all persistent directories from the old Tails version have safe access rights 2.538
And I take note of which tps features are available 0.411
And I shutdown Tails and wait for the computer to power off 4.308
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.309
After features/support/hooks.rb:330 0.131
After features/support/hooks.rb:100 0.009
Tags: @product
2:26.260
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.481
And I log in to a new session 18.266
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.442
And I plug USB drive "to_upgrade" 2.494
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.789
Then the running Tails is installed on USB drive "to_upgrade" 19.334
And I unplug USB drive "to_upgrade" 0.234
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:330 1.240
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.891
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.252
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.314
Then all tps features from the old Tails version are active 1.721
And Tails is running from USB drive "to_upgrade" 0.331
And the boot device has safe access rights 3.508
And the expected persistent files created with the old Tails version are present in the filesystem 1.388
And all persistent directories from the old Tails version have safe access rights 2.374
After features/support/hooks.rb:330 1.117
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:50.752
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 11.673
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.276
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.276
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.542
When the network is plugged 0.084
And Tor is ready 50.335
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.570
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.335
Given I shutdown Tails and wait for the computer to power off 8.577
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.348
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.170
And the file system changes introduced in version 6.2~testoverlayfs are present 0.264
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.307
# 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.279
When the network is plugged 0.063
And Tor is ready 18.681
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.324
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.614
Given I shutdown Tails and wait for the computer to power off 4.191
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.338
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.476
And the file system changes introduced in version 6.3~testoverlayfs are present 0.504
And only the 6.3~testoverlayfs SquashFS delta is installed 0.089
# 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.308
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.325
When the network is plugged 0.071
And Tor is ready 16.374
Then the Upgrader considers the system as up-to-date 0.336
# 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.154
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.632
After features/support/hooks.rb:330 0.782
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
37.482
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 12.114
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.287
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.070
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 18.390
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.483
After features/support/hooks.rb:330 0.676
After features/support/hooks.rb:100 0.000