Project Number Date
test_Tails_ISO_stable 5164 09 Oct 2024, 19:36

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 21:57.671 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
3:16.156
Before features/support/hooks.rb:269 0.005
Given a computer 0.263
And I create a 7200 MiB disk named "old" 0.066
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 1:1.181
When I start Tails from USB drive "old" with network unplugged 2:9.261
Then the boot device has safe access rights 3.305
And Tails is running from USB drive "old" 0.353
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.283
And I unplug USB drive "old" 0.207
After features/support/hooks.rb:326 0.865
After features/support/hooks.rb:100 0.011
Tags: @product
2:20.238
Before features/support/hooks.rb:269 0.005
Given a computer 0.261
And I start Tails from USB drive "old" with network unplugged and I login 1:35.108
Then Tails is running from USB drive "old" 0.395
And I create a persistent partition 32.596
And I take note of which tps features are available 2.450
Then a Tails persistence partition exists on USB drive "old" 0.771
And I shutdown Tails and wait for the computer to power off 8.655
After features/support/hooks.rb:326 0.216
After features/support/hooks.rb:100 0.008
Tags: @product
3:22.453
Before features/support/hooks.rb:269 0.004
Given a computer 0.240
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:43.441
Then Tails is running from USB drive "old" 0.917
And all tps features are active 2.702
When I write some files expected to persist 2.030
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.295
And all persistence configuration files have safe access rights 0.477
And all persistent directories from the old Tails version have safe access rights 2.790
And I take note of which tps features are available 0.594
And I shutdown Tails and wait for the computer to power off 4.167
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.795
After features/support/hooks.rb:326 0.157
After features/support/hooks.rb:100 0.011
Tags: @product
2:41.377
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.022
And I log in to a new session 20.502
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.795
And I plug USB drive "to_upgrade" 2.413
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.186
Then the running Tails is installed on USB drive "to_upgrade" 25.960
And I unplug USB drive "to_upgrade" 0.232
And I unplug USB drive "__internal" 0.264
After features/support/hooks.rb:326 2.987
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.441
Before features/support/hooks.rb:269 0.006
Given a computer 0.212
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.265
Then all tps features from the old Tails version are active 2.429
And Tails is running from USB drive "to_upgrade" 0.375
And the boot device has safe access rights 4.236
And the expected persistent files created with the old Tails version are present in the filesystem 1.771
And all persistent directories from the old Tails version have safe access rights 3.151
After features/support/hooks.rb:326 1.277
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
7:13.887
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 15.683
And no SquashFS delta is installed 0.135
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.348
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.445
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.863
When the network is plugged 0.095
And Tor is ready 21.416
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.500
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.715
Given I shutdown Tails and wait for the computer to power off 13.626
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:23.024
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.518
And the file system changes introduced in version 6.2~testoverlayfs are present 0.365
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.329
# 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.352
When the network is plugged 0.102
And Tor is ready 20.482
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.432
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.353
Given I shutdown Tails and wait for the computer to power off 4.569
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.047
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.374
And the file system changes introduced in version 6.3~testoverlayfs are present 0.801
And only the 6.3~testoverlayfs SquashFS delta is installed 0.104
# 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.365
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.313
When the network is plugged 0.079
And Tor is ready 21.815
Then the Upgrader considers the system as up-to-date 0.339
# 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.868
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.227
After features/support/hooks.rb:326 0.832
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
38.116
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 11.268
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.470
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.156
And the signing key used by the Upgrader is outdated 1.153
But a current signing key is available on our website 0.000
When the network is plugged 0.089
And Tor is ready 18.116
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.861
After features/support/hooks.rb:326 0.857
After features/support/hooks.rb:100 0.000