Project Number Date
test_Tails_ISO_stable 4620 16 Jan 2024, 12:09

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:55.078 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:19.582
Before features/support/hooks.rb:245 0.005
Given a computer 0.282
And I create a 7200 MiB disk named "old" 0.062
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 18.073
When I start Tails from USB drive "old" with network unplugged 56.193
Then the boot device has safe access rights 3.001
And Tails is running from USB drive "old" 0.312
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.065
And udev-watchdog is monitoring the correct device 0.265
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:291 3.737
After features/support/hooks.rb:75 0.009
Tags: @product
2:6.363
Before features/support/hooks.rb:245 0.006
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login 1:12.187
Then Tails is running from USB drive "old" 0.366
And I create a persistent partition 43.962
And I take note of which tps features are available 1.661
Then a Tails persistence partition exists on USB drive "old" 0.871
And I shutdown Tails and wait for the computer to power off 7.126
After features/support/hooks.rb:291 0.140
After features/support/hooks.rb:75 0.010
Tags: @product
2:11.711
Before features/support/hooks.rb:245 0.005
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:45.700
Then Tails is running from USB drive "old" 0.315
And all tps features are active 1.964
When I write some files expected to persist 1.858
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.217
And all persistence configuration files have safe access rights 0.522
And all persistent directories from the old Tails version have safe access rights 2.594
And I take note of which tps features are available 0.491
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" 14.788
After features/support/hooks.rb:291 0.146
After features/support/hooks.rb:75 0.009
Tags: @product
2:37.910
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.934
And I log in to a new session 23.326
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.108
And I plug USB drive "to_upgrade" 2.482
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.160
Then the running Tails is installed on USB drive "to_upgrade" 12.532
And I unplug USB drive "to_upgrade" 0.190
And I unplug USB drive "__internal" 0.174
After features/support/hooks.rb:291 6.586
After features/support/hooks.rb:75 0.000
Tags: @product
1:57.272
Before features/support/hooks.rb:245 0.005
Given a computer 0.181
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:47.303
Then all tps features from the old Tails version are active 1.677
And Tails is running from USB drive "to_upgrade" 0.332
And the boot device has safe access rights 3.541
And the expected persistent files created with the old Tails version are present in the filesystem 1.480
And all persistent directories from the old Tails version have safe access rights 2.756
After features/support/hooks.rb:291 0.595
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
6:12.995
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.616
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.323
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.091
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.370
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.546
When the network is plugged 0.065
And Tor is ready 18.528
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.781
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.165
Given I shutdown Tails and wait for the computer to power off 5.329
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:41.626
Then Tails is running version 2.2~testoverlayfsng 0.100
And all tps features are active 2.378
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.445
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.094
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.290
# 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.277
When the network is plugged 0.032
And Tor is ready 13.626
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.681
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.724
Given I shutdown Tails and wait for the computer to power off 3.576
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.434
Then Tails is running version 2.3~testoverlayfsng 0.140
And all tps features are active 2.086
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.627
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.057
# 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.278
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.297
When the network is plugged 0.037
And Tor is ready 42.096
Then the Upgrader considers the system as up-to-date 0.293
# 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 30.270
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.610
After features/support/hooks.rb:291 0.739
After features/support/hooks.rb:75 0.023
Tags: @product @automatic_upgrade
29.241
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.424
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.312
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.076
And the signing key used by the Upgrader is outdated 1.178
But a current signing key is available on our website 0.000
When the network is plugged 0.055
And Tor is ready 15.385
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.808
After features/support/hooks.rb:291 0.602
After features/support/hooks.rb:75 0.000