Project Number Date
test_Tails_ISO_stable 6687 22 Sep 2026, 11:37

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:16.932 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.141
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.096
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.087
When I start Tails from USB drive "old" with network unplugged 42.830
Then the boot device has safe access rights 2.161
And Tails is running from USB drive "old" 0.392
And there is no persistence partition on USB drive "old" 0.138
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.180
And I unplug USB drive "old" 0.144
After features/support/hooks.rb:339 3.416
After features/support/hooks.rb:108 0.020
Tags: @product
1:21.867
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login 48.554
Then Tails is running from USB drive "old" 0.210
And I create a persistent partition 23.253
And I take note of which tps features are available 6.633
Then a Tails persistence partition exists on USB drive "old" 0.513
And I shutdown Tails and wait for the computer to power off 2.621
After features/support/hooks.rb:339 0.446
After features/support/hooks.rb:108 0.005
Tags: @product
1:32.166
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.495
Then Tails is running from USB drive "old" 0.170
And all tps features are active 6.770
When I write some files expected to persist 1.168
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.183
And all persistence configuration files have safe access rights 0.226
And all persistent directories from the old Tails version have safe access rights 1.665
And I take note of which tps features are available 6.612
And I shutdown Tails and wait for the computer to power off 2.599
# 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" 11.184
After features/support/hooks.rb:339 0.167
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.984
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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.779
And I log in to a new session 11.286
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.597
And I plug USB drive "to_upgrade" 2.185
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.709
Then the running Tails is installed on USB drive "to_upgrade" 18.152
And I unplug USB drive "to_upgrade" 0.129
And I unplug USB drive "__internal" 0.144
After features/support/hooks.rb:339 1.609
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.222
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.072
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.656
Then all tps features from the old Tails version are active 1.090
And Tails is running from USB drive "to_upgrade" 0.207
And the boot device has safe access rights 2.255
And the expected persistent files created with the old Tails version are present in the filesystem 1.127
And all persistent directories from the old Tails version have safe access rights 1.812
After features/support/hooks.rb:339 0.486
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:42.621
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.328
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.215
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.032
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.177
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.286
When the network is plugged 0.027
And Tor is ready 12.236
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.611
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.155
Given I shutdown Tails and wait for the computer to power off 5.247
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.659
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.226
And the file system changes introduced in version 6.2~testoverlayfs are present 0.210
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.139
# 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.236
When the network is plugged 0.026
And Tor is ready 10.290
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.147
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.854
Given I shutdown Tails and wait for the computer to power off 4.021
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.240
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.424
And the file system changes introduced in version 6.3~testoverlayfs are present 0.286
And only the 6.3~testoverlayfs SquashFS delta is installed 0.040
# 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.113
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.425
When the network is plugged 0.040
And Tor is ready 10.288
Then the Upgrader considers the system as up-to-date 10.376
# 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.668
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.451
After features/support/hooks.rb:339 0.828
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
18.927
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.931
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.220
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.026
And Tor is ready 8.282
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.379
After features/support/hooks.rb:339 0.763
After features/support/hooks.rb:108 0.000