Project Number Date
test_Tails_ISO_stable 5220 24 Oct 2024, 19:57

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 18:36.818 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:7.732
Before features/support/hooks.rb:269 0.005
Given a computer 0.173
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 31.089
When I start Tails from USB drive "old" with network unplugged 1:31.461
Then the boot device has safe access rights 2.957
And Tails is running from USB drive "old" 0.315
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.321
And I unplug USB drive "old" 0.173
After features/support/hooks.rb:326 3.820
After features/support/hooks.rb:100 0.009
Tags: @product
2:2.539
Before features/support/hooks.rb:269 0.006
Given a computer 0.171
And I start Tails from USB drive "old" with network unplugged and I login 1:20.424
Then Tails is running from USB drive "old" 0.305
And I create a persistent partition 31.362
And I take note of which tps features are available 1.375
Then a Tails persistence partition exists on USB drive "old" 0.774
And I shutdown Tails and wait for the computer to power off 8.124
After features/support/hooks.rb:326 0.212
After features/support/hooks.rb:100 0.009
Tags: @product
2:48.612
Before features/support/hooks.rb:269 0.005
Given a computer 0.173
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.322
Then Tails is running from USB drive "old" 0.291
And all tps features are active 1.856
When I write some files expected to persist 1.653
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.218
And all persistence configuration files have safe access rights 0.369
And all persistent directories from the old Tails version have safe access rights 2.257
And I take note of which tps features are available 0.389
And I shutdown Tails and wait for the computer to power off 4.177
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.901
After features/support/hooks.rb:326 0.114
After features/support/hooks.rb:100 0.009
Tags: @product
2:31.790
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.932
And I log in to a new session 20.342
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.106
And I plug USB drive "to_upgrade" 2.384
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.245
Then the running Tails is installed on USB drive "to_upgrade" 21.328
And I unplug USB drive "to_upgrade" 0.234
And I unplug USB drive "__internal" 0.216
After features/support/hooks.rb:326 2.270
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.134
Before features/support/hooks.rb:269 0.006
Given a computer 0.172
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.217
Then all tps features from the old Tails version are active 1.575
And Tails is running from USB drive "to_upgrade" 0.305
And the boot device has safe access rights 3.260
And the expected persistent files created with the old Tails version are present in the filesystem 1.343
And all persistent directories from the old Tails version have safe access rights 2.259
After features/support/hooks.rb:326 0.741
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:18.268
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 12.170
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.064
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.360
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.458
When the network is plugged 0.074
And Tor is ready 25.944
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.422
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.875
Given I shutdown Tails and wait for the computer to power off 10.411
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.186
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.032
And the file system changes introduced in version 6.2~testoverlayfs are present 0.326
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.420
# 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.396
When the network is plugged 0.078
And Tor is ready 18.324
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.267
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.405
Given I shutdown Tails and wait for the computer to power off 4.300
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.577
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.091
And the file system changes introduced in version 6.3~testoverlayfs are present 0.479
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.331
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.307
When the network is plugged 0.065
And Tor is ready 19.966
Then the Upgrader considers the system as up-to-date 0.317
# 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 14.483
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.796
After features/support/hooks.rb:326 0.686
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
36.741
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 10.799
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.001
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.788
But a current signing key is available on our website 0.000
When the network is plugged 0.063
And Tor is ready 17.732
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.306
After features/support/hooks.rb:326 0.651
After features/support/hooks.rb:100 0.000