Project Number Date
test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution 6 10 Apr 2025, 21:03

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:41.853 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:17.186
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.251
And I create a 7200 MiB disk named "old" 0.115
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 31.544
When I start Tails from USB drive "old" with network unplugged 1:39.998
Then the boot device has safe access rights 3.147
And Tails is running from USB drive "old" 0.349
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.330
And I unplug USB drive "old" 0.209
After features/support/hooks.rb:330 3.732
After features/support/hooks.rb:100 0.009
Tags: @product
2:18.573
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.247
And I start Tails from USB drive "old" with network unplugged and I login 1:34.087
Then Tails is running from USB drive "old" 0.303
And I create a persistent partition 32.287
And I take note of which tps features are available 2.400
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.499
After features/support/hooks.rb:330 0.168
After features/support/hooks.rb:100 0.008
Tags: @product
2:57.712
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.783
Then Tails is running from USB drive "old" 0.385
And all tps features are active 2.020
When I write some files expected to persist 1.983
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.210
And all persistence configuration files have safe access rights 0.386
And all persistent directories from the old Tails version have safe access rights 2.662
And I take note of which tps features are available 0.448
And I shutdown Tails and wait for the computer to power off 4.501
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.147
After features/support/hooks.rb:330 0.155
After features/support/hooks.rb:100 0.007
Tags: @product
2:30.908
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.038
And I log in to a new session 19.528
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.746
And I plug USB drive "to_upgrade" 2.569
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.392
Then the running Tails is installed on USB drive "to_upgrade" 23.020
And I unplug USB drive "to_upgrade" 0.277
And I unplug USB drive "__internal" 0.333
After features/support/hooks.rb:330 2.333
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.193
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.177
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.711
Then all tps features from the old Tails version are active 1.649
And Tails is running from USB drive "to_upgrade" 0.358
And the boot device has safe access rights 3.438
And the expected persistent files created with the old Tails version are present in the filesystem 2.042
And all persistent directories from the old Tails version have safe access rights 2.815
After features/support/hooks.rb:330 1.485
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
6:36.947
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.862
And no SquashFS delta is installed 0.112
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.471
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.330
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.438
When the network is plugged 0.103
And Tor is ready 24.159
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.951
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.216
Given I shutdown Tails and wait for the computer to power off 8.733
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.122
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 2.219
And the file system changes introduced in version 6.2~testoverlayfs are present 0.319
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.299
# 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.348
When the network is plugged 0.067
And Tor is ready 18.774
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.866
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.634
Given I shutdown Tails and wait for the computer to power off 4.281
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.284
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.046
And the file system changes introduced in version 6.3~testoverlayfs are present 0.514
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.335
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.280
When the network is plugged 0.080
And Tor is ready 17.335
Then the Upgrader considers the system as up-to-date 0.307
# 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.668
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.529
After features/support/hooks.rb:330 0.769
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
40.332
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 10.028
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.369
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.101
And the signing key used by the Upgrader is outdated 0.097
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 23.022
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.644
After features/support/hooks.rb:330 0.917
After features/support/hooks.rb:100 0.000