Project Number Date
test_Tails_ISO_devel 4080 20 Nov 2025, 14:43

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 18:0.611 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:59.301
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.235
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.079
And I write an old version of the Tails USB image to disk "old" 33.758
When I start Tails from USB drive "old" with network unplugged 1:19.832
Then the boot device has safe access rights 3.192
And Tails is running from USB drive "old" 0.548
And there is no persistence partition on USB drive "old" 0.108
And process "udev-watchdog" is running 0.063
And udev-watchdog is monitoring the correct device 0.240
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:331 4.081
After features/support/hooks.rb:100 0.009
Tags: @product
2:10.294
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login 1:30.886
Then Tails is running from USB drive "old" 0.338
And I create a persistent partition 29.137
And I take note of which tps features are available 1.217
Then a Tails persistence partition exists on USB drive "old" 0.745
And I shutdown Tails and wait for the computer to power off 7.761
After features/support/hooks.rb:331 0.262
After features/support/hooks.rb:100 0.008
Tags: @product
2:37.948
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.246
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:38.435
Then Tails is running from USB drive "old" 0.767
And all tps features are active 13.544
When I write some files expected to persist 1.580
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.204
And all persistence configuration files have safe access rights 0.374
And all persistent directories from the old Tails version have safe access rights 2.258
And I take note of which tps features are available 6.238
And I shutdown Tails and wait for the computer to power off 9.709
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.587
After features/support/hooks.rb:331 0.582
After features/support/hooks.rb:100 0.008
Tags: @product
3:7.079
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 37.035
And I log in to a new session 18.452
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.256
And I plug USB drive "to_upgrade" 2.702
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.032
Then the running Tails is installed on USB drive "to_upgrade" 22.134
And I unplug USB drive "to_upgrade" 0.233
And I unplug USB drive "__internal" 0.231
After features/support/hooks.rb:331 4.013
After features/support/hooks.rb:100 0.000
Tags: @product
1:46.055
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.179
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:37.271
Then all tps features from the old Tails version are active 1.553
And Tails is running from USB drive "to_upgrade" 0.290
And the boot device has safe access rights 3.130
And the expected persistent files created with the old Tails version are present in the filesystem 1.396
And all persistent directories from the old Tails version have safe access rights 2.233
After features/support/hooks.rb:331 0.856
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
5:55.720
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 17.862
And no SquashFS delta is installed 0.106
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.278
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.281
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.406
When the network is plugged 0.050
And Tor is ready 14.489
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.599
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.479
Given I shutdown Tails and wait for the computer to power off 16.394
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:43.605
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.447
And the file system changes introduced in version 6.2~testoverlayfs are present 0.303
And only the 6.2~testoverlayfs SquashFS delta is installed 0.058
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.157
# 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.212
When the network is plugged 0.051
And Tor is ready 41.387
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.310
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.575
Given I shutdown Tails and wait for the computer to power off 9.639
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:40.088
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.212
And the file system changes introduced in version 6.3~testoverlayfs are present 0.492
And only the 6.3~testoverlayfs SquashFS delta is installed 0.053
# 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.160
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.210
When the network is plugged 0.747
And Tor is ready 14.337
Then the Upgrader considers the system as up-to-date 0.387
# 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.699
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.556
After features/support/hooks.rb:331 1.118
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
24.211
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.369
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.280
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.057
But a current signing key is available on our website 0.000
When the network is plugged 1.407
And Tor is ready 10.371
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.677
After features/support/hooks.rb:331 0.650
After features/support/hooks.rb:100 0.000