Project Number Date
test_Tails_ISO_stable 4549 04 Dec 2023, 19:42

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:43.807 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:20.489
Before features/support/hooks.rb:245 0.004
Given a computer 0.176
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 18.004
When I start Tails from USB drive "old" with network unplugged 57.379
Then the boot device has safe access rights 2.936
And Tails is running from USB drive "old" 0.324
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.258
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:291 3.514
After features/support/hooks.rb:75 0.008
Tags: @product
1:55.655
Before features/support/hooks.rb:245 0.005
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login 1:2.447
Then Tails is running from USB drive "old" 0.440
And I create a persistent partition 42.039
And I take note of which tps features are available 1.468
Then a Tails persistence partition exists on USB drive "old" 0.873
And I shutdown Tails and wait for the computer to power off 8.199
After features/support/hooks.rb:291 0.160
After features/support/hooks.rb:75 0.009
Tags: @product
2:14.209
Before features/support/hooks.rb:245 0.005
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:48.138
Then Tails is running from USB drive "old" 0.339
And all tps features are active 2.084
When I write some files expected to persist 1.713
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.251
And all persistence configuration files have safe access rights 0.573
And all persistent directories from the old Tails version have safe access rights 2.528
And I take note of which tps features are available 0.494
And I shutdown Tails and wait for the computer to power off 3.167
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.719
After features/support/hooks.rb:291 0.098
After features/support/hooks.rb:75 0.009
Tags: @product
2:33.419
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.547
And I log in to a new session 15.428
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.191
And I plug USB drive "to_upgrade" 2.396
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:50.737
Then the running Tails is installed on USB drive "to_upgrade" 12.757
And I unplug USB drive "to_upgrade" 0.182
And I unplug USB drive "__internal" 0.179
After features/support/hooks.rb:291 3.518
After features/support/hooks.rb:75 0.000
Tags: @product
1:57.030
Before features/support/hooks.rb:245 0.007
Given a computer 0.223
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:46.986
Then all tps features from the old Tails version are active 1.685
And Tails is running from USB drive "to_upgrade" 0.324
And the boot device has safe access rights 3.426
And the expected persistent files created with the old Tails version are present in the filesystem 1.559
And all persistent directories from the old Tails version have safe access rights 2.824
After features/support/hooks.rb:291 0.729
After features/support/hooks.rb:75 0.008
Tags: @product @automatic_upgrade
5:47.233
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.623
And no SquashFS delta is installed 0.092
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.090
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.389
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.594
When the network is plugged 0.049
And Tor is ready 15.463
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.589
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.849
Given I shutdown Tails and wait for the computer to power off 6.292
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.103
Then Tails is running version 2.2~testoverlayfsng 0.104
And all tps features are active 2.261
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.363
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.277
# 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.048
And Tor is ready 14.987
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.530
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.217
Given I shutdown Tails and wait for the computer to power off 4.367
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.504
Then Tails is running version 2.3~testoverlayfsng 0.120
And all tps features are active 2.376
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.584
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.079
# 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.287
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.280
When the network is plugged 0.051
And Tor is ready 17.468
Then the Upgrader considers the system as up-to-date 0.580
# 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 24.865
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.061
After features/support/hooks.rb:291 0.747
After features/support/hooks.rb:75 0.018
Tags: @product @automatic_upgrade
55.769
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 9.417
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.055
And the signing key used by the Upgrader is outdated 1.498
But a current signing key is available on our website 0.000
When the network is plugged 0.048
And Tor is ready 43.887
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.561
After features/support/hooks.rb:291 0.650
After features/support/hooks.rb:75 0.000