Project Number Date
test_Tails_ISO_stable 4629 22 Jan 2024, 15:45

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:14.547 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.669
Before features/support/hooks.rb:245 0.007
Given a computer 0.918
And I create a 7200 MiB disk named "old" 0.126
And I plug USB drive "old" 1.121
And I write an old version of the Tails USB image to disk "old" 19.673
When I start Tails from USB drive "old" with network unplugged 1:6.726
Then the boot device has safe access rights 3.189
And Tails is running from USB drive "old" 0.315
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.270
And I unplug USB drive "old" 0.209
After features/support/hooks.rb:291 3.514
After features/support/hooks.rb:75 0.009
Tags: @product
2:2.637
Before features/support/hooks.rb:245 0.005
Given a computer 0.204
And I start Tails from USB drive "old" with network unplugged and I login 1:6.027
Then Tails is running from USB drive "old" 0.484
And I create a persistent partition 45.432
And I take note of which tps features are available 1.608
Then a Tails persistence partition exists on USB drive "old" 0.807
And I shutdown Tails and wait for the computer to power off 8.073
After features/support/hooks.rb:291 0.161
After features/support/hooks.rb:75 0.010
Tags: @product
2:29.651
Before features/support/hooks.rb:245 0.006
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:1.407
Then Tails is running from USB drive "old" 0.351
And all tps features are active 2.155
When I write some files expected to persist 1.977
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.247
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.624
And I take note of which tps features are available 0.607
And I shutdown Tails and wait for the computer to power off 3.072
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.350
After features/support/hooks.rb:291 0.183
After features/support/hooks.rb:75 0.012
Tags: @product
2:37.868
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 11.651
And I log in to a new session 19.204
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.072
And I plug USB drive "to_upgrade" 2.422
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.712
Then the running Tails is installed on USB drive "to_upgrade" 14.399
And I unplug USB drive "to_upgrade" 0.223
And I unplug USB drive "__internal" 0.182
After features/support/hooks.rb:291 6.935
After features/support/hooks.rb:75 0.000
Tags: @product
2:6.420
Before features/support/hooks.rb:245 0.007
Given a computer 0.207
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:56.311
Then all tps features from the old Tails version are active 1.788
And Tails is running from USB drive "to_upgrade" 0.358
And the boot device has safe access rights 3.290
And the expected persistent files created with the old Tails version are present in the filesystem 1.535
And all persistent directories from the old Tails version have safe access rights 2.929
After features/support/hooks.rb:291 0.662
After features/support/hooks.rb:75 0.013
Tags: @product @automatic_upgrade
5:57.761
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 10.896
And no SquashFS delta is installed 0.297
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.396
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.054
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.421
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.564
When the network is plugged 0.055
And Tor is ready 15.075
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.693
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.254
Given I shutdown Tails and wait for the computer to power off 6.256
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.793
Then Tails is running version 2.2~testoverlayfsng 0.102
And all tps features are active 2.133
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.461
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.100
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.310
# 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.320
When the network is plugged 0.034
And Tor is ready 15.466
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.764
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 10.266
Given I shutdown Tails and wait for the computer to power off 4.452
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.257
Then Tails is running version 2.3~testoverlayfsng 0.138
And all tps features are active 2.263
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.610
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.085
# 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.337
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.339
When the network is plugged 0.047
And Tor is ready 17.689
Then the Upgrader considers the system as up-to-date 0.739
# 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.606
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.473
After features/support/hooks.rb:291 0.873
After features/support/hooks.rb:75 0.025
Tags: @product @automatic_upgrade
27.539
Before features/support/hooks.rb:245 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.206
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.363
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.069
And the signing key used by the Upgrader is outdated 0.699
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 14.480
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.681
After features/support/hooks.rb:291 0.654
After features/support/hooks.rb:75 0.000