Project Number Date
test_Tails_ISO_stable 4905 19 Jun 2024, 12:43

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 19:3.207 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
2:16.538
Before features/support/hooks.rb:269 0.006
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 33.036
When I start Tails from USB drive "old" with network unplugged 1:37.996
Then the boot device has safe access rights 3.232
And Tails is running from USB drive "old" 0.337
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.307
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:326 6.876
After features/support/hooks.rb:100 0.008
Tags: @product
2:11.946
Before features/support/hooks.rb:269 0.004
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login 1:29.990
Then Tails is running from USB drive "old" 0.319
And I create a persistent partition 30.677
And I take note of which tps features are available 1.511
Then a Tails persistence partition exists on USB drive "old" 0.859
And I shutdown Tails and wait for the computer to power off 8.389
After features/support/hooks.rb:326 0.187
After features/support/hooks.rb:100 0.007
Tags: @product
2:49.426
Before features/support/hooks.rb:269 0.004
Given a computer 0.228
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.855
Then Tails is running from USB drive "old" 0.329
And all tps features are active 1.871
When I write some files expected to persist 1.735
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.380
And all persistent directories from the old Tails version have safe access rights 2.467
And I take note of which tps features are available 0.424
And I shutdown Tails and wait for the computer to power off 4.427
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.482
After features/support/hooks.rb:326 0.130
After features/support/hooks.rb:100 0.008
Tags: @product
2:26.056
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.626
And I log in to a new session 18.177
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.348
And I plug USB drive "to_upgrade" 2.393
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.105
Then the running Tails is installed on USB drive "to_upgrade" 19.006
And I unplug USB drive "to_upgrade" 0.196
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:326 2.836
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.539
Before features/support/hooks.rb:269 0.005
Given a computer 0.199
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.037
Then all tps features from the old Tails version are active 1.506
And Tails is running from USB drive "to_upgrade" 0.286
And the boot device has safe access rights 2.817
And the expected persistent files created with the old Tails version are present in the filesystem 1.412
And all persistent directories from the old Tails version have safe access rights 2.278
After features/support/hooks.rb:326 0.983
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:26.162
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 17.578
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.487
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.317
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.479
When the network is plugged 0.052
And Tor is ready 19.888
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.182
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.864
Given I shutdown Tails and wait for the computer to power off 10.900
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.483
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.261
And the file system changes introduced in version 6.2~testoverlayfs are present 0.311
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.328
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.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 6.1~testoverlayfs was initially installed 0.276
When the network is plugged 0.040
And Tor is ready 18.959
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.474
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.386
Given I shutdown Tails and wait for the computer to power off 4.347
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.592
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.965
And the file system changes introduced in version 6.3~testoverlayfs are present 0.461
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.391
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.235
When the network is plugged 0.057
And Tor is ready 18.517
Then the Upgrader considers the system as up-to-date 0.320
# 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 13.615
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.062
After features/support/hooks.rb:326 0.864
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
36.536
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.843
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.476
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.080
And the signing key used by the Upgrader is outdated 0.904
But a current signing key is available on our website 0.000
When the network is plugged 0.506
And Tor is ready 18.745
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.978
After features/support/hooks.rb:326 0.961
After features/support/hooks.rb:100 0.000