Project Number Date
test_Tails_ISO_stable 4650 01 Feb 2024, 18:42

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 17:2.892 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
1:25.405
Before features/support/hooks.rb:245 0.005
Given a computer 0.166
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 19.158
When I start Tails from USB drive "old" with network unplugged 1:0.529
Then the boot device has safe access rights 3.450
And Tails is running from USB drive "old" 0.347
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.070
And udev-watchdog is monitoring the correct device 0.305
And I unplug USB drive "old" 0.221
After features/support/hooks.rb:291 3.553
After features/support/hooks.rb:75 0.039
Tags: @product
2:4.496
Before features/support/hooks.rb:245 0.007
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login 1:9.182
Then Tails is running from USB drive "old" 0.461
And I create a persistent partition 43.904
And I take note of which tps features are available 1.784
Then a Tails persistence partition exists on USB drive "old" 0.857
And I shutdown Tails and wait for the computer to power off 8.090
After features/support/hooks.rb:291 0.149
After features/support/hooks.rb:75 0.013
Tags: @product
2:21.424
Before features/support/hooks.rb:245 0.009
Given a computer 0.228
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:52.720
Then Tails is running from USB drive "old" 0.402
And all tps features are active 2.223
When I write some files expected to persist 2.282
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.345
And all persistence configuration files have safe access rights 0.473
And all persistent directories from the old Tails version have safe access rights 3.075
And I take note of which tps features are available 0.414
And I shutdown Tails and wait for the computer to power off 3.054
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.202
After features/support/hooks.rb:291 0.120
After features/support/hooks.rb:75 0.009
Tags: @product
2:38.018
Before features/support/hooks.rb:245 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 9.722
And I log in to a new session 21.960
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.392
And I plug USB drive "to_upgrade" 2.482
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.655
Then the running Tails is installed on USB drive "to_upgrade" 13.390
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.193
After features/support/hooks.rb:291 6.826
After features/support/hooks.rb:75 0.000
Tags: @product
2:1.806
Before features/support/hooks.rb:245 0.006
Given a computer 0.171
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:51.490
Then all tps features from the old Tails version are active 1.946
And Tails is running from USB drive "to_upgrade" 0.396
And the boot device has safe access rights 3.308
And the expected persistent files created with the old Tails version are present in the filesystem 1.519
And all persistent directories from the old Tails version have safe access rights 2.972
After features/support/hooks.rb:291 0.877
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
6:2.961
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.186
And no SquashFS delta is installed 0.429
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.379
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.068
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.473
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.691
When the network is plugged 0.060
And Tor is ready 18.090
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.676
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 10.985
Given I shutdown Tails and wait for the computer to power off 6.360
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.966
Then Tails is running version 2.2~testoverlayfsng 0.113
And all tps features are active 1.956
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.415
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.109
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.297
# We'll really install Tails_amd64_2.0~testoverlayfsng_to_2.3~testoverlayfsng.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 2.1~testoverlayfsng was initially installed 0.380
When the network is plugged 0.064
And Tor is ready 15.223
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.931
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.141
Given I shutdown Tails and wait for the computer to power off 4.100
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.744
Then Tails is running version 2.3~testoverlayfsng 0.108
And all tps features are active 2.065
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.553
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.089
# 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.312
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.306
When the network is plugged 0.057
And Tor is ready 15.672
Then the Upgrader considers the system as up-to-date 0.318
# 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 26.670
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.958
After features/support/hooks.rb:291 0.811
After features/support/hooks.rb:75 0.018
Tags: @product @automatic_upgrade
28.780
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.379
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.417
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.080
And the signing key used by the Upgrader is outdated 0.820
But a current signing key is available on our website 0.000
When the network is plugged 0.067
And Tor is ready 14.995
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.018
After features/support/hooks.rb:291 0.938
After features/support/hooks.rb:75 0.000