Project Number Date
test_Tails_ISO_stable 4532 25 Nov 2023, 12:32

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:45.548 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:25.966
Before features/support/hooks.rb:245 0.008
Given a computer 0.213
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 21.990
When I start Tails from USB drive "old" with network unplugged 58.691
Then the boot device has safe access rights 2.975
And Tails is running from USB drive "old" 0.326
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.071
And udev-watchdog is monitoring the correct device 0.301
And I unplug USB drive "old" 0.211
After features/support/hooks.rb:291 3.472
After features/support/hooks.rb:75 0.012
Tags: @product
2:11.054
Before features/support/hooks.rb:245 0.006
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login 1:17.335
Then Tails is running from USB drive "old" 0.520
And I create a persistent partition 43.401
And I take note of which tps features are available 1.623
Then a Tails persistence partition exists on USB drive "old" 0.904
And I shutdown Tails and wait for the computer to power off 7.079
After features/support/hooks.rb:291 0.191
After features/support/hooks.rb:75 0.010
Tags: @product
2:24.127
Before features/support/hooks.rb:245 0.006
Given a computer 0.219
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:55.245
Then Tails is running from USB drive "old" 0.397
And all tps features are active 2.117
When I write some files expected to persist 1.797
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.674
And all persistent directories from the old Tails version have safe access rights 3.073
And I take note of which tps features are available 0.659
And I shutdown Tails and wait for the computer to power off 3.192
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.525
After features/support/hooks.rb:291 0.152
After features/support/hooks.rb:75 0.010
Tags: @product
2:36.189
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 10.925
And I log in to a new session 17.044
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.378
And I plug USB drive "to_upgrade" 2.642
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:49.038
Then the running Tails is installed on USB drive "to_upgrade" 14.750
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.197
After features/support/hooks.rb:291 2.035
After features/support/hooks.rb:75 0.000
Tags: @product
2:5.980
Before features/support/hooks.rb:245 0.009
Given a computer 0.213
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:55.083
Then all tps features from the old Tails version are active 1.796
And Tails is running from USB drive "to_upgrade" 0.422
And the boot device has safe access rights 3.770
And the expected persistent files created with the old Tails version are present in the filesystem 1.789
And all persistent directories from the old Tails version have safe access rights 2.904
After features/support/hooks.rb:291 0.755
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
6:33.481
Before features/support/hooks.rb:245 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.511
And no SquashFS delta is installed 0.159
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.477
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.097
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.414
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.631
When the network is plugged 0.046
And Tor is ready 18.801
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.785
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 10.774
Given I shutdown Tails and wait for the computer to power off 7.322
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.788
Then Tails is running version 2.2~testoverlayfsng 0.135
And all tps features are active 2.557
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.481
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.086
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.292
# 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.381
When the network is plugged 0.055
And Tor is ready 45.364
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 0.635
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.164
Given I shutdown Tails and wait for the computer to power off 4.130
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.949
Then Tails is running version 2.3~testoverlayfsng 0.104
And all tps features are active 2.278
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.659
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.078
# 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.328
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.352
When the network is plugged 0.034
And Tor is ready 16.143
Then the Upgrader considers the system as up-to-date 0.285
# 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.408
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.758
After features/support/hooks.rb:291 0.902
After features/support/hooks.rb:75 0.030
Tags: @product @automatic_upgrade
28.749
Before features/support/hooks.rb:245 0.019
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.543
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.475
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.052
And the signing key used by the Upgrader is outdated 0.612
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 14.148
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.881
After features/support/hooks.rb:291 0.826
After features/support/hooks.rb:75 0.000