Project Number Date
test_Tails_ISO_devel 3189 11 Dec 2023, 12:20

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 16:18.143 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:23.312
Before features/support/hooks.rb:245 0.005
Given a computer 0.209
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.079
And I write an old version of the Tails USB image to disk "old" 19.182
When I start Tails from USB drive "old" with network unplugged 58.922
Then the boot device has safe access rights 3.002
And Tails is running from USB drive "old" 0.287
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.261
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:291 3.457
After features/support/hooks.rb:75 0.055
Tags: @product
1:56.626
Before features/support/hooks.rb:245 0.006
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login 1:3.055
Then Tails is running from USB drive "old" 0.556
And I create a persistent partition 43.365
And I take note of which tps features are available 1.369
Then a Tails persistence partition exists on USB drive "old" 0.930
And I shutdown Tails and wait for the computer to power off 7.171
After features/support/hooks.rb:291 0.112
After features/support/hooks.rb:75 0.011
Tags: @product
2:12.591
Before features/support/hooks.rb:245 0.007
Given a computer 0.240
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:45.341
Then Tails is running from USB drive "old" 0.360
And all tps features are active 2.350
When I write some files expected to persist 2.089
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.305
And all persistence configuration files have safe access rights 0.653
And all persistent directories from the old Tails version have safe access rights 3.025
And I take note of which tps features are available 0.504
And I shutdown Tails and wait for the computer to power off 3.071
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.648
After features/support/hooks.rb:291 0.135
After features/support/hooks.rb:75 0.010
Tags: @product
2:35.244
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.867
And I log in to a new session 15.724
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.150
And I plug USB drive "to_upgrade" 2.599
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:51.207
Then the running Tails is installed on USB drive "to_upgrade" 13.314
And I unplug USB drive "to_upgrade" 0.184
And I unplug USB drive "__internal" 0.195
After features/support/hooks.rb:291 6.654
After features/support/hooks.rb:75 0.000
Tags: @product
2:0.737
Before features/support/hooks.rb:245 0.008
Given a computer 0.262
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:50.290
Then all tps features from the old Tails version are active 1.874
And Tails is running from USB drive "to_upgrade" 0.368
And the boot device has safe access rights 3.487
And the expected persistent files created with the old Tails version are present in the filesystem 1.680
And all persistent directories from the old Tails version have safe access rights 2.773
After features/support/hooks.rb:291 0.672
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
5:42.940
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 10.808
And no SquashFS delta is installed 0.103
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.314
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.074
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.400
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.515
When the network is plugged 0.045
And Tor is ready 15.379
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.617
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.213
Given I shutdown Tails and wait for the computer to power off 5.221
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.690
Then Tails is running version 2.2~testoverlayfsng 0.107
And all tps features are active 2.460
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.392
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.096
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.269
# 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.313
When the network is plugged 0.035
And Tor is ready 13.264
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.756
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.818
Given I shutdown Tails and wait for the computer to power off 3.270
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:47.031
Then Tails is running version 2.3~testoverlayfsng 0.112
And all tps features are active 1.988
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.665
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.062
# 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.284
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.325
When the network is plugged 0.055
And Tor is ready 15.583
Then the Upgrader considers the system as up-to-date 0.264
# 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 27.504
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 2.892
After features/support/hooks.rb:291 0.756
After features/support/hooks.rb:75 0.025
Tags: @product @automatic_upgrade
26.689
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.546
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.368
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.093
And the signing key used by the Upgrader is outdated 0.572
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 14.368
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.706
After features/support/hooks.rb:291 0.648
After features/support/hooks.rb:75 0.000