Project Number Date
test_Tails_ISO_stable 5371 07 Jan 2025, 13:02

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 20:10.452 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:20.379
Before features/support/hooks.rb:269 0.004
Given a computer 0.191
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 32.897
When I start Tails from USB drive "old" with network unplugged 1:41.355
Then the boot device has safe access rights 3.715
And Tails is running from USB drive "old" 0.327
And there is no persistence partition on USB drive "old" 0.085
And process "udev-watchdog" is running 0.116
And udev-watchdog is monitoring the correct device 0.377
And I unplug USB drive "old" 0.220
After features/support/hooks.rb:326 4.002
After features/support/hooks.rb:100 0.009
Tags: @product
2:16.749
Before features/support/hooks.rb:269 0.006
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login 1:33.817
Then Tails is running from USB drive "old" 0.335
And I create a persistent partition 31.633
And I take note of which tps features are available 1.583
Then a Tails persistence partition exists on USB drive "old" 0.844
And I shutdown Tails and wait for the computer to power off 8.334
After features/support/hooks.rb:326 0.476
After features/support/hooks.rb:100 0.063
Tags: @product
3:1.632
Before features/support/hooks.rb:269 0.074
Given a computer 0.471
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.123
Then Tails is running from USB drive "old" 1.329
And all tps features are active 2.425
When I write some files expected to persist 2.824
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.255
And all persistence configuration files have safe access rights 0.429
And all persistent directories from the old Tails version have safe access rights 2.509
And I take note of which tps features are available 0.502
And I shutdown Tails and wait for the computer to power off 4.479
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.280
After features/support/hooks.rb:326 0.144
After features/support/hooks.rb:100 0.009
Tags: @product
2:37.140
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.758
And I log in to a new session 19.295
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.791
And I plug USB drive "to_upgrade" 2.482
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.188
Then the running Tails is installed on USB drive "to_upgrade" 25.209
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:326 2.007
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.301
Before features/support/hooks.rb:269 0.006
Given a computer 0.204
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.598
Then all tps features from the old Tails version are active 2.110
And Tails is running from USB drive "to_upgrade" 0.377
And the boot device has safe access rights 3.726
And the expected persistent files created with the old Tails version are present in the filesystem 1.664
And all persistent directories from the old Tails version have safe access rights 2.619
After features/support/hooks.rb:326 0.697
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
6:56.345
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.237
And no SquashFS delta is installed 0.188
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.377
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.099
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.392
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.493
When the network is plugged 0.074
And Tor is ready 22.935
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.763
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.764
Given I shutdown Tails and wait for the computer to power off 11.865
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.278
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.245
And the file system changes introduced in version 6.2~testoverlayfs are present 0.314
And only the 6.2~testoverlayfs SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.330
# 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.279
When the network is plugged 0.091
And Tor is ready 20.132
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.099
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.101
Given I shutdown Tails and wait for the computer to power off 5.596
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.228
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.509
And the file system changes introduced in version 6.3~testoverlayfs are present 0.499
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.375
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.376
When the network is plugged 0.111
And Tor is ready 21.078
Then the Upgrader considers the system as up-to-date 0.347
# 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.872
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.089
After features/support/hooks.rb:326 0.694
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
35.904
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.161
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.373
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the signing key used by the Upgrader is outdated 0.077
But a current signing key is available on our website 0.000
When the network is plugged 0.086
And Tor is ready 18.336
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.797
After features/support/hooks.rb:326 0.725
After features/support/hooks.rb:100 0.000