Project Number Date
test_Tails_ISO_devel 3305 01 Mar 2024, 12:10

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:24.012 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:36.854
Before features/support/hooks.rb:245 0.009
Given a computer 0.177
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 20.145
When I start Tails from USB drive "old" with network unplugged 1:11.336
Then the boot device has safe access rights 3.082
And Tails is running from USB drive "old" 0.313
And there is no persistence partition on USB drive "old" 0.111
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.293
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:291 6.762
After features/support/hooks.rb:75 0.012
Tags: @product
2:7.198
Before features/support/hooks.rb:245 0.008
Given a computer 0.523
And I start Tails from USB drive "old" with network unplugged and I login 1:15.004
Then Tails is running from USB drive "old" 0.320
And I create a persistent partition 40.799
And I take note of which tps features are available 1.774
Then a Tails persistence partition exists on USB drive "old" 0.748
And I shutdown Tails and wait for the computer to power off 8.027
After features/support/hooks.rb:291 0.184
After features/support/hooks.rb:75 0.011
Tags: @product
2:38.853
Before features/support/hooks.rb:245 0.008
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.558
Then Tails is running from USB drive "old" 0.370
And all tps features are active 1.667
When I write some files expected to persist 1.615
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.200
And all persistence configuration files have safe access rights 0.369
And all persistent directories from the old Tails version have safe access rights 2.372
And I take note of which tps features are available 0.319
And I shutdown Tails and wait for the computer to power off 4.019
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.184
After features/support/hooks.rb:291 0.156
After features/support/hooks.rb:75 0.010
Tags: @product
2:34.860
Before features/support/hooks.rb:245 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 12.605
And I log in to a new session 15.005
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.028
And I plug USB drive "to_upgrade" 2.380
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.508
Then the running Tails is installed on USB drive "to_upgrade" 14.927
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:291 2.227
After features/support/hooks.rb:75 0.000
Tags: @product
2:17.680
Before features/support/hooks.rb:245 0.007
Given a computer 0.523
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.073
Then all tps features from the old Tails version are active 1.311
And Tails is running from USB drive "to_upgrade" 0.310
And the boot device has safe access rights 2.890
And the expected persistent files created with the old Tails version are present in the filesystem 1.346
And all persistent directories from the old Tails version have safe access rights 2.223
After features/support/hooks.rb:291 0.639
After features/support/hooks.rb:75 0.011
Tags: @product @automatic_upgrade
6:36.167
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.608
And no SquashFS delta is installed 0.185
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.294
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.290
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.460
When the network is plugged 0.027
And Tor is ready 18.248
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.091
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.178
Given I shutdown Tails and wait for the computer to power off 6.021
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.480
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.798
And the file system changes introduced in version 6.2~testoverlayfs are present 0.314
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.305
# 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.242
When the network is plugged 0.035
And Tor is ready 18.170
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.240
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.344
Given I shutdown Tails and wait for the computer to power off 4.048
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.783
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 1.610
And the file system changes introduced in version 6.3~testoverlayfs are present 0.428
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.293
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.266
When the network is plugged 0.027
And Tor is ready 16.082
Then the Upgrader considers the system as up-to-date 10.681
# 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.480
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.875
After features/support/hooks.rb:291 0.727
After features/support/hooks.rb:75 0.021
Tags: @product @automatic_upgrade
32.397
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.126
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.439
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 1.098
But a current signing key is available on our website 0.000
When the network is plugged 0.065
And Tor is ready 15.286
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.326
After features/support/hooks.rb:291 1.042
After features/support/hooks.rb:75 0.000