Project Number Date
test_Tails_ISO_stable 5188 16 Oct 2024, 17:45

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:26.056 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:27.542
Before features/support/hooks.rb:269 0.005
Given a computer 0.172
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 53.031
When I start Tails from USB drive "old" with network unplugged 1:29.139
Then the boot device has safe access rights 3.066
And Tails is running from USB drive "old" 0.334
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.334
And I unplug USB drive "old" 0.207
After features/support/hooks.rb:326 7.252
After features/support/hooks.rb:100 0.009
Tags: @product
2:11.453
Before features/support/hooks.rb:269 0.005
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login 1:29.698
Then Tails is running from USB drive "old" 0.362
And I create a persistent partition 30.149
And I take note of which tps features are available 1.730
Then a Tails persistence partition exists on USB drive "old" 0.924
And I shutdown Tails and wait for the computer to power off 8.374
After features/support/hooks.rb:326 0.214
After features/support/hooks.rb:100 0.008
Tags: @product
2:53.548
Before features/support/hooks.rb:269 0.004
Given a computer 0.173
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.357
Then Tails is running from USB drive "old" 0.426
And all tps features are active 2.047
When I write some files expected to persist 1.997
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.296
And all persistence configuration files have safe access rights 0.449
And all persistent directories from the old Tails version have safe access rights 2.448
And I take note of which tps features are available 1.683
And I shutdown Tails and wait for the computer to power off 6.405
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.261
After features/support/hooks.rb:326 0.127
After features/support/hooks.rb:100 0.008
Tags: @product
2:29.816
Before features/support/hooks.rb:269 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.490
And I log in to a new session 20.837
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.799
And I plug USB drive "to_upgrade" 2.347
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.871
Then the running Tails is installed on USB drive "to_upgrade" 19.051
And I unplug USB drive "to_upgrade" 0.212
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:326 7.059
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.593
Before features/support/hooks.rb:269 0.004
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:18.551
Then all tps features from the old Tails version are active 1.642
And Tails is running from USB drive "to_upgrade" 0.342
And the boot device has safe access rights 3.095
And the expected persistent files created with the old Tails version are present in the filesystem 1.346
And all persistent directories from the old Tails version have safe access rights 2.423
After features/support/hooks.rb:326 0.876
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:25.254
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.431
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.486
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.319
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.457
When the network is plugged 0.149
And Tor is ready 20.426
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.520
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.571
Given I shutdown Tails and wait for the computer to power off 10.624
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.664
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.101
And the file system changes introduced in version 6.2~testoverlayfs are present 0.331
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.347
# 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.503
When the network is plugged 0.074
And Tor is ready 18.847
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.515
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.642
Given I shutdown Tails and wait for the computer to power off 4.266
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.193
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.136
And the file system changes introduced in version 6.3~testoverlayfs are present 0.551
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.328
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.249
When the network is plugged 0.072
And Tor is ready 19.782
Then the Upgrader considers the system as up-to-date 0.322
# 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.994
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.010
After features/support/hooks.rb:326 0.942
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
30.847
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 9.390
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.346
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.726
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 15.133
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.109
After features/support/hooks.rb:326 0.707
After features/support/hooks.rb:100 0.000