Project Number Date
test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution 21 19 Apr 2025, 22:31

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:21.280 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:14.594
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.191
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 30.197
When I start Tails from USB drive "old" with network unplugged 1:39.042
Then the boot device has safe access rights 2.962
And Tails is running from USB drive "old" 0.341
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.109
And udev-watchdog is monitoring the correct device 0.349
And I unplug USB drive "old" 0.240
After features/support/hooks.rb:330 6.899
After features/support/hooks.rb:100 0.009
Tags: @product
2:8.592
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login 1:25.224
Then Tails is running from USB drive "old" 0.309
And I create a persistent partition 31.518
And I take note of which tps features are available 1.830
Then a Tails persistence partition exists on USB drive "old" 0.928
And I shutdown Tails and wait for the computer to power off 8.571
After features/support/hooks.rb:330 0.161
After features/support/hooks.rb:100 0.008
Tags: @product
2:52.067
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.411
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.888
Then Tails is running from USB drive "old" 0.403
And all tps features are active 2.848
When I write some files expected to persist 2.044
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.251
And all persistence configuration files have safe access rights 0.460
And all persistent directories from the old Tails version have safe access rights 2.744
And I take note of which tps features are available 0.517
And I shutdown Tails and wait for the computer to power off 4.421
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.075
After features/support/hooks.rb:330 0.147
After features/support/hooks.rb:100 0.009
Tags: @product
2:34.264
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.083
And I log in to a new session 19.810
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.468
And I plug USB drive "to_upgrade" 2.386
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.807
Then the running Tails is installed on USB drive "to_upgrade" 25.112
And I unplug USB drive "to_upgrade" 0.281
And I unplug USB drive "__internal" 0.312
After features/support/hooks.rb:330 1.039
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.068
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.250
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.835
Then all tps features from the old Tails version are active 1.661
And Tails is running from USB drive "to_upgrade" 0.323
And the boot device has safe access rights 3.303
And the expected persistent files created with the old Tails version are present in the filesystem 1.406
And all persistent directories from the old Tails version have safe access rights 2.286
After features/support/hooks.rb:330 1.553
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:40.778
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 12.514
And no SquashFS delta is installed 0.178
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.858
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.298
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.446
When the network is plugged 0.071
And Tor is ready 23.427
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.377
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.614
Given I shutdown Tails and wait for the computer to power off 11.056
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.679
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.277
And the file system changes introduced in version 6.2~testoverlayfs are present 0.303
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.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.299
When the network is plugged 0.095
And Tor is ready 19.244
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.160
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.798
Given I shutdown Tails and wait for the computer to power off 4.366
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.665
Then Tails is running version 6.3~testoverlayfs 0.030
And all tps features are active 2.016
And the file system changes introduced in version 6.3~testoverlayfs are present 0.556
And only the 6.3~testoverlayfs SquashFS delta is installed 0.127
# 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.377
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.250
When the network is plugged 0.062
And Tor is ready 20.719
Then the Upgrader considers the system as up-to-date 0.363
# 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.448
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.645
After features/support/hooks.rb:330 0.816
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
38.914
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 10.664
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.246
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.076
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 20.108
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.681
After features/support/hooks.rb:330 0.633
After features/support/hooks.rb:100 0.000