Project Number Date
test_Tails_ISO_stable 4571 17 Dec 2023, 12:01

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 15:50.120 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:32.038
Before features/support/hooks.rb:245 0.005
Given a computer 0.179
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 18.512
When I start Tails from USB drive "old" with network unplugged 1:8.352
Then the boot device has safe access rights 2.992
And Tails is running from USB drive "old" 0.345
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.255
And I unplug USB drive "old" 0.174
After features/support/hooks.rb:291 3.506
After features/support/hooks.rb:75 0.010
Tags: @product
1:52.924
Before features/support/hooks.rb:245 0.007
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login 58.906
Then Tails is running from USB drive "old" 0.419
And I create a persistent partition 43.088
And I take note of which tps features are available 1.500
Then a Tails persistence partition exists on USB drive "old" 0.758
And I shutdown Tails and wait for the computer to power off 8.066
After features/support/hooks.rb:291 0.156
After features/support/hooks.rb:75 0.009
Tags: @product
2:12.354
Before features/support/hooks.rb:245 0.005
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:46.014
Then Tails is running from USB drive "old" 0.338
And all tps features are active 2.045
When I write some files expected to persist 1.772
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.249
And all persistence configuration files have safe access rights 0.650
And all persistent directories from the old Tails version have safe access rights 2.577
And I take note of which tps features are available 0.491
And I shutdown Tails and wait for the computer to power off 3.068
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.932
After features/support/hooks.rb:291 0.118
After features/support/hooks.rb:75 0.011
Tags: @product
2:33.375
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 12.215
And I log in to a new session 14.892
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.957
And I plug USB drive "to_upgrade" 2.446
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:49.182
Then the running Tails is installed on USB drive "to_upgrade" 13.284
And I unplug USB drive "to_upgrade" 0.192
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:291 6.597
After features/support/hooks.rb:75 0.000
Tags: @product
1:50.132
Before features/support/hooks.rb:245 0.005
Given a computer 0.163
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:40.423
Then all tps features from the old Tails version are active 1.630
And Tails is running from USB drive "to_upgrade" 0.347
And the boot device has safe access rights 3.482
And the expected persistent files created with the old Tails version are present in the filesystem 1.528
And all persistent directories from the old Tails version have safe access rights 2.555
After features/support/hooks.rb:291 0.703
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
5:21.903
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 10.505
And no SquashFS delta is installed 0.142
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.316
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.089
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.404
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.525
When the network is plugged 0.053
And Tor is ready 14.528
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.561
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.797
Given I shutdown Tails and wait for the computer to power off 5.263
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:42.452
Then Tails is running version 2.2~testoverlayfsng 0.112
And all tps features are active 2.321
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.383
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.094
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.294
# 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.262
When the network is plugged 0.041
And Tor is ready 14.201
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.608
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.298
Given I shutdown Tails and wait for the computer to power off 3.125
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:41.779
Then Tails is running version 2.3~testoverlayfsng 0.090
And all tps features are active 2.028
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.598
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.061
# 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.291
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.308
When the network is plugged 0.055
And Tor is ready 13.743
Then the Upgrader considers the system as up-to-date 0.255
# 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.085
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.220
After features/support/hooks.rb:291 1.085
After features/support/hooks.rb:75 0.019
Tags: @product @automatic_upgrade
27.391
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.334
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.403
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.067
And the signing key used by the Upgrader is outdated 0.599
But a current signing key is available on our website 0.000
When the network is plugged 0.040
And Tor is ready 14.344
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.601
After features/support/hooks.rb:291 0.652
After features/support/hooks.rb:75 0.000