Project Number Date
test_Tails_ISO_stable 4517 15 Nov 2023, 19:53

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:9.676 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:22.581
Before features/support/hooks.rb:245 0.005
Given a computer 0.180
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 19.548
When I start Tails from USB drive "old" with network unplugged 57.839
Then the boot device has safe access rights 3.000
And Tails is running from USB drive "old" 0.295
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.263
And I unplug USB drive "old" 0.228
After features/support/hooks.rb:290 3.591
After features/support/hooks.rb:75 0.022
Tags: @product
1:55.133
Before features/support/hooks.rb:245 0.005
Given a computer 0.248
And I start Tails from USB drive "old" with network unplugged and I login 1:0.865
Then Tails is running from USB drive "old" 0.408
And I create a persistent partition 42.323
And I take note of which tps features are available 2.149
Then a Tails persistence partition exists on USB drive "old" 1.045
And I shutdown Tails and wait for the computer to power off 8.091
After features/support/hooks.rb:290 0.146
After features/support/hooks.rb:75 0.010
Tags: @product
2:19.151
Before features/support/hooks.rb:245 0.007
Given a computer 0.221
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:45.837
Then Tails is running from USB drive "old" 0.353
And all tps features are active 7.896
When I write some files expected to persist 1.969
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.237
And all persistence configuration files have safe access rights 0.735
And all persistent directories from the old Tails version have safe access rights 2.756
And I take note of which tps features are available 0.412
And I shutdown Tails and wait for the computer to power off 3.059
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.671
After features/support/hooks.rb:290 0.114
After features/support/hooks.rb:75 0.009
Tags: @product
2:31.441
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 9.803
And I log in to a new session 14.574
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.187
And I plug USB drive "to_upgrade" 2.404
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:49.992
Then the running Tails is installed on USB drive "to_upgrade" 13.093
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.183
After features/support/hooks.rb:290 6.715
After features/support/hooks.rb:75 0.000
Tags: @product
2:2.040
Before features/support/hooks.rb:245 0.006
Given a computer 0.208
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:45.910
Then all tps features from the old Tails version are active 7.871
And Tails is running from USB drive "to_upgrade" 0.398
And the boot device has safe access rights 3.576
And the expected persistent files created with the old Tails version are present in the filesystem 1.466
And all persistent directories from the old Tails version have safe access rights 2.607
After features/support/hooks.rb:290 0.871
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
6:3.277
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.491
And no SquashFS delta is installed 0.101
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.425
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.083
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.381
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.564
When the network is plugged 0.047
And Tor is ready 17.060
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.625
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.184
Given I shutdown Tails and wait for the computer to power off 6.480
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.651
Then Tails is running version 2.2~testoverlayfsng 0.108
And all tps features are active 9.578
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.395
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.268
# 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.283
When the network is plugged 0.032
And Tor is ready 15.716
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.643
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.504
Given I shutdown Tails and wait for the computer to power off 4.553
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.307
Then Tails is running version 2.3~testoverlayfsng 0.097
And all tps features are active 8.506
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.588
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.090
# 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.282
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.296
When the network is plugged 0.031
And Tor is ready 17.010
Then the Upgrader considers the system as up-to-date 0.257
# 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.128
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.430
After features/support/hooks.rb:290 0.714
After features/support/hooks.rb:75 0.019
Tags: @product @automatic_upgrade
56.050
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.031
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.454
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.068
And the signing key used by the Upgrader is outdated 1.249
But a current signing key is available on our website 0.000
When the network is plugged 0.055
And Tor is ready 43.617
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.574
After features/support/hooks.rb:290 0.768
After features/support/hooks.rb:75 0.000