Project Number Date
test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution 25 24 Apr 2025, 00:43

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 18:55.538 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.780
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.161
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 30.760
When I start Tails from USB drive "old" with network unplugged 1:23.908
Then the boot device has safe access rights 2.941
And Tails is running from USB drive "old" 0.305
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.088
And udev-watchdog is monitoring the correct device 0.279
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:330 6.786
After features/support/hooks.rb:100 0.008
Tags: @product
2:3.694
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login 1:21.971
Then Tails is running from USB drive "old" 0.344
And I create a persistent partition 30.883
And I take note of which tps features are available 1.394
Then a Tails persistence partition exists on USB drive "old" 0.692
And I shutdown Tails and wait for the computer to power off 8.236
After features/support/hooks.rb:330 0.165
After features/support/hooks.rb:100 0.007
Tags: @product
2:46.374
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.163
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.304
Then Tails is running from USB drive "old" 0.339
And all tps features are active 1.756
When I write some files expected to persist 1.719
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.215
And all persistence configuration files have safe access rights 0.401
And all persistent directories from the old Tails version have safe access rights 2.691
And I take note of which tps features are available 0.403
And I shutdown Tails and wait for the computer to power off 4.629
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.750
After features/support/hooks.rb:330 0.157
After features/support/hooks.rb:100 0.008
Tags: @product
2:32.275
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 9.869
And I log in to a new session 17.570
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.607
And I plug USB drive "to_upgrade" 2.417
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.708
Then the running Tails is installed on USB drive "to_upgrade" 24.687
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:330 1.064
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.071
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.171
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.078
Then all tps features from the old Tails version are active 1.570
And Tails is running from USB drive "to_upgrade" 0.330
And the boot device has safe access rights 3.194
And the expected persistent files created with the old Tails version are present in the filesystem 1.447
And all persistent directories from the old Tails version have safe access rights 2.278
After features/support/hooks.rb:330 1.488
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:35.112
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.726
And no SquashFS delta is installed 0.483
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.505
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.289
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.466
When the network is plugged 0.058
And Tor is ready 21.558
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.783
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.362
Given I shutdown Tails and wait for the computer to power off 8.466
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.363
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.106
And the file system changes introduced in version 6.2~testoverlayfs are present 0.396
And only the 6.2~testoverlayfs SquashFS delta is installed 0.090
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.347
# 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.312
When the network is plugged 0.073
And Tor is ready 16.742
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.888
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.697
Given I shutdown Tails and wait for the computer to power off 4.606
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.750
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.953
And the file system changes introduced in version 6.3~testoverlayfs are present 0.478
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.291
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.269
When the network is plugged 0.064
And Tor is ready 19.259
Then the Upgrader considers the system as up-to-date 0.306
# 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 14.755
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.504
After features/support/hooks.rb:330 0.689
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
40.230
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.476
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.437
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.128
And the signing key used by the Upgrader is outdated 0.117
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 22.283
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.717
After features/support/hooks.rb:330 0.659
After features/support/hooks.rb:100 0.000