Project Number Date
test_Tails_ISO_devel 3892 30 Jun 2025, 14:11

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 26:56.436 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:46.289
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 39.214
When I start Tails from USB drive "old" with network unplugged 2:0.818
Then the boot device has safe access rights 3.568
And Tails is running from USB drive "old" 0.585
And there is no persistence partition on USB drive "old" 0.174
And process "udev-watchdog" is running 0.118
And udev-watchdog is monitoring the correct device 0.333
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:330 6.494
After features/support/hooks.rb:100 0.034
Tags: @product
3:20.204
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.017
Given a computer 0.318
And I start Tails from USB drive "old" with network unplugged and I login 2:13.892
Then Tails is running from USB drive "old" 2.585
And I create a persistent partition 45.594
And I take note of which tps features are available 2.653
Then a Tails persistence partition exists on USB drive "old" 0.798
And I shutdown Tails and wait for the computer to power off 14.361
After features/support/hooks.rb:330 0.368
After features/support/hooks.rb:100 0.022
Tags: @product
4:13.508
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.298
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:17.396
Then Tails is running from USB drive "old" 1.997
And all tps features are active 4.140
When I write some files expected to persist 2.170
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.295
And all persistence configuration files have safe access rights 0.415
And all persistent directories from the old Tails version have safe access rights 3.112
And I take note of which tps features are available 0.671
And I shutdown Tails and wait for the computer to power off 7.719
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 35.290
After features/support/hooks.rb:330 1.856
After features/support/hooks.rb:100 0.382
Tags: @product
3:15.490
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.153
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 15.024
And I log in to a new session 31.457
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.060
And I plug USB drive "to_upgrade" 2.445
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:52.480
Then the running Tails is installed on USB drive "to_upgrade" 31.591
And I unplug USB drive "to_upgrade" 0.196
And I unplug USB drive "__internal" 0.232
After features/support/hooks.rb:330 3.906
After features/support/hooks.rb:100 0.000
Tags: @product
3:8.661
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.027
Given a computer 0.565
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:49.771
Then all tps features from the old Tails version are active 1.985
And Tails is running from USB drive "to_upgrade" 0.432
And the boot device has safe access rights 4.491
And the expected persistent files created with the old Tails version are present in the filesystem 7.176
And all persistent directories from the old Tails version have safe access rights 4.237
After features/support/hooks.rb:330 2.028
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
9:20.579
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.360
And no SquashFS delta is installed 0.420
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.090
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.227
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.477
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.573
When the network is plugged 0.109
And Tor is ready 28.876
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 12.352
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 18.390
Given I shutdown Tails and wait for the computer to power off 9.047
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:59.508
Then Tails is running version 6.2~testoverlayfs 0.063
And all tps features are active 3.310
And the file system changes introduced in version 6.2~testoverlayfs are present 3.554
And only the 6.2~testoverlayfs SquashFS delta is installed 0.566
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.700
# 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 1.461
When the network is plugged 0.200
And Tor is ready 24.908
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 12.149
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.903
Given I shutdown Tails and wait for the computer to power off 9.323
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:48.594
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.586
And the file system changes introduced in version 6.3~testoverlayfs are present 0.606
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.351
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.377
When the network is plugged 0.080
And Tor is ready 30.347
Then the Upgrader considers the system as up-to-date 0.482
# 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 21.333
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.150
After features/support/hooks.rb:330 0.808
After features/support/hooks.rb:100 0.031
Tags: @product @automatic_upgrade
51.701
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.373
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.346
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.123
But a current signing key is available on our website 0.000
When the network is plugged 0.087
And Tor is ready 23.705
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 14.002
After features/support/hooks.rb:330 1.880
After features/support/hooks.rb:100 0.000