Project Number Date
test_Tails_ISO_devel 3636 07 Jan 2025, 13:01

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:7.362 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:37.005
Before features/support/hooks.rb:269 0.006
Given a computer 0.229
And I create a 7200 MiB disk named "old" 0.061
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 32.460
When I start Tails from USB drive "old" with network unplugged 1:58.836
Then the boot device has safe access rights 3.234
And Tails is running from USB drive "old" 0.368
And there is no persistence partition on USB drive "old" 0.085
And process "udev-watchdog" is running 0.111
And udev-watchdog is monitoring the correct device 0.343
And I unplug USB drive "old" 0.212
After features/support/hooks.rb:326 3.546
After features/support/hooks.rb:100 0.099
Tags: @product
2:12.917
Before features/support/hooks.rb:269 0.005
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login 1:29.673
Then Tails is running from USB drive "old" 0.359
And I create a persistent partition 31.620
And I take note of which tps features are available 1.532
Then a Tails persistence partition exists on USB drive "old" 0.846
And I shutdown Tails and wait for the computer to power off 8.687
After features/support/hooks.rb:326 0.161
After features/support/hooks.rb:100 0.008
Tags: @product
2:59.476
Before features/support/hooks.rb:269 0.004
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.987
Then Tails is running from USB drive "old" 1.344
And all tps features are active 2.163
When I write some files expected to persist 1.802
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.285
And all persistence configuration files have safe access rights 0.422
And all persistent directories from the old Tails version have safe access rights 4.430
And I take note of which tps features are available 0.605
And I shutdown Tails and wait for the computer to power off 4.228
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.008
After features/support/hooks.rb:326 0.160
After features/support/hooks.rb:100 0.011
Tags: @product
2:34.730
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 12.628
And I log in to a new session 20.995
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.719
And I plug USB drive "to_upgrade" 2.396
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.546
Then the running Tails is installed on USB drive "to_upgrade" 19.990
And I unplug USB drive "to_upgrade" 0.232
And I unplug USB drive "__internal" 0.220
After features/support/hooks.rb:326 7.154
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.390
Before features/support/hooks.rb:269 0.005
Given a computer 0.199
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.946
Then all tps features from the old Tails version are active 1.749
And Tails is running from USB drive "to_upgrade" 0.349
And the boot device has safe access rights 3.119
And the expected persistent files created with the old Tails version are present in the filesystem 1.403
And all persistent directories from the old Tails version have safe access rights 2.622
After features/support/hooks.rb:326 0.968
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
6:44.571
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 11.806
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.296
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.287
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.476
When the network is plugged 0.148
And Tor is ready 20.232
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 10.351
Given I shutdown Tails and wait for the computer to power off 12.814
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.018
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 3.200
And the file system changes introduced in version 6.2~testoverlayfs are present 0.392
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.331
# 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.292
When the network is plugged 0.076
And Tor is ready 19.368
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.844
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.475
Given I shutdown Tails and wait for the computer to power off 4.292
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.555
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.238
And the file system changes introduced in version 6.3~testoverlayfs are present 0.522
And only the 6.3~testoverlayfs SquashFS delta is installed 0.093
# 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.333
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.321
When the network is plugged 0.067
And Tor is ready 15.229
Then the Upgrader considers the system as up-to-date 10.935
# 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.897
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.978
After features/support/hooks.rb:326 0.778
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
35.271
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 9.986
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.290
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.064
But a current signing key is available on our website 0.000
When the network is plugged 0.110
And Tor is ready 17.589
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.171
After features/support/hooks.rb:326 0.949
After features/support/hooks.rb:100 0.000