Project Number Date
test_Tails_ISO_stable 5196 18 Oct 2024, 08:49

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 21:37.639 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:32.031
Before features/support/hooks.rb:269 0.007
Given a computer 0.206
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 35.221
When I start Tails from USB drive "old" with network unplugged 1:50.717
Then the boot device has safe access rights 3.491
And Tails is running from USB drive "old" 0.494
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.411
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:326 7.528
After features/support/hooks.rb:100 0.008
Tags: @product
2:17.648
Before features/support/hooks.rb:269 0.005
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login 1:31.293
Then Tails is running from USB drive "old" 0.393
And I create a persistent partition 34.409
And I take note of which tps features are available 1.886
Then a Tails persistence partition exists on USB drive "old" 0.923
And I shutdown Tails and wait for the computer to power off 8.544
After features/support/hooks.rb:326 0.184
After features/support/hooks.rb:100 0.010
Tags: @product
3:14.621
Before features/support/hooks.rb:269 0.006
Given a computer 0.233
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:36.177
Then Tails is running from USB drive "old" 0.388
And all tps features are active 2.285
When I write some files expected to persist 2.018
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.451
And all persistence configuration files have safe access rights 0.402
And all persistent directories from the old Tails version have safe access rights 2.696
And I take note of which tps features are available 0.507
And I shutdown Tails and wait for the computer to power off 4.450
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.008
After features/support/hooks.rb:326 0.104
After features/support/hooks.rb:100 0.010
Tags: @product
2:45.351
Before features/support/hooks.rb:269 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 16.891
And I log in to a new session 21.297
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.748
And I plug USB drive "to_upgrade" 2.422
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.570
Then the running Tails is installed on USB drive "to_upgrade" 21.003
And I unplug USB drive "to_upgrade" 0.214
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:326 7.491
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.735
Before features/support/hooks.rb:269 0.006
Given a computer 0.266
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.467
Then all tps features from the old Tails version are active 1.873
And Tails is running from USB drive "to_upgrade" 0.334
And the boot device has safe access rights 3.445
And the expected persistent files created with the old Tails version are present in the filesystem 1.582
And all persistent directories from the old Tails version have safe access rights 2.764
After features/support/hooks.rb:326 1.162
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:36.525
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 17.805
And no SquashFS delta is installed 0.160
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.425
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.298
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.498
When the network is plugged 0.063
And Tor is ready 51.539
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.681
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.218
Given I shutdown Tails and wait for the computer to power off 11.182
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.894
Then Tails is running version 6.2~testoverlayfs 0.077
And all tps features are active 2.668
And the file system changes introduced in version 6.2~testoverlayfs are present 0.306
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# 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_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.355
When the network is plugged 0.087
And Tor is ready 22.259
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.411
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.826
Given I shutdown Tails and wait for the computer to power off 6.581
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:20.892
Then Tails is running version 6.3~testoverlayfs 0.023
And all tps features are active 2.668
And the file system changes introduced in version 6.3~testoverlayfs are present 0.645
And only the 6.3~testoverlayfs SquashFS delta is installed 0.095
# 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.457
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.584
When the network is plugged 0.072
And Tor is ready 20.021
Then the Upgrader considers the system as up-to-date 0.355
# 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 16.803
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.101
After features/support/hooks.rb:326 1.031
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
43.724
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 11.720
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.554
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 1.788
But a current signing key is available on our website 0.000
When the network is plugged 0.285
And Tor is ready 21.121
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.192
After features/support/hooks.rb:326 1.350
After features/support/hooks.rb:100 0.000