Project Number Date
test_Tails_ISO_stable 4613 10 Jan 2024, 22:03

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:54.906 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:21.936
Before features/support/hooks.rb:245 0.006
Given a computer 0.133
And I create a 7200 MiB disk named "old" 0.025
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 18.110
When I start Tails from USB drive "old" with network unplugged 58.375
Then the boot device has safe access rights 3.267
And Tails is running from USB drive "old" 0.331
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.063
And udev-watchdog is monitoring the correct device 0.330
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:291 3.534
After features/support/hooks.rb:75 0.046
Tags: @product
1:59.225
Before features/support/hooks.rb:245 0.006
Given a computer 0.144
And I start Tails from USB drive "old" with network unplugged and I login 1:4.391
Then Tails is running from USB drive "old" 0.474
And I create a persistent partition 44.754
And I take note of which tps features are available 1.595
Then a Tails persistence partition exists on USB drive "old" 0.784
And I shutdown Tails and wait for the computer to power off 7.081
After features/support/hooks.rb:291 0.121
After features/support/hooks.rb:75 0.010
Tags: @product
2:21.899
Before features/support/hooks.rb:245 0.004
Given a computer 0.143
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:55.716
Then Tails is running from USB drive "old" 0.386
And all tps features are active 1.930
When I write some files expected to persist 1.818
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.261
And all persistence configuration files have safe access rights 0.664
And all persistent directories from the old Tails version have safe access rights 2.773
And I take note of which tps features are available 0.320
And I shutdown Tails and wait for the computer to power off 3.063
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.821
After features/support/hooks.rb:291 0.171
After features/support/hooks.rb:75 0.010
Tags: @product
2:33.835
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 11.466
And I log in to a new session 15.929
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.094
And I plug USB drive "to_upgrade" 2.445
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.618
Then the running Tails is installed on USB drive "to_upgrade" 13.897
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.176
After features/support/hooks.rb:291 6.666
After features/support/hooks.rb:75 0.000
Tags: @product
1:55.666
Before features/support/hooks.rb:245 0.007
Given a computer 0.145
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:45.181
Then all tps features from the old Tails version are active 1.499
And Tails is running from USB drive "to_upgrade" 0.326
And the boot device has safe access rights 4.138
And the expected persistent files created with the old Tails version are present in the filesystem 1.547
And all persistent directories from the old Tails version have safe access rights 2.829
After features/support/hooks.rb:291 0.969
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
7:13.421
Before features/support/hooks.rb:245 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:9.055
And no SquashFS delta is installed 0.139
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.300
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.066
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.358
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.577
When the network is plugged 0.023
And Tor is ready 16.338
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.827
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.779
Given I shutdown Tails and wait for the computer to power off 6.340
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.569
Then Tails is running version 2.2~testoverlayfsng 0.154
And all tps features are active 2.111
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.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.316
# 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.331
When the network is plugged 0.025
And Tor is ready 45.104
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 0.595
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.233
Given I shutdown Tails and wait for the computer to power off 4.183
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:45.522
Then Tails is running version 2.3~testoverlayfsng 0.114
And all tps features are active 1.630
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.674
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.082
# 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.310
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.307
When the network is plugged 0.050
And Tor is ready 15.884
Then the Upgrader considers the system as up-to-date 0.248
# 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.559
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.151
After features/support/hooks.rb:291 0.790
After features/support/hooks.rb:75 0.019
Tags: @product @automatic_upgrade
28.920
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.296
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.386
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.064
And the signing key used by the Upgrader is outdated 0.861
But a current signing key is available on our website 0.000
When the network is plugged 0.023
And Tor is ready 15.694
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.594
After features/support/hooks.rb:291 0.927
After features/support/hooks.rb:75 0.000