Project Number Date
test_Tails_ISO_devel 3447 05 Jul 2024, 12:08

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 17:56.162 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:13.100
Before features/support/hooks.rb:269 0.008
Given a computer 0.227
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 28.138
When I start Tails from USB drive "old" with network unplugged 1:40.022
Then the boot device has safe access rights 2.723
And Tails is running from USB drive "old" 0.283
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.084
And udev-watchdog is monitoring the correct device 0.293
And I unplug USB drive "old" 0.172
After features/support/hooks.rb:326 3.727
After features/support/hooks.rb:100 0.011
Tags: @product
2:1.096
Before features/support/hooks.rb:269 0.007
Given a computer 0.283
And I start Tails from USB drive "old" with network unplugged and I login 1:17.912
Then Tails is running from USB drive "old" 0.346
And I create a persistent partition 31.756
And I take note of which tps features are available 1.385
Then a Tails persistence partition exists on USB drive "old" 0.780
And I shutdown Tails and wait for the computer to power off 8.630
After features/support/hooks.rb:326 0.147
After features/support/hooks.rb:100 0.011
Tags: @product
2:42.153
Before features/support/hooks.rb:269 0.007
Given a computer 0.221
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:6.310
Then Tails is running from USB drive "old" 0.278
And all tps features are active 1.827
When I write some files expected to persist 1.674
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.193
And all persistence configuration files have safe access rights 0.370
And all persistent directories from the old Tails version have safe access rights 2.306
And I take note of which tps features are available 0.443
And I shutdown Tails and wait for the computer to power off 4.763
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.762
After features/support/hooks.rb:326 0.096
After features/support/hooks.rb:100 0.011
Tags: @product
2:20.284
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.396
And I log in to a new session 17.876
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.296
And I plug USB drive "to_upgrade" 2.330
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.993
Then the running Tails is installed on USB drive "to_upgrade" 15.989
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.200
After features/support/hooks.rb:326 3.496
After features/support/hooks.rb:100 0.000
Tags: @product
2:3.337
Before features/support/hooks.rb:269 0.008
Given a computer 0.221
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:53.944
Then all tps features from the old Tails version are active 1.548
And Tails is running from USB drive "to_upgrade" 0.318
And the boot device has safe access rights 2.979
And the expected persistent files created with the old Tails version are present in the filesystem 1.614
And all persistent directories from the old Tails version have safe access rights 2.709
After features/support/hooks.rb:326 0.773
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:1.428
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.066
And no SquashFS delta is installed 0.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.330
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.080
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.314
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.494
When the network is plugged 0.036
And Tor is ready 18.247
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.406
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.400
Given I shutdown Tails and wait for the computer to power off 8.520
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.297
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 1.998
And the file system changes introduced in version 6.2~testoverlayfs are present 0.275
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.314
# 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.243
When the network is plugged 0.040
And Tor is ready 16.980
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.978
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.234
Given I shutdown Tails and wait for the computer to power off 4.297
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.932
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.002
And the file system changes introduced in version 6.3~testoverlayfs are present 0.491
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.342
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.230
When the network is plugged 0.064
And Tor is ready 18.965
Then the Upgrader considers the system as up-to-date 0.320
# 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.427
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.850
After features/support/hooks.rb:326 0.701
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
34.761
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.772
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.314
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.747
But a current signing key is available on our website 0.000
When the network is plugged 0.044
And Tor is ready 17.627
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.195
After features/support/hooks.rb:326 0.643
After features/support/hooks.rb:100 0.000