Project Number Date
test_Tails_ISO_devel 4523 30 Jul 2026, 11:25

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:20.551 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:7.632
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.085
And I create a 7200 MiB disk named "old" 0.024
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.601
When I start Tails from USB drive "old" with network unplugged 50.235
Then the boot device has safe access rights 2.048
And Tails is running from USB drive "old" 0.206
And there is no persistence partition on USB drive "old" 0.033
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.188
And I unplug USB drive "old" 0.136
After features/support/hooks.rb:339 3.432
After features/support/hooks.rb:108 0.005
Tags: @product
1:23.305
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.092
And I start Tails from USB drive "old" with network unplugged and I login 48.823
Then Tails is running from USB drive "old" 0.210
And I create a persistent partition 23.377
And I take note of which tps features are available 6.047
Then a Tails persistence partition exists on USB drive "old" 0.515
And I shutdown Tails and wait for the computer to power off 4.238
After features/support/hooks.rb:339 0.557
After features/support/hooks.rb:108 0.005
Tags: @product
1:32.135
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.575
Then Tails is running from USB drive "old" 0.222
And all tps features are active 7.166
When I write some files expected to persist 0.972
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.145
And all persistence configuration files have safe access rights 0.248
And all persistent directories from the old Tails version have safe access rights 1.292
And I take note of which tps features are available 6.621
And I shutdown Tails and wait for the computer to power off 2.652
# 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.160
After features/support/hooks.rb:339 0.198
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.652
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.267
And I log in to a new session 11.221
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.652
And I plug USB drive "to_upgrade" 2.287
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.044
Then the running Tails is installed on USB drive "to_upgrade" 17.837
And I unplug USB drive "to_upgrade" 0.167
And I unplug USB drive "__internal" 0.174
After features/support/hooks.rb:339 1.399
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.661
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.071
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.799
Then all tps features from the old Tails version are active 1.223
And Tails is running from USB drive "to_upgrade" 0.168
And the boot device has safe access rights 1.974
And the expected persistent files created with the old Tails version are present in the filesystem 0.917
And all persistent directories from the old Tails version have safe access rights 1.506
After features/support/hooks.rb:339 0.508
After features/support/hooks.rb:108 0.005
3:27.110
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 8.137
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.184
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.284
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.381
When the network is plugged 0.033
And Tor is ready 11.724
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.421
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.920
Given I shutdown Tails and wait for the computer to power off 5.360
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.088
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.491
And the file system changes introduced in version 6.2~testoverlayfs are present 0.157
And only the 6.2~testoverlayfs SquashFS delta is installed 0.037
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.158
# 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.335
When the network is plugged 0.084
And Tor is ready 10.327
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.291
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.410
Given I shutdown Tails and wait for the computer to power off 2.617
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.227
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.253
And the file system changes introduced in version 6.3~testoverlayfs are present 0.418
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.105
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.193
When the network is plugged 0.024
And Tor is ready 10.274
Then the Upgrader considers the system as up-to-date 0.090
# 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.513
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.347
After features/support/hooks.rb:339 0.923
After features/support/hooks.rb:108 0.028
32.052
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 21.347
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.238
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.030
And the signing key used by the Upgrader is outdated 0.033
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 8.480
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.887
After features/support/hooks.rb:339 0.649
After features/support/hooks.rb:108 0.000