Project Number Date
test_Tails_ISO_stable 4829 06 May 2024, 15:08

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:46.196 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:6.260
Before features/support/hooks.rb:259 0.005
Given a computer 0.182
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 30.662
When I start Tails from USB drive "old" with network unplugged 1:30.501
Then the boot device has safe access rights 2.833
And Tails is running from USB drive "old" 0.304
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.086
And udev-watchdog is monitoring the correct device 0.343
And I unplug USB drive "old" 0.184
After features/support/hooks.rb:305 3.761
After features/support/hooks.rb:89 0.008
Tags: @product
2:14.225
Before features/support/hooks.rb:259 0.004
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login 1:25.384
Then Tails is running from USB drive "old" 0.351
And I create a persistent partition 37.175
And I take note of which tps features are available 1.550
Then a Tails persistence partition exists on USB drive "old" 0.849
And I shutdown Tails and wait for the computer to power off 8.733
After features/support/hooks.rb:305 0.244
After features/support/hooks.rb:89 0.010
Tags: @product
2:49.053
Before features/support/hooks.rb:259 0.005
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.601
Then Tails is running from USB drive "old" 0.560
And all tps features are active 2.115
When I write some files expected to persist 1.834
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.218
And all persistence configuration files have safe access rights 0.442
And all persistent directories from the old Tails version have safe access rights 2.860
And I take note of which tps features are available 0.474
And I shutdown Tails and wait for the computer to power off 4.350
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.388
After features/support/hooks.rb:305 0.140
After features/support/hooks.rb:89 0.009
Tags: @product
2:23.202
Before features/support/hooks.rb:259 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 10.923
And I log in to a new session 17.021
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.563
And I plug USB drive "to_upgrade" 2.442
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.392
Then the running Tails is installed on USB drive "to_upgrade" 16.486
And I unplug USB drive "to_upgrade" 0.188
And I unplug USB drive "__internal" 0.184
After features/support/hooks.rb:305 3.585
After features/support/hooks.rb:89 0.000
Tags: @product
2:12.739
Before features/support/hooks.rb:259 0.004
Given a computer 0.203
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.428
Then all tps features from the old Tails version are active 1.715
And Tails is running from USB drive "to_upgrade" 0.315
And the boot device has safe access rights 3.192
And the expected persistent files created with the old Tails version are present in the filesystem 1.501
And all persistent directories from the old Tails version have safe access rights 2.382
After features/support/hooks.rb:305 0.823
After features/support/hooks.rb:89 0.008
Tags: @product @automatic_upgrade
6:24.976
Before features/support/hooks.rb:259 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.656
And no SquashFS delta is installed 0.119
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.309
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
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.499
When the network is plugged 0.103
And Tor is ready 19.410
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.272
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.125
Given I shutdown Tails and wait for the computer to power off 11.310
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.369
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.155
And the file system changes introduced in version 6.2~testoverlayfs are present 0.315
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.327
# 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.306
When the network is plugged 0.047
And Tor is ready 19.297
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.337
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.260
Given I shutdown Tails and wait for the computer to power off 4.422
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.751
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.070
And the file system changes introduced in version 6.3~testoverlayfs are present 0.513
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.308
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.249
When the network is plugged 0.056
And Tor is ready 19.069
Then the Upgrader considers the system as up-to-date 0.340
# 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 15.526
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.926
After features/support/hooks.rb:305 0.805
After features/support/hooks.rb:89 0.018
Tags: @product @automatic_upgrade
35.738
Before features/support/hooks.rb:259 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.671
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.383
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the signing key used by the Upgrader is outdated 0.765
But a current signing key is available on our website 0.000
When the network is plugged 0.044
And Tor is ready 15.323
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.479
After features/support/hooks.rb:305 0.641
After features/support/hooks.rb:89 0.000