Project Number Date
test_Tails_ISO_stable 6002 11 Dec 2025, 13:53

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 14:2.015 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
1:44.476
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.155
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 27.837
When I start Tails from USB drive "old" with network unplugged 1:11.489
Then the boot device has safe access rights 3.072
And Tails is running from USB drive "old" 0.321
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.220
And I unplug USB drive "old" 0.170
After features/support/hooks.rb:331 3.952
After features/support/hooks.rb:100 0.054
Tags: @product
1:59.054
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.173
And I start Tails from USB drive "old" with network unplugged and I login 1:22.685
Then Tails is running from USB drive "old" 0.319
And I create a persistent partition 26.350
And I take note of which tps features are available 1.245
Then a Tails persistence partition exists on USB drive "old" 0.720
And I shutdown Tails and wait for the computer to power off 7.559
After features/support/hooks.rb:331 0.525
After features/support/hooks.rb:100 0.009
Tags: @product
2:7.556
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:34.087
Then Tails is running from USB drive "old" 0.299
And all tps features are active 1.890
When I write some files expected to persist 1.457
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.187
And all persistence configuration files have safe access rights 0.388
And all persistent directories from the old Tails version have safe access rights 2.665
And I take note of which tps features are available 0.483
And I shutdown Tails and wait for the computer to power off 7.782
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.104
After features/support/hooks.rb:331 0.415
After features/support/hooks.rb:100 0.011
Tags: @product
2:22.128
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 without a persistent partition and stopped at Tails Greeter's login screen 9.971
And I log in to a new session 10.096
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.879
And I plug USB drive "to_upgrade" 2.966
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.057
Then the running Tails is installed on USB drive "to_upgrade" 19.736
And I unplug USB drive "to_upgrade" 0.190
And I unplug USB drive "__internal" 0.228
After features/support/hooks.rb:331 3.640
After features/support/hooks.rb:100 0.000
Tags: @product
1:24.190
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.169
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:13.717
Then all tps features from the old Tails version are active 1.990
And Tails is running from USB drive "to_upgrade" 0.293
And the boot device has safe access rights 3.346
And the expected persistent files created with the old Tails version are present in the filesystem 1.693
And all persistent directories from the old Tails version have safe access rights 2.980
After features/support/hooks.rb:331 0.746
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:3.558
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.837
And no SquashFS delta is installed 0.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.247
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.276
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.455
When the network is plugged 0.055
And Tor is ready 12.933
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.845
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.478
Given I shutdown Tails and wait for the computer to power off 7.647
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.460
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.011
And the file system changes introduced in version 6.2~testoverlayfs are present 0.313
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.167
# 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.239
When the network is plugged 0.056
And Tor is ready 12.676
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.617
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.934
Given I shutdown Tails and wait for the computer to power off 7.866
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.209
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.510
And the file system changes introduced in version 6.3~testoverlayfs are present 0.435
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.156
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.278
When the network is plugged 0.054
And Tor is ready 13.075
Then the Upgrader considers the system as up-to-date 0.199
# 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 6.595
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.648
After features/support/hooks.rb:331 1.053
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
21.051
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 9.570
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.226
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the signing key used by the Upgrader is outdated 0.067
But a current signing key is available on our website 0.000
When the network is plugged 0.048
And Tor is ready 10.428
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.633
After features/support/hooks.rb:331 0.943
After features/support/hooks.rb:100 0.000