Project Number Date
test_Tails_ISO_stable 4886 12 Jun 2024, 18:48

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:51.867 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.023
Before features/support/hooks.rb:269 0.008
Given a computer 0.314
And I create a 7200 MiB disk named "old" 0.114
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 39.800
When I start Tails from USB drive "old" with network unplugged 1:28.242
Then the boot device has safe access rights 3.399
And Tails is running from USB drive "old" 0.410
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.335
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:320 3.646
After features/support/hooks.rb:100 0.022
Tags: @product
2:27.745
Before features/support/hooks.rb:269 0.005
Given a computer 0.252
And I start Tails from USB drive "old" with network unplugged and I login 1:28.928
Then Tails is running from USB drive "old" 0.378
And I create a persistent partition 46.051
And I take note of which tps features are available 2.153
Then a Tails persistence partition exists on USB drive "old" 1.235
And I shutdown Tails and wait for the computer to power off 8.745
After features/support/hooks.rb:320 0.170
After features/support/hooks.rb:100 0.012
Tags: @product
3:8.843
Before features/support/hooks.rb:269 0.011
Given a computer 0.243
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:28.760
Then Tails is running from USB drive "old" 0.524
And all tps features are active 3.765
When I write some files expected to persist 2.166
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.234
And all persistence configuration files have safe access rights 0.417
And all persistent directories from the old Tails version have safe access rights 2.691
And I take note of which tps features are available 0.473
And I shutdown Tails and wait for the computer to power off 4.479
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.086
After features/support/hooks.rb:320 0.149
After features/support/hooks.rb:100 0.010
Tags: @product
2:30.546
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 11.509
And I log in to a new session 20.392
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.602
And I plug USB drive "to_upgrade" 2.456
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.500
Then the running Tails is installed on USB drive "to_upgrade" 19.687
And I unplug USB drive "to_upgrade" 0.184
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:320 2.175
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.625
Before features/support/hooks.rb:269 0.006
Given a computer 0.217
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.998
Then all tps features from the old Tails version are active 1.671
And Tails is running from USB drive "to_upgrade" 0.313
And the boot device has safe access rights 3.152
And the expected persistent files created with the old Tails version are present in the filesystem 1.790
And all persistent directories from the old Tails version have safe access rights 2.481
After features/support/hooks.rb:320 0.750
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:38.884
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 10.999
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.371
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.262
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.451
When the network is plugged 0.053
And Tor is ready 18.902
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.626
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.913
Given I shutdown Tails and wait for the computer to power off 17.875
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.551
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.086
And the file system changes introduced in version 6.2~testoverlayfs are present 0.279
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.321
# 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.247
When the network is plugged 0.052
And Tor is ready 21.640
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.729
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.180
Given I shutdown Tails and wait for the computer to power off 4.432
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.019
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.186
And the file system changes introduced in version 6.3~testoverlayfs are present 0.473
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.302
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.265
When the network is plugged 0.038
And Tor is ready 17.117
Then the Upgrader considers the system as up-to-date 0.384
# 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.878
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.952
After features/support/hooks.rb:320 0.847
After features/support/hooks.rb:100 0.047
Tags: @product @automatic_upgrade
34.198
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 9.728
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.388
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 1.035
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 15.149
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.806
After features/support/hooks.rb:320 1.117
After features/support/hooks.rb:100 0.000