Project Number Date
test_Tails_ISO_devel 3225 07 Jan 2024, 12:34

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:0.136 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:28.201
Before features/support/hooks.rb:245 0.005
Given a computer 0.220
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 22.713
When I start Tails from USB drive "old" with network unplugged 59.861
Then the boot device has safe access rights 3.410
And Tails is running from USB drive "old" 0.306
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.064
And udev-watchdog is monitoring the correct device 0.253
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:291 3.548
After features/support/hooks.rb:75 0.011
Tags: @product
2:0.773
Before features/support/hooks.rb:245 0.008
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login 1:5.076
Then Tails is running from USB drive "old" 0.446
And I create a persistent partition 45.608
And I take note of which tps features are available 1.507
Then a Tails persistence partition exists on USB drive "old" 0.843
And I shutdown Tails and wait for the computer to power off 7.087
After features/support/hooks.rb:291 0.137
After features/support/hooks.rb:75 0.012
Tags: @product
2:21.755
Before features/support/hooks.rb:245 0.007
Given a computer 0.226
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:53.283
Then Tails is running from USB drive "old" 0.369
And all tps features are active 2.262
When I write some files expected to persist 1.855
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.242
And all persistence configuration files have safe access rights 0.633
And all persistent directories from the old Tails version have safe access rights 2.548
And I take note of which tps features are available 0.535
And I shutdown Tails and wait for the computer to power off 3.070
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.728
After features/support/hooks.rb:291 0.148
After features/support/hooks.rb:75 0.012
Tags: @product
2:36.089
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.904
And I log in to a new session 16.025
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.262
And I plug USB drive "to_upgrade" 2.428
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:49.789
Then the running Tails is installed on USB drive "to_upgrade" 13.295
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.176
After features/support/hooks.rb:291 0.794
After features/support/hooks.rb:75 0.000
Tags: @product
2:0.211
Before features/support/hooks.rb:245 0.007
Given a computer 0.183
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:49.765
Then all tps features from the old Tails version are active 1.746
And Tails is running from USB drive "to_upgrade" 0.387
And the boot device has safe access rights 3.591
And the expected persistent files created with the old Tails version are present in the filesystem 1.541
And all persistent directories from the old Tails version have safe access rights 2.994
After features/support/hooks.rb:291 0.696
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
6:4.410
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 11.822
And no SquashFS delta is installed 0.327
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.357
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.081
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.406
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.625
When the network is plugged 0.045
And Tor is ready 18.023
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.913
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.679
Given I shutdown Tails and wait for the computer to power off 12.426
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.573
Then Tails is running version 2.2~testoverlayfsng 0.118
And all tps features are active 2.206
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.378
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.289
# 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.050
And Tor is ready 14.867
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.671
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.229
Given I shutdown Tails and wait for the computer to power off 4.331
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.485
Then Tails is running version 2.3~testoverlayfsng 0.117
And all tps features are active 2.623
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.692
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.089
# 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.307
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.251
When the network is plugged 0.046
And Tor is ready 20.949
Then the Upgrader considers the system as up-to-date 0.246
# 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.173
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.652
After features/support/hooks.rb:291 0.891
After features/support/hooks.rb:75 0.017
Tags: @product @automatic_upgrade
28.695
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 9.887
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.517
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.046
And the signing key used by the Upgrader is outdated 0.526
But a current signing key is available on our website 0.000
When the network is plugged 0.053
And Tor is ready 16.062
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.601
After features/support/hooks.rb:291 0.783
After features/support/hooks.rb:75 0.000