Project Number Date
test_Tails_ISO_stable 5224 27 Oct 2024, 12:32

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 20:9.431 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.237
Before features/support/hooks.rb:269 0.005
Given a computer 0.186
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 30.645
When I start Tails from USB drive "old" with network unplugged 1:37.923
Then the boot device has safe access rights 3.343
And Tails is running from USB drive "old" 0.350
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.338
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:326 6.998
After features/support/hooks.rb:100 0.008
Tags: @product
2:10.104
Before features/support/hooks.rb:269 0.005
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login 1:25.997
Then Tails is running from USB drive "old" 0.344
And I create a persistent partition 32.992
And I take note of which tps features are available 1.481
Then a Tails persistence partition exists on USB drive "old" 0.741
And I shutdown Tails and wait for the computer to power off 8.359
After features/support/hooks.rb:326 0.152
After features/support/hooks.rb:100 0.009
Tags: @product
2:59.769
Before features/support/hooks.rb:269 0.005
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.769
Then Tails is running from USB drive "old" 0.475
And all tps features are active 2.128
When I write some files expected to persist 2.122
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.294
And all persistence configuration files have safe access rights 0.559
And all persistent directories from the old Tails version have safe access rights 2.678
And I take note of which tps features are available 0.466
And I shutdown Tails and wait for the computer to power off 4.396
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.674
After features/support/hooks.rb:326 0.113
After features/support/hooks.rb:100 0.009
Tags: @product
2:36.380
Before features/support/hooks.rb:269 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 12.676
And I log in to a new session 21.608
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.815
And I plug USB drive "to_upgrade" 2.821
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.756
Then the running Tails is installed on USB drive "to_upgrade" 20.023
And I unplug USB drive "to_upgrade" 0.199
And I unplug USB drive "__internal" 0.480
After features/support/hooks.rb:326 8.416
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.412
Before features/support/hooks.rb:269 0.006
Given a computer 0.200
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.921
Then all tps features from the old Tails version are active 1.774
And Tails is running from USB drive "to_upgrade" 0.329
And the boot device has safe access rights 3.188
And the expected persistent files created with the old Tails version are present in the filesystem 1.405
And all persistent directories from the old Tails version have safe access rights 2.592
After features/support/hooks.rb:326 0.974
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:8.310
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.346
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.393
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.500
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.593
When the network is plugged 0.077
And Tor is ready 52.592
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.590
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.990
Given I shutdown Tails and wait for the computer to power off 8.871
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.210
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.225
And the file system changes introduced in version 6.2~testoverlayfs are present 0.336
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.435
# 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.276
When the network is plugged 0.070
And Tor is ready 17.910
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.305
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.717
Given I shutdown Tails and wait for the computer to power off 6.739
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.495
Then Tails is running version 6.3~testoverlayfs 0.049
And all tps features are active 2.992
And the file system changes introduced in version 6.3~testoverlayfs are present 0.606
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.401
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.309
When the network is plugged 0.076
And Tor is ready 16.871
Then the Upgrader considers the system as up-to-date 0.335
# 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.522
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.117
After features/support/hooks.rb:326 0.767
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
42.216
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.627
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.049
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.919
But a current signing key is available on our website 0.000
When the network is plugged 0.087
And Tor is ready 20.113
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.356
After features/support/hooks.rb:326 0.684
After features/support/hooks.rb:100 0.000