Project Number Date
test_Tails_ISO_stable 5273 16 Nov 2024, 22:18

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 20:15.532 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:19.808
Before features/support/hooks.rb:269 0.005
Given a computer 0.195
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 40.212
When I start Tails from USB drive "old" with network unplugged 1:34.092
Then the boot device has safe access rights 3.150
And Tails is running from USB drive "old" 0.343
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.324
And I unplug USB drive "old" 0.215
After features/support/hooks.rb:326 7.189
After features/support/hooks.rb:100 0.014
Tags: @product
2:16.033
Before features/support/hooks.rb:269 0.007
Given a computer 0.312
And I start Tails from USB drive "old" with network unplugged and I login 1:27.828
Then Tails is running from USB drive "old" 0.395
And I create a persistent partition 36.144
And I take note of which tps features are available 2.143
Then a Tails persistence partition exists on USB drive "old" 0.895
And I shutdown Tails and wait for the computer to power off 8.314
After features/support/hooks.rb:326 0.121
After features/support/hooks.rb:100 0.008
Tags: @product
2:54.586
Before features/support/hooks.rb:269 0.006
Given a computer 0.240
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.180
Then Tails is running from USB drive "old" 0.501
And all tps features are active 2.249
When I write some files expected to persist 1.881
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.290
And all persistence configuration files have safe access rights 0.470
And all persistent directories from the old Tails version have safe access rights 2.459
And I take note of which tps features are available 0.660
And I shutdown Tails and wait for the computer to power off 4.516
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.134
After features/support/hooks.rb:326 0.149
After features/support/hooks.rb:100 0.007
Tags: @product
2:50.426
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 28.010
And I log in to a new session 19.504
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.736
And I plug USB drive "to_upgrade" 2.498
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.740
Then the running Tails is installed on USB drive "to_upgrade" 19.468
And I unplug USB drive "to_upgrade" 0.250
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:326 3.734
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.949
Before features/support/hooks.rb:269 0.006
Given a computer 0.193
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.174
Then all tps features from the old Tails version are active 1.783
And Tails is running from USB drive "to_upgrade" 0.388
And the boot device has safe access rights 3.500
And the expected persistent files created with the old Tails version are present in the filesystem 1.838
And all persistent directories from the old Tails version have safe access rights 3.071
After features/support/hooks.rb:326 0.953
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:57.306
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.676
And no SquashFS delta is installed 0.106
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.446
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.082
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.306
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.918
When the network is plugged 0.092
And Tor is ready 23.372
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.389
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.272
Given I shutdown Tails and wait for the computer to power off 10.780
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.240
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.556
And the file system changes introduced in version 6.2~testoverlayfs are present 0.390
And only the 6.2~testoverlayfs SquashFS delta is installed 0.098
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.372
# 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.299
When the network is plugged 0.087
And Tor is ready 21.162
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.691
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.556
Given I shutdown Tails and wait for the computer to power off 4.447
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.626
Then Tails is running version 6.3~testoverlayfs 0.022
And all tps features are active 2.307
And the file system changes introduced in version 6.3~testoverlayfs are present 0.569
And only the 6.3~testoverlayfs SquashFS delta is installed 0.094
# 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.396
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.314
When the network is plugged 0.101
And Tor is ready 21.757
Then the Upgrader considers the system as up-to-date 0.364
# 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 16.283
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.103
After features/support/hooks.rb:326 0.839
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
37.421
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.439
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.798
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the signing key used by the Upgrader is outdated 0.784
But a current signing key is available on our website 0.000
When the network is plugged 0.114
And Tor is ready 17.964
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.247
After features/support/hooks.rb:326 1.355
After features/support/hooks.rb:100 0.000