Project Number Date
test_Tails_ISO_stable 4592 26 Dec 2023, 12:04

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:53.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:28.863
Before features/support/hooks.rb:245 0.008
Given a computer 0.180
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 22.057
When I start Tails from USB drive "old" with network unplugged 1:1.714
Then the boot device has safe access rights 2.893
And Tails is running from USB drive "old" 0.315
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.237
And I unplug USB drive "old" 0.247
After features/support/hooks.rb:291 7.946
After features/support/hooks.rb:75 0.009
Tags: @product
2:1.550
Before features/support/hooks.rb:245 0.005
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login 1:5.881
Then Tails is running from USB drive "old" 0.405
And I create a persistent partition 44.590
And I take note of which tps features are available 1.573
Then a Tails persistence partition exists on USB drive "old" 0.816
And I shutdown Tails and wait for the computer to power off 8.098
After features/support/hooks.rb:291 0.189
After features/support/hooks.rb:75 0.010
Tags: @product
2:27.014
Before features/support/hooks.rb:245 0.007
Given a computer 0.242
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:59.945
Then Tails is running from USB drive "old" 0.359
And all tps features are active 2.342
When I write some files expected to persist 2.040
# 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.733
And all persistent directories from the old Tails version have safe access rights 2.895
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.078
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.628
After features/support/hooks.rb:291 0.198
After features/support/hooks.rb:75 0.009
Tags: @product
2:35.287
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.076
And I log in to a new session 20.100
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.272
And I plug USB drive "to_upgrade" 2.529
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.987
Then the running Tails is installed on USB drive "to_upgrade" 12.952
And I unplug USB drive "to_upgrade" 0.189
And I unplug USB drive "__internal" 0.178
After features/support/hooks.rb:291 6.820
After features/support/hooks.rb:75 0.000
Tags: @product
1:56.166
Before features/support/hooks.rb:245 0.006
Given a computer 0.175
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:46.424
Then all tps features from the old Tails version are active 1.503
And Tails is running from USB drive "to_upgrade" 0.336
And the boot device has safe access rights 3.494
And the expected persistent files created with the old Tails version are present in the filesystem 1.565
And all persistent directories from the old Tails version have safe access rights 2.667
After features/support/hooks.rb:291 0.696
After features/support/hooks.rb:75 0.012
Tags: @product @automatic_upgrade
5:58.296
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.921
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.325
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.078
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.370
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.501
When the network is plugged 0.039
And Tor is ready 16.758
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.618
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.072
Given I shutdown Tails and wait for the computer to power off 5.318
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.384
Then Tails is running version 2.2~testoverlayfsng 0.103
And all tps features are active 2.282
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.453
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.283
# 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.313
When the network is plugged 0.044
And Tor is ready 17.059
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.743
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.928
Given I shutdown Tails and wait for the computer to power off 4.309
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.015
Then Tails is running version 2.3~testoverlayfsng 0.098
And all tps features are active 2.074
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.572
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.099
# 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.304
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.310
When the network is plugged 0.042
And Tor is ready 16.609
Then the Upgrader considers the system as up-to-date 0.265
# 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 29.404
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.449
After features/support/hooks.rb:291 0.675
After features/support/hooks.rb:75 0.018
Tags: @product @automatic_upgrade
26.628
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.519
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.319
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.064
And the signing key used by the Upgrader is outdated 0.557
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 13.410
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.724
After features/support/hooks.rb:291 1.150
After features/support/hooks.rb:75 0.000