Project Number Date
test_Tails_ISO_stable 4558 07 Dec 2023, 20:51

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:6.317 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:33.761
Before features/support/hooks.rb:245 0.005
Given a computer 0.212
And I create a 7200 MiB disk named "old" 0.028
And I plug USB drive "old" 1.042
And I write an old version of the Tails USB image to disk "old" 24.077
When I start Tails from USB drive "old" with network unplugged 1:4.276
Then the boot device has safe access rights 3.208
And Tails is running from USB drive "old" 0.330
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.259
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:291 6.679
After features/support/hooks.rb:75 0.010
Tags: @product
2:1.344
Before features/support/hooks.rb:245 0.007
Given a computer 0.164
And I start Tails from USB drive "old" with network unplugged and I login 1:6.573
Then Tails is running from USB drive "old" 0.416
And I create a persistent partition 44.822
And I take note of which tps features are available 1.250
Then a Tails persistence partition exists on USB drive "old" 0.926
And I shutdown Tails and wait for the computer to power off 7.192
After features/support/hooks.rb:291 0.143
After features/support/hooks.rb:75 0.012
Tags: @product
2:19.794
Before features/support/hooks.rb:245 0.005
Given a computer 0.147
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:50.006
Then Tails is running from USB drive "old" 0.387
And all tps features are active 2.139
When I write some files expected to persist 2.044
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.202
And all persistence configuration files have safe access rights 0.665
And all persistent directories from the old Tails version have safe access rights 3.026
And I take note of which tps features are available 0.341
And I shutdown Tails and wait for the computer to power off 4.170
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.665
After features/support/hooks.rb:291 0.147
After features/support/hooks.rb:75 0.012
Tags: @product
2:32.645
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.301
And I log in to a new session 16.433
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.240
And I plug USB drive "to_upgrade" 2.452
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.724
Then the running Tails is installed on USB drive "to_upgrade" 14.022
And I unplug USB drive "to_upgrade" 0.279
And I unplug USB drive "__internal" 0.191
After features/support/hooks.rb:291 3.491
After features/support/hooks.rb:75 0.000
Tags: @product
2:14.172
Before features/support/hooks.rb:245 0.006
Given a computer 0.152
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.933
Then all tps features from the old Tails version are active 1.610
And Tails is running from USB drive "to_upgrade" 0.343
And the boot device has safe access rights 3.852
And the expected persistent files created with the old Tails version are present in the filesystem 1.550
And all persistent directories from the old Tails version have safe access rights 2.730
After features/support/hooks.rb:291 0.819
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
5:54.914
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.355
And no SquashFS delta is installed 0.156
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.457
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.094
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.494
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.630
When the network is plugged 0.029
And Tor is ready 17.168
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.977
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 10.221
Given I shutdown Tails and wait for the computer to power off 6.770
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.427
Then Tails is running version 2.2~testoverlayfsng 0.131
And all tps features are active 1.798
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.369
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.288
# 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.356
When the network is plugged 0.034
And Tor is ready 17.743
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.689
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.648
Given I shutdown Tails and wait for the computer to power off 4.477
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.718
Then Tails is running version 2.3~testoverlayfsng 0.100
And all tps features are active 2.572
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.549
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.103
# 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.293
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.296
When the network is plugged 0.054
And Tor is ready 15.644
Then the Upgrader considers the system as up-to-date 0.254
# 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.424
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.511
After features/support/hooks.rb:291 0.814
After features/support/hooks.rb:75 0.020
Tags: @product @automatic_upgrade
29.684
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.934
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.373
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.116
And the signing key used by the Upgrader is outdated 1.125
But a current signing key is available on our website 0.000
When the network is plugged 0.031
And Tor is ready 13.237
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 4.864
After features/support/hooks.rb:291 0.656
After features/support/hooks.rb:75 0.000