Project Number Date
test_Tails_ISO_devel 3421 08 Jun 2024, 12:26

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:11.173 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:56.558
Before features/support/hooks.rb:269 0.005
Given a computer 0.227
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 29.889
When I start Tails from USB drive "old" with network unplugged 1:21.405
Then the boot device has safe access rights 2.937
And Tails is running from USB drive "old" 0.314
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.084
And udev-watchdog is monitoring the correct device 0.304
And I unplug USB drive "old" 0.244
After features/support/hooks.rb:315 3.513
After features/support/hooks.rb:100 0.011
Tags: @product
2:6.871
Before features/support/hooks.rb:269 0.008
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login 1:19.919
Then Tails is running from USB drive "old" 0.329
And I create a persistent partition 35.914
And I take note of which tps features are available 1.394
Then a Tails persistence partition exists on USB drive "old" 0.830
And I shutdown Tails and wait for the computer to power off 8.276
After features/support/hooks.rb:315 0.161
After features/support/hooks.rb:100 0.010
Tags: @product
2:49.926
Before features/support/hooks.rb:269 0.007
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.058
Then Tails is running from USB drive "old" 0.349
And all tps features are active 1.892
When I write some files expected to persist 1.761
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.298
And all persistence configuration files have safe access rights 0.472
And all persistent directories from the old Tails version have safe access rights 2.490
And I take note of which tps features are available 0.506
And I shutdown Tails and wait for the computer to power off 4.429
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.458
After features/support/hooks.rb:315 0.129
After features/support/hooks.rb:100 0.012
Tags: @product
2:22.744
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.859
And I log in to a new session 17.905
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.652
And I plug USB drive "to_upgrade" 2.462
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.443
Then the running Tails is installed on USB drive "to_upgrade" 16.035
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.183
After features/support/hooks.rb:315 2.300
After features/support/hooks.rb:100 0.000
Tags: @product
2:8.281
Before features/support/hooks.rb:269 0.008
Given a computer 0.202
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.528
Then all tps features from the old Tails version are active 1.680
And Tails is running from USB drive "to_upgrade" 0.360
And the boot device has safe access rights 2.906
And the expected persistent files created with the old Tails version are present in the filesystem 1.441
And all persistent directories from the old Tails version have safe access rights 2.160
After features/support/hooks.rb:315 1.100
After features/support/hooks.rb:100 0.086
Tags: @product @automatic_upgrade
7:12.338
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.047
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.362
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.304
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.464
When the network is plugged 0.030
And Tor is ready 20.998
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.889
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.386
Given I shutdown Tails and wait for the computer to power off 8.499
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.962
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.169
And the file system changes introduced in version 6.2~testoverlayfs are present 0.293
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.393
# 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.284
When the network is plugged 0.033
And Tor is ready 17.041
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.399
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.455
Given I shutdown Tails and wait for the computer to power off 56.757
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.984
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.799
And the file system changes introduced in version 6.3~testoverlayfs are present 0.488
And only the 6.3~testoverlayfs SquashFS delta is installed 0.097
# 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.311
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.232
When the network is plugged 0.043
And Tor is ready 17.192
Then the Upgrader considers the system as up-to-date 10.698
# 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 13.972
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.490
After features/support/hooks.rb:315 0.639
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
34.452
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.531
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.315
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.096
And the signing key used by the Upgrader is outdated 1.503
But a current signing key is available on our website 0.000
When the network is plugged 0.040
And Tor is ready 15.477
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.486
After features/support/hooks.rb:315 0.977
After features/support/hooks.rb:100 0.000