Project Number Date
test_Tails_ISO_devel 3207 22 Dec 2023, 15:26

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:44.730 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:36.031
Before features/support/hooks.rb:245 0.005
Given a computer 0.165
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 19.328
When I start Tails from USB drive "old" with network unplugged 1:11.069
Then the boot device has safe access rights 3.303
And Tails is running from USB drive "old" 0.445
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.272
And I unplug USB drive "old" 0.216
After features/support/hooks.rb:291 3.480
After features/support/hooks.rb:75 0.010
Tags: @product
1:57.559
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:4.529
Then Tails is running from USB drive "old" 0.587
And I create a persistent partition 42.733
And I take note of which tps features are available 1.571
Then a Tails persistence partition exists on USB drive "old" 0.835
And I shutdown Tails and wait for the computer to power off 7.124
After features/support/hooks.rb:291 0.126
After features/support/hooks.rb:75 0.009
Tags: @product
2:17.256
Before features/support/hooks.rb:245 0.005
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:50.208
Then Tails is running from USB drive "old" 0.378
And all tps features are active 2.203
When I write some files expected to persist 1.754
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.272
And all persistence configuration files have safe access rights 0.689
And all persistent directories from the old Tails version have safe access rights 3.092
And I take note of which tps features are available 0.542
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.832
After features/support/hooks.rb:291 0.146
After features/support/hooks.rb:75 0.011
Tags: @product
2:34.375
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 10.949
And I log in to a new session 16.328
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.143
And I plug USB drive "to_upgrade" 2.437
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:50.638
Then the running Tails is installed on USB drive "to_upgrade" 12.496
And I unplug USB drive "to_upgrade" 0.192
And I unplug USB drive "__internal" 0.187
After features/support/hooks.rb:291 6.719
After features/support/hooks.rb:75 0.000
Tags: @product
1:59.767
Before features/support/hooks.rb:245 0.005
Given a computer 0.206
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:49.089
Then all tps features from the old Tails version are active 1.669
And Tails is running from USB drive "to_upgrade" 0.397
And the boot device has safe access rights 3.812
And the expected persistent files created with the old Tails version are present in the filesystem 1.582
And all persistent directories from the old Tails version have safe access rights 3.009
After features/support/hooks.rb:291 0.760
After features/support/hooks.rb:75 0.012
Tags: @product @automatic_upgrade
5:52.856
Before features/support/hooks.rb:245 0.014
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.388
And no SquashFS delta is installed 0.118
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.400
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.071
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.424
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.569
When the network is plugged 0.066
And Tor is ready 18.114
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.736
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 10.253
Given I shutdown Tails and wait for the computer to power off 7.281
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.796
Then Tails is running version 2.2~testoverlayfsng 0.143
And all tps features are active 2.328
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.381
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.302
# 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.328
When the network is plugged 0.044
And Tor is ready 15.039
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.600
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.989
Given I shutdown Tails and wait for the computer to power off 4.466
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:45.540
Then Tails is running version 2.3~testoverlayfsng 0.098
And all tps features are active 1.963
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.554
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.061
# 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.253
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.276
When the network is plugged 0.063
And Tor is ready 15.102
Then the Upgrader considers the system as up-to-date 0.255
# 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 25.245
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.521
After features/support/hooks.rb:291 0.777
After features/support/hooks.rb:75 0.016
Tags: @product @automatic_upgrade
26.885
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.640
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.437
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.100
And the signing key used by the Upgrader is outdated 0.548
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 13.458
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.662
After features/support/hooks.rb:291 1.029
After features/support/hooks.rb:75 0.000