Project Number Date
test_Tails_ISO_devel 3188 10 Dec 2023, 12:26

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:13.598 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.926
Before features/support/hooks.rb:245 0.006
Given a computer 0.186
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 18.257
When I start Tails from USB drive "old" with network unplugged 58.135
Then the boot device has safe access rights 3.253
And Tails is running from USB drive "old" 0.343
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.068
And udev-watchdog is monitoring the correct device 0.299
And I unplug USB drive "old" 0.204
After features/support/hooks.rb:291 3.788
After features/support/hooks.rb:75 0.010
Tags: @product
1:58.810
Before features/support/hooks.rb:245 0.006
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login 1:6.028
Then Tails is running from USB drive "old" 0.437
And I create a persistent partition 42.931
And I take note of which tps features are available 1.290
Then a Tails persistence partition exists on USB drive "old" 0.809
And I shutdown Tails and wait for the computer to power off 7.080
After features/support/hooks.rb:291 0.140
After features/support/hooks.rb:75 0.013
Tags: @product
2:21.918
Before features/support/hooks.rb:245 0.009
Given a computer 0.238
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:53.895
Then Tails is running from USB drive "old" 0.396
And all tps features are active 2.353
When I write some files expected to persist 2.062
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.240
And all persistence configuration files have safe access rights 0.946
And all persistent directories from the old Tails version have safe access rights 3.133
And I take note of which tps features are available 0.496
And I shutdown Tails and wait for the computer to power off 3.066
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.088
After features/support/hooks.rb:291 0.149
After features/support/hooks.rb:75 0.010
Tags: @product
2:33.374
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.415
And I log in to a new session 15.280
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.214
And I plug USB drive "to_upgrade" 2.438
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:49.281
Then the running Tails is installed on USB drive "to_upgrade" 13.261
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.281
After features/support/hooks.rb:291 3.513
After features/support/hooks.rb:75 0.000
Tags: @product
1:56.216
Before features/support/hooks.rb:245 0.007
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:44.940
Then all tps features from the old Tails version are active 1.620
And Tails is running from USB drive "to_upgrade" 0.355
And the boot device has safe access rights 4.600
And the expected persistent files created with the old Tails version are present in the filesystem 1.599
And all persistent directories from the old Tails version have safe access rights 2.909
After features/support/hooks.rb:291 0.621
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
5:35.367
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.715
And no SquashFS delta is installed 0.296
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.261
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.055
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.347
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.545
When the network is plugged 0.042
And Tor is ready 15.142
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.703
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 10.280
Given I shutdown Tails and wait for the computer to power off 5.244
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:47.041
Then Tails is running version 2.2~testoverlayfsng 0.121
And all tps features are active 2.220
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.418
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.088
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.293
# 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.274
When the network is plugged 0.036
And Tor is ready 15.600
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.554
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.233
Given I shutdown Tails and wait for the computer to power off 4.291
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.349
Then Tails is running version 2.3~testoverlayfsng 0.122
And all tps features are active 2.109
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.602
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.278
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.296
When the network is plugged 0.057
And Tor is ready 13.806
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 26.964
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.592
After features/support/hooks.rb:291 0.740
After features/support/hooks.rb:75 0.018
Tags: @product @automatic_upgrade
25.985
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.577
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.456
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.060
And the signing key used by the Upgrader is outdated 0.440
But a current signing key is available on our website 0.000
When the network is plugged 0.058
And Tor is ready 13.650
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.741
After features/support/hooks.rb:291 0.769
After features/support/hooks.rb:75 0.000