Project Number Date
test_Tails_ISO_devel 4436 07 Jun 2026, 11:15

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 11:31.357 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:10.170
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.079
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.508
When I start Tails from USB drive "old" with network unplugged 52.219
Then the boot device has safe access rights 2.687
And Tails is running from USB drive "old" 0.211
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.195
And I unplug USB drive "old" 0.129
After features/support/hooks.rb:335 1.237
After features/support/hooks.rb:104 0.006
Tags: @product
1:26.972
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login 53.100
Then Tails is running from USB drive "old" 0.272
And I create a persistent partition 24.369
And I take note of which tps features are available 0.386
Then a Tails persistence partition exists on USB drive "old" 0.550
And I shutdown Tails and wait for the computer to power off 8.245
After features/support/hooks.rb:335 0.477
After features/support/hooks.rb:104 0.007
Tags: @product
1:25.065
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.100
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.361
Then Tails is running from USB drive "old" 0.295
And all tps features are active 1.185
When I write some files expected to persist 1.521
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.248
And all persistence configuration files have safe access rights 0.391
And all persistent directories from the old Tails version have safe access rights 2.126
And I take note of which tps features are available 0.271
And I shutdown Tails and wait for the computer to power off 4.033
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 12.529
After features/support/hooks.rb:335 0.256
After features/support/hooks.rb:104 0.008
Tags: @product
2:10.756
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.116
And I log in to a new session 12.707
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.843
And I plug USB drive "to_upgrade" 2.220
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.293
Then the running Tails is installed on USB drive "to_upgrade" 15.230
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:335 2.076
After features/support/hooks.rb:104 0.000
Tags: @product
1:12.246
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.058
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.959
Then all tps features from the old Tails version are active 1.039
And Tails is running from USB drive "to_upgrade" 0.231
And the boot device has safe access rights 2.756
And the expected persistent files created with the old Tails version are present in the filesystem 1.137
And all persistent directories from the old Tails version have safe access rights 2.063
After features/support/hooks.rb:335 1.013
After features/support/hooks.rb:104 0.012
Tags: @product @automatic_upgrade
3:45.656
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.076
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.339
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.123
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.275
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.335
When the network is plugged 0.033
And Tor is ready 12.035
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.223
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.263
Given I shutdown Tails and wait for the computer to power off 9.769
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.423
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.149
And the file system changes introduced in version 6.2~testoverlayfs are present 0.241
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.151
# 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.201
When the network is plugged 0.015
And Tor is ready 10.466
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.529
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.169
Given I shutdown Tails and wait for the computer to power off 8.595
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.609
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 1.249
And the file system changes introduced in version 6.3~testoverlayfs are present 0.338
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.129
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.200
When the network is plugged 0.019
And Tor is ready 10.685
Then the Upgrader considers the system as up-to-date 10.619
# 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 3.792
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.384
After features/support/hooks.rb:335 0.696
After features/support/hooks.rb:104 0.010
Tags: @product @automatic_upgrade
20.489
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.643
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.209
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 9.979
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.549
After features/support/hooks.rb:335 0.736
After features/support/hooks.rb:104 0.000