Project Number Date
test_Tails_ISO_stable 6291 14 Apr 2026, 07:14

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:3.454 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:6.448
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.080
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.081
When I start Tails from USB drive "old" with network unplugged 48.904
Then the boot device has safe access rights 2.632
And Tails is running from USB drive "old" 0.271
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.214
And I unplug USB drive "old" 0.145
After features/support/hooks.rb:331 3.680
After features/support/hooks.rb:100 0.006
Tags: @product
1:26.003
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.046
And I start Tails from USB drive "old" with network unplugged and I login 52.393
Then Tails is running from USB drive "old" 0.279
And I create a persistent partition 24.237
And I take note of which tps features are available 0.662
Then a Tails persistence partition exists on USB drive "old" 0.559
And I shutdown Tails and wait for the computer to power off 7.824
After features/support/hooks.rb:331 0.312
After features/support/hooks.rb:100 0.006
Tags: @product
1:23.803
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.696
Then Tails is running from USB drive "old" 0.255
And all tps features are active 1.012
When I write some files expected to persist 1.356
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.164
And all persistence configuration files have safe access rights 0.406
And all persistent directories from the old Tails version have safe access rights 1.757
And I take note of which tps features are available 0.159
And I shutdown Tails and wait for the computer to power off 8.308
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.636
After features/support/hooks.rb:331 0.557
After features/support/hooks.rb:100 0.006
Tags: @product
2:8.739
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 7.847
And I log in to a new session 11.418
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.665
And I plug USB drive "to_upgrade" 2.225
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.005
Then the running Tails is installed on USB drive "to_upgrade" 15.313
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:331 2.072
After features/support/hooks.rb:100 0.000
Tags: @product
1:6.630
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.054
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.321
Then all tps features from the old Tails version are active 0.885
And Tails is running from USB drive "to_upgrade" 0.216
And the boot device has safe access rights 2.336
And the expected persistent files created with the old Tails version are present in the filesystem 0.953
And all persistent directories from the old Tails version have safe access rights 1.862
After features/support/hooks.rb:331 0.613
After features/support/hooks.rb:100 0.020
4:25.697
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.164
And no SquashFS delta is installed 0.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.188
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.193
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.321
When the network is plugged 0.015
And Tor is ready 19.722
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.372
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.616
Given I shutdown Tails and wait for the computer to power off 19.697
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.003
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.193
And the file system changes introduced in version 6.2~testoverlayfs are present 0.216
And only the 6.2~testoverlayfs SquashFS delta is installed 0.033
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.124
# 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.191
When the network is plugged 0.016
And Tor is ready 20.027
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.374
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.789
Given I shutdown Tails and wait for the computer to power off 17.160
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.603
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.082
And the file system changes introduced in version 6.3~testoverlayfs are present 0.346
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.135
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.283
When the network is plugged 0.017
And Tor is ready 19.980
Then the Upgrader considers the system as up-to-date 0.084
# 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.184
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.368
After features/support/hooks.rb:331 0.831
After features/support/hooks.rb:100 0.011
26.131
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.635
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.221
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.054
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 17.729
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.423
After features/support/hooks.rb:331 0.593
After features/support/hooks.rb:100 0.000