Project Number Date
test_Tails_ISO_devel 4099 03 Dec 2025, 18:38

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 15:10.217 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:52.593
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.326
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 28.867
When I start Tails from USB drive "old" with network unplugged 1:18.470
Then the boot device has safe access rights 2.903
And Tails is running from USB drive "old" 0.359
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.269
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:331 3.855
After features/support/hooks.rb:100 0.010
Tags: @product
2:11.305
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.336
And I start Tails from USB drive "old" with network unplugged and I login 1:28.513
Then Tails is running from USB drive "old" 0.678
And I create a persistent partition 31.299
And I take note of which tps features are available 1.597
Then a Tails persistence partition exists on USB drive "old" 0.864
And I shutdown Tails and wait for the computer to power off 8.016
After features/support/hooks.rb:331 0.686
After features/support/hooks.rb:100 0.011
Tags: @product
2:14.706
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:39.673
Then Tails is running from USB drive "old" 0.740
And all tps features are active 1.723
When I write some files expected to persist 1.657
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.247
And all persistence configuration files have safe access rights 0.422
And all persistent directories from the old Tails version have safe access rights 2.366
And I take note of which tps features are available 0.474
And I shutdown Tails and wait for the computer to power off 8.027
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.163
After features/support/hooks.rb:331 0.365
After features/support/hooks.rb:100 0.013
Tags: @product
2:32.081
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.881
And I log in to a new session 12.345
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.130
And I plug USB drive "to_upgrade" 3.644
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.543
Then the running Tails is installed on USB drive "to_upgrade" 20.664
And I unplug USB drive "to_upgrade" 0.672
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:331 3.787
After features/support/hooks.rb:100 0.000
Tags: @product
1:27.739
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.173
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:17.455
Then all tps features from the old Tails version are active 2.037
And Tails is running from USB drive "to_upgrade" 0.306
And the boot device has safe access rights 3.504
And the expected persistent files created with the old Tails version are present in the filesystem 1.587
And all persistent directories from the old Tails version have safe access rights 2.673
After features/support/hooks.rb:331 0.672
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
4:27.659
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 9.786
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.261
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.322
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.600
When the network is plugged 0.063
And Tor is ready 12.652
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.055
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.769
Given I shutdown Tails and wait for the computer to power off 7.975
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.076
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.093
And the file system changes introduced in version 6.2~testoverlayfs are present 0.284
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.176
# 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.245
When the network is plugged 0.051
And Tor is ready 13.766
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.763
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.208
Given I shutdown Tails and wait for the computer to power off 8.023
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.468
Then Tails is running version 6.3~testoverlayfs 0.034
And all tps features are active 2.793
And the file system changes introduced in version 6.3~testoverlayfs are present 0.520
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.194
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.366
When the network is plugged 0.053
And Tor is ready 12.949
Then the Upgrader considers the system as up-to-date 10.725
# 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.466
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.635
After features/support/hooks.rb:331 1.194
After features/support/hooks.rb:100 0.217
Tags: @product @automatic_upgrade
24.131
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.054
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.891
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.222
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.071
But a current signing key is available on our website 0.000
When the network is plugged 0.065
And Tor is ready 10.817
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.011
After features/support/hooks.rb:331 1.049
After features/support/hooks.rb:100 0.000