Project Number Date
test_Tails_ISO_devel 3371 02 May 2024, 13:52

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:6.352 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:30.872
Before features/support/hooks.rb:259 0.006
Given a computer 0.388
And I create a 7200 MiB disk named "old" 0.127
And I plug USB drive "old" 1.086
And I write an old version of the Tails USB image to disk "old" 56.322
When I start Tails from USB drive "old" with network unplugged 1:28.528
Then the boot device has safe access rights 3.270
And Tails is running from USB drive "old" 0.352
And there is no persistence partition on USB drive "old" 0.106
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.338
And I unplug USB drive "old" 0.243
After features/support/hooks.rb:305 3.534
After features/support/hooks.rb:89 0.013
Tags: @product
2:21.958
Before features/support/hooks.rb:259 0.009
Given a computer 0.236
And I start Tails from USB drive "old" with network unplugged and I login 1:32.847
Then Tails is running from USB drive "old" 0.378
And I create a persistent partition 36.722
And I take note of which tps features are available 1.753
Then a Tails persistence partition exists on USB drive "old" 0.955
And I shutdown Tails and wait for the computer to power off 9.064
After features/support/hooks.rb:305 0.185
After features/support/hooks.rb:89 0.015
Tags: @product
3:10.065
Before features/support/hooks.rb:259 0.010
Given a computer 0.276
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:27.489
Then Tails is running from USB drive "old" 0.384
And all tps features are active 2.329
When I write some files expected to persist 2.339
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.311
And all persistence configuration files have safe access rights 0.486
And all persistent directories from the old Tails version have safe access rights 2.436
And I take note of which tps features are available 1.609
And I shutdown Tails and wait for the computer to power off 6.557
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.844
After features/support/hooks.rb:305 0.151
After features/support/hooks.rb:89 0.011
Tags: @product
3:11.149
Before features/support/hooks.rb:259 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 44.450
And I log in to a new session 17.118
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.796
And I plug USB drive "to_upgrade" 2.556
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:46.422
Then the running Tails is installed on USB drive "to_upgrade" 18.251
And I unplug USB drive "to_upgrade" 0.266
And I unplug USB drive "__internal" 0.287
After features/support/hooks.rb:305 2.413
After features/support/hooks.rb:89 0.000
Tags: @product
2:16.242
Before features/support/hooks.rb:259 0.008
Given a computer 0.179
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.287
Then all tps features from the old Tails version are active 1.659
And Tails is running from USB drive "to_upgrade" 0.307
And the boot device has safe access rights 3.333
And the expected persistent files created with the old Tails version are present in the filesystem 1.889
And all persistent directories from the old Tails version have safe access rights 2.584
After features/support/hooks.rb:305 0.752
After features/support/hooks.rb:89 0.013
Tags: @product @automatic_upgrade
6:47.733
Before features/support/hooks.rb:259 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.605
And no SquashFS delta is installed 0.241
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.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.297
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.443
When the network is plugged 0.030
And Tor is ready 19.603
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.804
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.140
Given I shutdown Tails and wait for the computer to power off 9.378
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.894
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.092
And the file system changes introduced in version 6.2~testoverlayfs are present 0.266
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.428
# 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.278
When the network is plugged 0.038
And Tor is ready 19.803
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.710
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.786
Given I shutdown Tails and wait for the computer to power off 4.571
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.847
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 2.852
And the file system changes introduced in version 6.3~testoverlayfs are present 0.672
And only the 6.3~testoverlayfs SquashFS delta is installed 0.096
# 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.392
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.348
When the network is plugged 0.044
And Tor is ready 19.405
Then the Upgrader considers the system as up-to-date 0.421
# 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.471
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.235
After features/support/hooks.rb:305 0.930
After features/support/hooks.rb:89 0.028
Tags: @product @automatic_upgrade
48.330
Before features/support/hooks.rb:259 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 18.107
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.411
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.554
But a current signing key is available on our website 0.000
When the network is plugged 0.048
And Tor is ready 21.048
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.099
After features/support/hooks.rb:305 0.821
After features/support/hooks.rb:89 0.000