Project Number Date
test_Tails_ISO_stable 5761 07 Jul 2025, 14:40

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 24:46.694 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:59.489
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.296
And I create a 7200 MiB disk named "old" 0.059
And I plug USB drive "old" 1.111
And I write an old version of the Tails USB image to disk "old" 42.117
When I start Tails from USB drive "old" with network unplugged 2:11.725
Then the boot device has safe access rights 3.166
And Tails is running from USB drive "old" 0.342
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.323
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:330 11.377
After features/support/hooks.rb:100 0.076
Tags: @product
2:51.108
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.045
Given a computer 0.585
And I start Tails from USB drive "old" with network unplugged and I login 1:49.524
Then Tails is running from USB drive "old" 0.408
And I create a persistent partition 48.022
And I take note of which tps features are available 2.720
Then a Tails persistence partition exists on USB drive "old" 1.083
And I shutdown Tails and wait for the computer to power off 8.763
After features/support/hooks.rb:330 0.234
After features/support/hooks.rb:100 0.009
Tags: @product
3:55.348
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:2.153
Then Tails is running from USB drive "old" 1.369
And all tps features are active 4.738
When I write some files expected to persist 3.054
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.478
And all persistence configuration files have safe access rights 0.554
And all persistent directories from the old Tails version have safe access rights 2.692
And I take note of which tps features are available 0.464
And I shutdown Tails and wait for the computer to power off 5.253
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 34.364
After features/support/hooks.rb:330 0.137
After features/support/hooks.rb:100 0.009
Tags: @product
3:12.188
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 without a persistent partition and stopped at Tails Greeter's login screen 13.370
And I log in to a new session 25.596
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.680
And I plug USB drive "to_upgrade" 2.514
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.863
Then the running Tails is installed on USB drive "to_upgrade" 35.330
And I unplug USB drive "to_upgrade" 4.352
And I unplug USB drive "__internal" 0.480
After features/support/hooks.rb:330 3.549
After features/support/hooks.rb:100 0.000
Tags: @product
3:2.345
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.211
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:43.719
Then all tps features from the old Tails version are active 1.683
And Tails is running from USB drive "to_upgrade" 0.365
And the boot device has safe access rights 4.100
And the expected persistent files created with the old Tails version are present in the filesystem 6.975
And all persistent directories from the old Tails version have safe access rights 5.288
After features/support/hooks.rb:330 2.801
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:53.097
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 14.031
And no SquashFS delta is installed 0.169
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.662
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.086
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.403
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.510
When the network is plugged 0.089
And Tor is ready 24.832
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.273
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.702
Given I shutdown Tails and wait for the computer to power off 11.994
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.064
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.475
And the file system changes introduced in version 6.2~testoverlayfs are present 0.401
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.312
# 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.323
When the network is plugged 0.079
And Tor is ready 49.721
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.706
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.847
Given I shutdown Tails and wait for the computer to power off 4.615
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:28.639
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.490
And the file system changes introduced in version 6.3~testoverlayfs are present 0.580
And only the 6.3~testoverlayfs SquashFS delta is installed 0.083
# 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.381
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.467
When the network is plugged 0.093
And Tor is ready 19.161
Then the Upgrader considers the system as up-to-date 0.323
# 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 17.152
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.314
After features/support/hooks.rb:330 0.835
After features/support/hooks.rb:100 0.034
Tags: @product @automatic_upgrade
53.115
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 23.444
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.360
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.082
And the signing key used by the Upgrader is outdated 0.117
But a current signing key is available on our website 0.000
When the network is plugged 0.106
And Tor is ready 21.424
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.578
After features/support/hooks.rb:330 0.947
After features/support/hooks.rb:100 0.000