Project Number Date
test_Tails_ISO_stable 5638 09 May 2025, 13:14

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 21:27.747 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:28.489
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.233
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.069
And I write an old version of the Tails USB image to disk "old" 32.696
When I start Tails from USB drive "old" with network unplugged 1:49.402
Then the boot device has safe access rights 3.668
And Tails is running from USB drive "old" 0.535
And there is no persistence partition on USB drive "old" 0.091
And process "udev-watchdog" is running 0.122
And udev-watchdog is monitoring the correct device 0.368
And I unplug USB drive "old" 0.254
After features/support/hooks.rb:330 3.870
After features/support/hooks.rb:100 0.007
Tags: @product
2:26.605
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.229
And I start Tails from USB drive "old" with network unplugged and I login 1:36.385
Then Tails is running from USB drive "old" 0.400
And I create a persistent partition 37.371
And I take note of which tps features are available 2.513
Then a Tails persistence partition exists on USB drive "old" 0.825
And I shutdown Tails and wait for the computer to power off 8.880
After features/support/hooks.rb:330 0.239
After features/support/hooks.rb:100 0.011
Tags: @product
3:10.361
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 2.153
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.708
Then Tails is running from USB drive "old" 0.641
And all tps features are active 2.326
When I write some files expected to persist 2.032
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.257
And all persistence configuration files have safe access rights 0.385
And all persistent directories from the old Tails version have safe access rights 2.937
And I take note of which tps features are available 0.549
And I shutdown Tails and wait for the computer to power off 6.560
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.809
After features/support/hooks.rb:330 0.130
After features/support/hooks.rb:100 0.023
Tags: @product
2:44.487
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.663
And I log in to a new session 20.536
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.011
And I plug USB drive "to_upgrade" 2.458
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.659
Then the running Tails is installed on USB drive "to_upgrade" 28.733
And I unplug USB drive "to_upgrade" 0.217
And I unplug USB drive "__internal" 0.206
After features/support/hooks.rb:330 6.780
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.054
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.221
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.169
Then all tps features from the old Tails version are active 1.762
And Tails is running from USB drive "to_upgrade" 0.388
And the boot device has safe access rights 4.021
And the expected persistent files created with the old Tails version are present in the filesystem 1.609
And all persistent directories from the old Tails version have safe access rights 2.882
After features/support/hooks.rb:330 1.290
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
7:11.124
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 13.992
And no SquashFS delta is installed 0.303
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.544
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.128
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.384
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.543
When the network is plugged 0.106
And Tor is ready 19.512
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.867
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.120
Given I shutdown Tails and wait for the computer to power off 13.080
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.346
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.466
And the file system changes introduced in version 6.2~testoverlayfs are present 0.345
And only the 6.2~testoverlayfs SquashFS delta is installed 0.090
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.313
# 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.392
When the network is plugged 0.082
And Tor is ready 19.958
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.950
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.923
Given I shutdown Tails and wait for the computer to power off 6.834
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.213
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.262
And the file system changes introduced in version 6.3~testoverlayfs are present 0.596
And only the 6.3~testoverlayfs SquashFS delta is installed 0.102
# 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.315
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.383
When the network is plugged 0.076
And Tor is ready 25.097
Then the Upgrader considers the system as up-to-date 0.356
# 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.584
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.815
After features/support/hooks.rb:330 0.649
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
59.625
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.747
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.123
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 47.316
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.668
After features/support/hooks.rb:330 0.772
After features/support/hooks.rb:100 0.000