Project Number Date
test_Tails_ISO_stable 5363 01 Jan 2025, 12:18

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:57.505 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:8.991
Before features/support/hooks.rb:269 0.005
Given a computer 0.187
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" 34.598
When I start Tails from USB drive "old" with network unplugged 1:28.693
Then the boot device has safe access rights 3.383
And Tails is running from USB drive "old" 0.342
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.290
And I unplug USB drive "old" 0.243
After features/support/hooks.rb:326 3.767
After features/support/hooks.rb:100 0.010
Tags: @product
2:9.660
Before features/support/hooks.rb:269 0.020
Given a computer 0.219
And I start Tails from USB drive "old" with network unplugged and I login 1:25.839
Then Tails is running from USB drive "old" 0.306
And I create a persistent partition 32.338
And I take note of which tps features are available 1.914
Then a Tails persistence partition exists on USB drive "old" 0.764
And I shutdown Tails and wait for the computer to power off 8.277
After features/support/hooks.rb:326 0.178
After features/support/hooks.rb:100 0.007
Tags: @product
2:44.153
Before features/support/hooks.rb:269 0.005
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:6.942
Then Tails is running from USB drive "old" 1.207
And all tps features are active 1.964
When I write some files expected to persist 1.670
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.222
And all persistence configuration files have safe access rights 0.396
And all persistent directories from the old Tails version have safe access rights 2.544
And I take note of which tps features are available 0.486
And I shutdown Tails and wait for the computer to power off 4.202
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.324
After features/support/hooks.rb:326 0.110
After features/support/hooks.rb:100 0.009
Tags: @product
2:28.663
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.068
And I log in to a new session 18.495
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.909
And I plug USB drive "to_upgrade" 2.402
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.238
Then the running Tails is installed on USB drive "to_upgrade" 21.146
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:326 6.693
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.794
Before features/support/hooks.rb:269 0.005
Given a computer 0.244
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.257
Then all tps features from the old Tails version are active 1.665
And Tails is running from USB drive "to_upgrade" 0.402
And the boot device has safe access rights 3.078
And the expected persistent files created with the old Tails version are present in the filesystem 1.469
And all persistent directories from the old Tails version have safe access rights 2.676
After features/support/hooks.rb:326 0.611
After features/support/hooks.rb:100 0.038
Tags: @product @automatic_upgrade
6:23.822
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.862
And no SquashFS delta is installed 0.203
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.344
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.126
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.262
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.418
When the network is plugged 0.078
And Tor is ready 22.975
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.296
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.124
Given I shutdown Tails and wait for the computer to power off 10.329
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.322
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.144
And the file system changes introduced in version 6.2~testoverlayfs are present 0.301
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.324
# 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.300
When the network is plugged 0.075
And Tor is ready 16.196
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.629
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.440
Given I shutdown Tails and wait for the computer to power off 4.308
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.254
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.086
And the file system changes introduced in version 6.3~testoverlayfs are present 0.453
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.307
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.528
When the network is plugged 0.062
And Tor is ready 21.920
Then the Upgrader considers the system as up-to-date 0.310
# 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.538
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.132
After features/support/hooks.rb:326 0.839
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
36.419
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.942
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.332
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.072
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 19.517
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.417
After features/support/hooks.rb:326 0.630
After features/support/hooks.rb:100 0.000