Project Number Date
test_Tails_ISO_stable 4614 11 Jan 2024, 12:31

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:40.398 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.404
Before features/support/hooks.rb:245 0.008
Given a computer 0.198
And I create a 7200 MiB disk named "old" 0.057
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 19.858
When I start Tails from USB drive "old" with network unplugged 1:8.520
Then the boot device has safe access rights 2.835
And Tails is running from USB drive "old" 0.301
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.251
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:291 3.514
After features/support/hooks.rb:75 0.009
Tags: @product
1:59.992
Before features/support/hooks.rb:245 0.004
Given a computer 0.171
And I start Tails from USB drive "old" with network unplugged and I login 1:4.602
Then Tails is running from USB drive "old" 0.605
And I create a persistent partition 43.994
And I take note of which tps features are available 1.521
Then a Tails persistence partition exists on USB drive "old" 0.976
And I shutdown Tails and wait for the computer to power off 8.120
After features/support/hooks.rb:291 0.180
After features/support/hooks.rb:75 0.012
Tags: @product
2:14.276
Before features/support/hooks.rb:245 0.005
Given a computer 0.215
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:46.762
Then Tails is running from USB drive "old" 0.368
And all tps features are active 2.052
When I write some files expected to persist 1.940
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.235
And all persistence configuration files have safe access rights 0.612
And all persistent directories from the old Tails version have safe access rights 2.724
And I take note of which tps features are available 0.422
And I shutdown Tails and wait for the computer to power off 3.084
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.856
After features/support/hooks.rb:291 0.129
After features/support/hooks.rb:75 0.010
Tags: @product
2:30.924
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 9.867
And I log in to a new session 14.622
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.107
And I plug USB drive "to_upgrade" 2.440
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:50.162
Then the running Tails is installed on USB drive "to_upgrade" 12.350
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.178
After features/support/hooks.rb:291 1.736
After features/support/hooks.rb:75 0.000
Tags: @product
1:59.047
Before features/support/hooks.rb:245 0.006
Given a computer 0.176
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:49.379
Then all tps features from the old Tails version are active 1.691
And Tails is running from USB drive "to_upgrade" 0.310
And the boot device has safe access rights 3.375
And the expected persistent files created with the old Tails version are present in the filesystem 1.640
And all persistent directories from the old Tails version have safe access rights 2.473
After features/support/hooks.rb:291 0.607
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
5:53.884
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.009
And no SquashFS delta is installed 0.107
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.301
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.057
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.380
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.622
When the network is plugged 0.036
And Tor is ready 16.639
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.606
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.699
Given I shutdown Tails and wait for the computer to power off 6.593
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.064
Then Tails is running version 2.2~testoverlayfsng 0.118
And all tps features are active 2.417
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.386
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.307
# 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.280
When the network is plugged 0.056
And Tor is ready 17.429
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.585
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.721
Given I shutdown Tails and wait for the computer to power off 4.236
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:45.963
Then Tails is running version 2.3~testoverlayfsng 0.112
And all tps features are active 2.120
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.609
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.071
# 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.282
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.345
When the network is plugged 0.051
And Tor is ready 15.055
Then the Upgrader considers the system as up-to-date 10.787
# 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.262
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.478
After features/support/hooks.rb:291 0.797
After features/support/hooks.rb:75 0.025
Tags: @product @automatic_upgrade
28.868
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 8.983
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.284
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.051
And the signing key used by the Upgrader is outdated 0.612
But a current signing key is available on our website 0.000
When the network is plugged 0.047
And Tor is ready 16.295
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.593
After features/support/hooks.rb:291 0.729
After features/support/hooks.rb:75 0.000