Project Number Date
test_Tails_ISO_stable 5603 28 Apr 2025, 18:12

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:38.890 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.404
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.254
And I create a 7200 MiB disk named "old" 0.088
And I plug USB drive "old" 1.088
And I write an old version of the Tails USB image to disk "old" 30.343
When I start Tails from USB drive "old" with network unplugged 1:31.403
Then the boot device has safe access rights 3.189
And Tails is running from USB drive "old" 0.328
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.119
And udev-watchdog is monitoring the correct device 0.299
And I unplug USB drive "old" 0.213
After features/support/hooks.rb:330 3.532
After features/support/hooks.rb:100 0.046
Tags: @product
2:7.624
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login 1:24.010
Then Tails is running from USB drive "old" 0.362
And I create a persistent partition 31.712
And I take note of which tps features are available 2.398
Then a Tails persistence partition exists on USB drive "old" 0.790
And I shutdown Tails and wait for the computer to power off 8.169
After features/support/hooks.rb:330 0.161
After features/support/hooks.rb:100 0.008
Tags: @product
2:58.358
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.943
Then Tails is running from USB drive "old" 0.456
And all tps features are active 2.020
When I write some files expected to persist 2.107
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.219
And all persistence configuration files have safe access rights 0.416
And all persistent directories from the old Tails version have safe access rights 2.414
And I take note of which tps features are available 0.484
And I shutdown Tails and wait for the computer to power off 6.493
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.619
After features/support/hooks.rb:330 0.117
After features/support/hooks.rb:100 0.009
Tags: @product
2:38.727
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 14.018
And I log in to a new session 19.955
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.713
And I plug USB drive "to_upgrade" 2.472
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.333
Then the running Tails is installed on USB drive "to_upgrade" 26.754
And I unplug USB drive "to_upgrade" 0.259
And I unplug USB drive "__internal" 0.221
After features/support/hooks.rb:330 2.233
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.841
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.252
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.564
Then all tps features from the old Tails version are active 1.740
And Tails is running from USB drive "to_upgrade" 0.342
And the boot device has safe access rights 3.745
And the expected persistent files created with the old Tails version are present in the filesystem 1.521
And all persistent directories from the old Tails version have safe access rights 2.674
After features/support/hooks.rb:330 1.315
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
6:51.302
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.013
And no SquashFS delta is installed 0.358
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.556
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.168
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.292
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.526
When the network is plugged 0.079
And Tor is ready 21.414
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.943
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.103
Given I shutdown Tails and wait for the computer to power off 14.879
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.758
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.305
And the file system changes introduced in version 6.2~testoverlayfs are present 0.396
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.349
# 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.357
When the network is plugged 0.212
And Tor is ready 17.209
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.841
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.814
Given I shutdown Tails and wait for the computer to power off 6.340
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.471
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.010
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.087
# 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.324
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.321
When the network is plugged 0.081
And Tor is ready 17.037
Then the Upgrader considers the system as up-to-date 0.314
# 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.451
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.688
After features/support/hooks.rb:330 0.810
After features/support/hooks.rb:100 0.047
Tags: @product @automatic_upgrade
39.631
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.247
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.456
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.127
But a current signing key is available on our website 0.000
When the network is plugged 0.085
And Tor is ready 19.466
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.197
After features/support/hooks.rb:330 1.064
After features/support/hooks.rb:100 0.000