Project Number Date
test_Tails_ISO_stable 4569 14 Dec 2023, 12:08

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:41.759 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:24.797
Before features/support/hooks.rb:245 0.006
Given a computer 0.193
And I create a 7200 MiB disk named "old" 0.064
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 18.710
When I start Tails from USB drive "old" with network unplugged 1:1.096
Then the boot device has safe access rights 2.820
And Tails is running from USB drive "old" 0.310
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.247
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:291 3.542
After features/support/hooks.rb:75 0.013
Tags: @product
1:52.121
Before features/support/hooks.rb:245 0.006
Given a computer 0.168
And I start Tails from USB drive "old" with network unplugged and I login 57.443
Then Tails is running from USB drive "old" 0.456
And I create a persistent partition 42.302
And I take note of which tps features are available 2.731
Then a Tails persistence partition exists on USB drive "old" 0.795
And I shutdown Tails and wait for the computer to power off 8.223
After features/support/hooks.rb:291 0.147
After features/support/hooks.rb:75 0.010
Tags: @product
2:8.202
Before features/support/hooks.rb:245 0.006
Given a computer 0.229
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:41.121
Then Tails is running from USB drive "old" 0.301
And all tps features are active 2.160
When I write some files expected to persist 1.814
# 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.576
And all persistent directories from the old Tails version have safe access rights 2.710
And I take note of which tps features are available 1.234
And I shutdown Tails and wait for the computer to power off 3.106
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.698
After features/support/hooks.rb:291 0.121
After features/support/hooks.rb:75 0.008
Tags: @product
2:30.521
Before features/support/hooks.rb:245 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.797
And I log in to a new session 15.106
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.133
And I plug USB drive "to_upgrade" 2.541
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.527
Then the running Tails is installed on USB drive "to_upgrade" 13.982
And I unplug USB drive "to_upgrade" 0.215
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:291 3.603
After features/support/hooks.rb:75 0.000
Tags: @product
1:49.939
Before features/support/hooks.rb:245 0.008
Given a computer 0.193
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:39.965
Then all tps features from the old Tails version are active 1.669
And Tails is running from USB drive "to_upgrade" 0.328
And the boot device has safe access rights 3.472
And the expected persistent files created with the old Tails version are present in the filesystem 1.576
And all persistent directories from the old Tails version have safe access rights 2.733
After features/support/hooks.rb:291 0.608
After features/support/hooks.rb:75 0.008
Tags: @product @automatic_upgrade
5:30.424
Before features/support/hooks.rb:245 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.080
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.395
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.065
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.633
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.500
When the network is plugged 0.062
And Tor is ready 15.996
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.524
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.062
Given I shutdown Tails and wait for the computer to power off 6.300
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:47.845
Then Tails is running version 2.2~testoverlayfsng 0.098
And all tps features are active 2.379
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.350
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.267
# 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.453
When the network is plugged 0.085
And Tor is ready 15.299
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 0.568
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.506
Given I shutdown Tails and wait for the computer to power off 4.186
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:41.285
Then Tails is running version 2.3~testoverlayfsng 0.097
And all tps features are active 2.027
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.625
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.055
# 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.301
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.317
When the network is plugged 0.053
And Tor is ready 13.984
Then the Upgrader considers the system as up-to-date 0.278
# 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 24.914
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.664
After features/support/hooks.rb:291 0.737
After features/support/hooks.rb:75 0.019
Tags: @product @automatic_upgrade
25.752
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.699
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.493
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.054
And the signing key used by the Upgrader is outdated 0.335
But a current signing key is available on our website 0.000
When the network is plugged 0.044
And Tor is ready 13.581
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.541
After features/support/hooks.rb:291 0.736
After features/support/hooks.rb:75 0.000