Project Number Date
test_Tails_ISO_stable 5918 29 Oct 2025, 20:55

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 17:35.529 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:24.771
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.160
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 33.838
When I start Tails from USB drive "old" with network unplugged 1:45.850
Then the boot device has safe access rights 2.805
And Tails is running from USB drive "old" 0.351
And there is no persistence partition on USB drive "old" 0.114
And process "udev-watchdog" is running 0.077
And udev-watchdog is monitoring the correct device 0.266
And I unplug USB drive "old" 0.218
After features/support/hooks.rb:331 3.730
After features/support/hooks.rb:100 0.011
Tags: @product
2:3.917
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.259
And I start Tails from USB drive "old" with network unplugged and I login 1:26.800
Then Tails is running from USB drive "old" 0.708
And I create a persistent partition 29.291
And I take note of which tps features are available 1.208
Then a Tails persistence partition exists on USB drive "old" 0.731
And I shutdown Tails and wait for the computer to power off 4.918
After features/support/hooks.rb:331 0.640
After features/support/hooks.rb:100 0.010
Tags: @product
2:10.808
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:36.537
Then Tails is running from USB drive "old" 0.337
And all tps features are active 2.007
When I write some files expected to persist 1.963
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.238
And all persistence configuration files have safe access rights 0.437
And all persistent directories from the old Tails version have safe access rights 2.403
And I take note of which tps features are available 0.574
And I shutdown Tails and wait for the computer to power off 7.726
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.382
After features/support/hooks.rb:331 0.258
After features/support/hooks.rb:100 0.012
Tags: @product
2:56.133
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.358
And I log in to a new session 18.559
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.928
And I plug USB drive "to_upgrade" 2.535
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:57.120
Then the running Tails is installed on USB drive "to_upgrade" 22.073
And I unplug USB drive "to_upgrade" 0.250
And I unplug USB drive "__internal" 0.309
After features/support/hooks.rb:331 3.980
After features/support/hooks.rb:100 0.000
Tags: @product
1:48.372
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.228
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:38.805
Then all tps features from the old Tails version are active 1.539
And Tails is running from USB drive "to_upgrade" 0.346
And the boot device has safe access rights 2.985
And the expected persistent files created with the old Tails version are present in the filesystem 2.057
And all persistent directories from the old Tails version have safe access rights 2.410
After features/support/hooks.rb:331 1.051
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
5:8.424
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 12.844
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.297
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.340
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.491
When the network is plugged 0.067
And Tor is ready 13.981
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.715
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.484
Given I shutdown Tails and wait for the computer to power off 11.516
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:46.686
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.838
And the file system changes introduced in version 6.2~testoverlayfs are present 0.338
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.216
# 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.277
When the network is plugged 0.076
And Tor is ready 11.978
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.804
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.600
Given I shutdown Tails and wait for the computer to power off 4.862
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:39.857
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.525
And the file system changes introduced in version 6.3~testoverlayfs are present 0.476
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.157
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.284
When the network is plugged 0.068
And Tor is ready 12.443
Then the Upgrader considers the system as up-to-date 0.214
# 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 5.237
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.416
After features/support/hooks.rb:331 0.804
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
1:3.101
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 11.299
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.463
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
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.085
And Tor is ready 50.514
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.615
After features/support/hooks.rb:331 1.035
After features/support/hooks.rb:100 0.000