Project Number Date
test_Tails_ISO_devel 4354 21 Apr 2026, 11:18

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 12:56.103 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:0.153
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.098
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 14.129
When I start Tails from USB drive "old" with network unplugged 41.052
Then the boot device has safe access rights 3.068
And Tails is running from USB drive "old" 0.337
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.194
And I unplug USB drive "old" 0.137
After features/support/hooks.rb:331 1.346
After features/support/hooks.rb:100 0.008
Tags: @product
1:31.568
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.089
And I start Tails from USB drive "old" with network unplugged and I login 56.919
Then Tails is running from USB drive "old" 0.663
And I create a persistent partition 24.079
And I take note of which tps features are available 0.834
Then a Tails persistence partition exists on USB drive "old" 0.601
And I shutdown Tails and wait for the computer to power off 8.380
After features/support/hooks.rb:331 0.379
After features/support/hooks.rb:100 0.008
Tags: @product
1:32.677
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.067
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.014
Then Tails is running from USB drive "old" 0.277
And all tps features are active 1.346
When I write some files expected to persist 1.416
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.210
And all persistence configuration files have safe access rights 0.468
And all persistent directories from the old Tails version have safe access rights 2.199
And I take note of which tps features are available 0.183
And I shutdown Tails and wait for the computer to power off 8.072
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.420
After features/support/hooks.rb:331 0.173
After features/support/hooks.rb:100 0.007
Tags: @product
2:19.298
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.203
And I log in to a new session 18.316
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.796
And I plug USB drive "to_upgrade" 2.248
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.490
Then the running Tails is installed on USB drive "to_upgrade" 16.934
And I unplug USB drive "to_upgrade" 0.152
And I unplug USB drive "__internal" 0.156
After features/support/hooks.rb:331 3.592
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.621
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.068
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.789
Then all tps features from the old Tails version are active 1.099
And Tails is running from USB drive "to_upgrade" 0.230
And the boot device has safe access rights 2.816
And the expected persistent files created with the old Tails version are present in the filesystem 1.395
And all persistent directories from the old Tails version have safe access rights 2.221
After features/support/hooks.rb:331 0.650
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:50.219
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.674
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.298
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
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.332
When the network is plugged 0.014
And Tor is ready 24.323
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.433
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.210
Given I shutdown Tails and wait for the computer to power off 21.315
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.216
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.269
And the file system changes introduced in version 6.2~testoverlayfs are present 0.248
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.194
# 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.255
When the network is plugged 0.025
And Tor is ready 20.606
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.388
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.679
Given I shutdown Tails and wait for the computer to power off 17.242
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.671
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.138
And the file system changes introduced in version 6.3~testoverlayfs are present 0.426
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.137
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.207
When the network is plugged 0.015
And Tor is ready 21.624
Then the Upgrader considers the system as up-to-date 0.109
# 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 4.278
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.409
After features/support/hooks.rb:331 0.727
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
29.563
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.841
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.231
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 20.969
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.389
After features/support/hooks.rb:331 0.658
After features/support/hooks.rb:100 0.000