Project Number Date
test_Tails_ISO_devel 4159 08 Jan 2026, 22:21

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 14:39.232 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:45.179
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.259
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 32.786
When I start Tails from USB drive "old" with network unplugged 1:7.306
Then the boot device has safe access rights 2.900
And Tails is running from USB drive "old" 0.284
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.248
And I unplug USB drive "old" 0.170
After features/support/hooks.rb:331 3.753
After features/support/hooks.rb:100 0.011
Tags: @product
1:48.188
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.216
And I start Tails from USB drive "old" with network unplugged and I login 1:7.164
Then Tails is running from USB drive "old" 0.711
And I create a persistent partition 30.587
And I take note of which tps features are available 1.364
Then a Tails persistence partition exists on USB drive "old" 0.749
And I shutdown Tails and wait for the computer to power off 7.394
After features/support/hooks.rb:331 0.339
After features/support/hooks.rb:100 0.013
Tags: @product
1:52.355
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.299
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:17.678
Then Tails is running from USB drive "old" 0.336
And all tps features are active 2.042
When I write some files expected to persist 1.771
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.227
And all persistence configuration files have safe access rights 0.481
And all persistent directories from the old Tails version have safe access rights 2.330
And I take note of which tps features are available 0.463
And I shutdown Tails and wait for the computer to power off 7.796
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.926
After features/support/hooks.rb:331 0.936
After features/support/hooks.rb:100 0.013
Tags: @product
2:44.572
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 13.884
And I log in to a new session 16.401
And I clone USB drive "old" to a new USB drive "to_upgrade" 4.432
And I plug USB drive "to_upgrade" 2.483
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.767
Then the running Tails is installed on USB drive "to_upgrade" 21.042
And I unplug USB drive "to_upgrade" 0.336
And I unplug USB drive "__internal" 0.223
After features/support/hooks.rb:331 4.014
After features/support/hooks.rb:100 0.000
Tags: @product
1:27.482
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given a computer 0.177
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:17.864
Then all tps features from the old Tails version are active 2.010
And Tails is running from USB drive "to_upgrade" 0.399
And the boot device has safe access rights 3.156
And the expected persistent files created with the old Tails version are present in the filesystem 1.360
And all persistent directories from the old Tails version have safe access rights 2.513
After features/support/hooks.rb:331 1.123
After features/support/hooks.rb:100 0.009
4:36.489
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.960
And no SquashFS delta is installed 0.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.288
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.262
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.428
When the network is plugged 0.053
And Tor is ready 14.366
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.888
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.546
Given I shutdown Tails and wait for the computer to power off 10.232
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:28.861
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.503
And the file system changes introduced in version 6.2~testoverlayfs are present 0.255
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.172
# 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.515
When the network is plugged 0.145
And Tor is ready 12.397
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.644
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.089
Given I shutdown Tails and wait for the computer to power off 8.283
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.987
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.379
And the file system changes introduced in version 6.3~testoverlayfs are present 0.461
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.155
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.206
When the network is plugged 0.056
And Tor is ready 13.724
Then the Upgrader considers the system as up-to-date 0.147
# 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.696
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.477
After features/support/hooks.rb:331 0.731
After features/support/hooks.rb:100 0.016
24.964
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 12.397
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.334
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.060
But a current signing key is available on our website 0.000
When the network is plugged 0.080
And Tor is ready 11.431
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.603
After features/support/hooks.rb:331 1.664
After features/support/hooks.rb:100 0.000