Project Number Date
test_Tails_ISO_stable 4640 26 Jan 2024, 12:19

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:19.611 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:35.261
Before features/support/hooks.rb:245 0.006
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 18.782
When I start Tails from USB drive "old" with network unplugged 1:11.256
Then the boot device has safe access rights 3.044
And Tails is running from USB drive "old" 0.285
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.069
And udev-watchdog is monitoring the correct device 0.272
And I unplug USB drive "old" 0.201
After features/support/hooks.rb:291 3.564
After features/support/hooks.rb:75 0.008
Tags: @product
1:58.124
Before features/support/hooks.rb:245 0.006
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login 1:4.084
Then Tails is running from USB drive "old" 0.615
And I create a persistent partition 42.729
And I take note of which tps features are available 1.497
Then a Tails persistence partition exists on USB drive "old" 0.896
And I shutdown Tails and wait for the computer to power off 8.096
After features/support/hooks.rb:291 0.159
After features/support/hooks.rb:75 0.009
Tags: @product
2:21.860
Before features/support/hooks.rb:245 0.006
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:55.367
Then Tails is running from USB drive "old" 0.400
And all tps features are active 1.922
When I write some files expected to persist 1.821
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.263
And all persistence configuration files have safe access rights 0.414
And all persistent directories from the old Tails version have safe access rights 2.686
And I take note of which tps features are available 0.469
And I shutdown Tails and wait for the computer to power off 3.064
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.237
After features/support/hooks.rb:291 0.134
After features/support/hooks.rb:75 0.010
Tags: @product
2:32.927
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 9.437
And I log in to a new session 17.788
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.113
And I plug USB drive "to_upgrade" 2.428
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.882
Then the running Tails is installed on USB drive "to_upgrade" 13.869
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.188
After features/support/hooks.rb:291 6.871
After features/support/hooks.rb:75 0.000
Tags: @product
1:59.055
Before features/support/hooks.rb:245 0.008
Given a computer 0.211
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:48.143
Then all tps features from the old Tails version are active 1.715
And Tails is running from USB drive "to_upgrade" 0.388
And the boot device has safe access rights 3.969
And the expected persistent files created with the old Tails version are present in the filesystem 1.578
And all persistent directories from the old Tails version have safe access rights 3.048
After features/support/hooks.rb:291 0.739
After features/support/hooks.rb:75 0.011
Tags: @product @automatic_upgrade
6:25.205
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 13.676
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.365
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.098
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.355
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.580
When the network is plugged 0.040
And Tor is ready 18.005
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.526
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 10.538
Given I shutdown Tails and wait for the computer to power off 7.257
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.528
Then Tails is running version 2.2~testoverlayfsng 0.104
And all tps features are active 1.809
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.392
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.055
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.268
# 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.312
When the network is plugged 0.033
And Tor is ready 14.080
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.737
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.534
Given I shutdown Tails and wait for the computer to power off 6.315
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.939
Then Tails is running version 2.3~testoverlayfsng 0.115
And all tps features are active 2.567
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.563
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.066
# 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.310
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.297
When the network is plugged 0.052
And Tor is ready 42.394
Then the Upgrader considers the system as up-to-date 0.314
# 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.247
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.639
After features/support/hooks.rb:291 0.891
After features/support/hooks.rb:75 0.019
Tags: @product @automatic_upgrade
27.176
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.117
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.280
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.058
And the signing key used by the Upgrader is outdated 0.513
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 14.407
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.766
After features/support/hooks.rb:291 0.681
After features/support/hooks.rb:75 0.000