Project Number Date
test_Tails_ISO_stable 5760 06 Jul 2025, 13:09

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:28.389 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:5.333
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.172
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 32.584
When I start Tails from USB drive "old" with network unplugged 1:27.220
Then the boot device has safe access rights 3.215
And Tails is running from USB drive "old" 0.338
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.117
And udev-watchdog is monitoring the correct device 0.298
And I unplug USB drive "old" 0.227
After features/support/hooks.rb:330 3.740
After features/support/hooks.rb:100 0.009
Tags: @product
2:14.776
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login 1:29.318
Then Tails is running from USB drive "old" 0.297
And I create a persistent partition 34.454
And I take note of which tps features are available 1.466
Then a Tails persistence partition exists on USB drive "old" 0.696
And I shutdown Tails and wait for the computer to power off 8.362
After features/support/hooks.rb:330 0.122
After features/support/hooks.rb:100 0.010
Tags: @product
2:57.820
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.270
Then Tails is running from USB drive "old" 0.432
And all tps features are active 2.034
When I write some files expected to persist 1.732
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.200
And all persistence configuration files have safe access rights 0.530
And all persistent directories from the old Tails version have safe access rights 2.458
And I take note of which tps features are available 0.412
And I shutdown Tails and wait for the computer to power off 6.657
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.876
After features/support/hooks.rb:330 0.111
After features/support/hooks.rb:100 0.010
Tags: @product
2:33.541
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 9.936
And I log in to a new session 18.944
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.690
And I plug USB drive "to_upgrade" 2.404
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.845
Then the running Tails is installed on USB drive "to_upgrade" 25.292
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.220
After features/support/hooks.rb:330 2.240
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.858
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.181
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.159
Then all tps features from the old Tails version are active 1.613
And Tails is running from USB drive "to_upgrade" 0.322
And the boot device has safe access rights 3.322
And the expected persistent files created with the old Tails version are present in the filesystem 1.594
And all persistent directories from the old Tails version have safe access rights 2.663
After features/support/hooks.rb:330 1.369
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:48.615
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 12.150
And no SquashFS delta is installed 0.131
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.584
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.313
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.432
When the network is plugged 0.072
And Tor is ready 19.427
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.337
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.960
Given I shutdown Tails and wait for the computer to power off 9.089
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.196
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.394
And the file system changes introduced in version 6.2~testoverlayfs are present 0.321
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.295
# 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.298
When the network is plugged 0.075
And Tor is ready 17.904
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.343
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.424
Given I shutdown Tails and wait for the computer to power off 6.421
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.665
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.026
And the file system changes introduced in version 6.3~testoverlayfs are present 0.445
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.402
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.341
When the network is plugged 0.094
And Tor is ready 18.976
Then the Upgrader considers the system as up-to-date 0.308
# 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.308
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.647
After features/support/hooks.rb:330 0.682
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
35.443
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 10.374
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.401
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.095
And the signing key used by the Upgrader is outdated 0.134
But a current signing key is available on our website 0.000
When the network is plugged 0.107
And Tor is ready 15.877
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.452
After features/support/hooks.rb:330 1.020
After features/support/hooks.rb:100 0.000