Project Number Date
test_Tails_ISO_devel 4046 31 Oct 2025, 13:50

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 16:32.747 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:55.896
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.214
And I create a 7200 MiB disk named "old" 0.059
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 27.381
When I start Tails from USB drive "old" with network unplugged 1:23.299
Then the boot device has safe access rights 2.941
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.075
And udev-watchdog is monitoring the correct device 0.241
And I unplug USB drive "old" 0.229
After features/support/hooks.rb:331 4.042
After features/support/hooks.rb:100 0.008
Tags: @product
2:3.897
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login 1:24.276
Then Tails is running from USB drive "old" 0.315
And I create a persistent partition 29.459
And I take note of which tps features are available 1.324
Then a Tails persistence partition exists on USB drive "old" 0.648
And I shutdown Tails and wait for the computer to power off 7.672
After features/support/hooks.rb:331 0.619
After features/support/hooks.rb:100 0.008
Tags: @product
2:14.253
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.204
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:39.635
Then Tails is running from USB drive "old" 0.315
And all tps features are active 2.394
When I write some files expected to persist 1.712
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.211
And all persistence configuration files have safe access rights 0.391
And all persistent directories from the old Tails version have safe access rights 2.357
And I take note of which tps features are available 0.582
And I shutdown Tails and wait for the computer to power off 7.898
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.548
After features/support/hooks.rb:331 0.146
After features/support/hooks.rb:100 0.008
Tags: @product
2:27.690
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 without a persistent partition and stopped at Tails Greeter's login screen 10.948
And I log in to a new session 15.377
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.634
And I plug USB drive "to_upgrade" 2.442
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.042
Then the running Tails is installed on USB drive "to_upgrade" 20.830
And I unplug USB drive "to_upgrade" 0.212
And I unplug USB drive "__internal" 0.200
After features/support/hooks.rb:331 3.900
After features/support/hooks.rb:100 0.000
Tags: @product
1:47.316
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.219
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:38.084
Then all tps features from the old Tails version are active 1.934
And Tails is running from USB drive "to_upgrade" 0.297
And the boot device has safe access rights 3.086
And the expected persistent files created with the old Tails version are present in the filesystem 1.369
And all persistent directories from the old Tails version have safe access rights 2.324
After features/support/hooks.rb:331 1.044
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
5:33.515
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 12.877
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.295
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.238
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.506
When the network is plugged 0.063
And Tor is ready 43.239
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.607
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.217
Given I shutdown Tails and wait for the computer to power off 11.591
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:43.080
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.328
And the file system changes introduced in version 6.2~testoverlayfs are present 0.261
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.208
# 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.225
When the network is plugged 0.066
And Tor is ready 11.130
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.876
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.543
Given I shutdown Tails and wait for the computer to power off 8.136
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:40.812
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.441
And the file system changes introduced in version 6.3~testoverlayfs are present 0.475
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.129
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.205
When the network is plugged 0.075
And Tor is ready 10.937
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 5.860
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.505
After features/support/hooks.rb:331 1.390
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
30.176
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 13.822
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.329
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.086
And Tor is ready 15.192
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.634
After features/support/hooks.rb:331 0.681
After features/support/hooks.rb:100 0.000