Project Number Date
test_Tails_ISO_devel 4107 08 Dec 2025, 08:58

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:4.783 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:0.467
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.227
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 28.112
When I start Tails from USB drive "old" with network unplugged 1:26.281
Then the boot device has safe access rights 3.739
And Tails is running from USB drive "old" 0.317
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.063
And udev-watchdog is monitoring the correct device 0.303
And I unplug USB drive "old" 0.256
After features/support/hooks.rb:331 4.978
After features/support/hooks.rb:100 0.010
Tags: @product
2:15.331
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 1.058
And I start Tails from USB drive "old" with network unplugged and I login 1:29.318
Then Tails is running from USB drive "old" 0.301
And I create a persistent partition 34.535
And I take note of which tps features are available 2.014
Then a Tails persistence partition exists on USB drive "old" 0.979
And I shutdown Tails and wait for the computer to power off 7.122
After features/support/hooks.rb:331 0.370
After features/support/hooks.rb:100 0.017
Tags: @product
2:14.677
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:40.007
Then Tails is running from USB drive "old" 0.646
And all tps features are active 1.803
When I write some files expected to persist 1.490
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
And all persistence configuration files have safe access rights 0.383
And all persistent directories from the old Tails version have safe access rights 2.424
And I take note of which tps features are available 0.445
And I shutdown Tails and wait for the computer to power off 7.772
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.283
After features/support/hooks.rb:331 0.285
After features/support/hooks.rb:100 0.011
Tags: @product
2:31.962
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 10.598
And I log in to a new session 12.075
And I clone USB drive "old" to a new USB drive "to_upgrade" 4.031
And I plug USB drive "to_upgrade" 3.999
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.378
Then the running Tails is installed on USB drive "to_upgrade" 21.409
And I unplug USB drive "to_upgrade" 0.242
And I unplug USB drive "__internal" 0.227
After features/support/hooks.rb:331 4.133
After features/support/hooks.rb:100 0.000
Tags: @product
1:29.616
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.018
Given a computer 0.345
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:19.212
Then all tps features from the old Tails version are active 2.253
And Tails is running from USB drive "to_upgrade" 0.321
And the boot device has safe access rights 3.372
And the expected persistent files created with the old Tails version are present in the filesystem 1.487
And all persistent directories from the old Tails version have safe access rights 2.622
After features/support/hooks.rb:331 0.973
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
4:8.705
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 10.442
And no SquashFS delta is installed 0.148
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.273
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.343
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.511
When the network is plugged 0.061
And Tor is ready 12.795
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.886
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.693
Given I shutdown Tails and wait for the computer to power off 5.087
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:22.330
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.151
And the file system changes introduced in version 6.2~testoverlayfs are present 0.279
And only the 6.2~testoverlayfs SquashFS delta is installed 0.097
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.177
# 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.271
When the network is plugged 0.060
And Tor is ready 13.629
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.773
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.359
Given I shutdown Tails and wait for the computer to power off 3.306
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.442
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.277
And the file system changes introduced in version 6.3~testoverlayfs are present 0.646
And only the 6.3~testoverlayfs SquashFS delta is installed 0.140
# 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.401
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.411
When the network is plugged 0.100
And Tor is ready 12.340
Then the Upgrader considers the system as up-to-date 0.103
# 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.533
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.528
After features/support/hooks.rb:331 1.707
After features/support/hooks.rb:100 0.105
Tags: @product @automatic_upgrade
24.023
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.022
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.896
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.252
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.070
But a current signing key is available on our website 0.000
When the network is plugged 0.056
And Tor is ready 10.768
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.930
After features/support/hooks.rb:331 1.112
After features/support/hooks.rb:100 0.000