Project Number Date
test_Tails_ISO_21472-circumvention-settings-2 7 02 Apr 2026, 02:11

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 13:54.156 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:18.957
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.048
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.368
When I start Tails from USB drive "old" with network unplugged 1:1.236
Then the boot device has safe access rights 2.643
And Tails is running from USB drive "old" 0.237
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.039
And udev-watchdog is monitoring the correct device 0.178
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:331 1.394
After features/support/hooks.rb:100 0.006
Tags: @product
1:24.560
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login 51.838
Then Tails is running from USB drive "old" 0.293
And I create a persistent partition 23.335
And I take note of which tps features are available 0.654
Then a Tails persistence partition exists on USB drive "old" 0.504
And I shutdown Tails and wait for the computer to power off 7.878
After features/support/hooks.rb:331 0.299
After features/support/hooks.rb:100 0.006
Tags: @product
1:25.787
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.612
Then Tails is running from USB drive "old" 0.238
And all tps features are active 1.227
When I write some files expected to persist 1.254
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.437
And all persistent directories from the old Tails version have safe access rights 1.847
And I take note of which tps features are available 0.157
And I shutdown Tails and wait for the computer to power off 7.915
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.821
After features/support/hooks.rb:331 0.499
After features/support/hooks.rb:100 0.007
Tags: @product
2:10.465
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.252
And I log in to a new session 12.571
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.785
And I plug USB drive "to_upgrade" 2.230
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.207
Then the running Tails is installed on USB drive "to_upgrade" 15.127
And I unplug USB drive "to_upgrade" 0.159
And I unplug USB drive "__internal" 0.130
After features/support/hooks.rb:331 2.019
After features/support/hooks.rb:100 0.000
Tags: @product
1:7.397
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.047
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.704
Then all tps features from the old Tails version are active 0.931
And Tails is running from USB drive "to_upgrade" 0.259
And the boot device has safe access rights 2.384
And the expected persistent files created with the old Tails version are present in the filesystem 1.124
And all persistent directories from the old Tails version have safe access rights 1.946
After features/support/hooks.rb:331 0.789
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
5:39.543
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.143
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.242
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.251
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.328
When the network is plugged 0.016
And Tor is ready 1:12.083
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.380
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.891
Given I shutdown Tails and wait for the computer to power off 18.390
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.938
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.232
And the file system changes introduced in version 6.2~testoverlayfs are present 0.193
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.155
# 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.252
When the network is plugged 0.037
And Tor is ready 41.268
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.396
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.305
Given I shutdown Tails and wait for the computer to power off 18.467
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.152
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.095
And the file system changes introduced in version 6.3~testoverlayfs are present 0.282
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.176
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.174
When the network is plugged 0.015
And Tor is ready 20.676
Then the Upgrader considers the system as up-to-date 0.097
# 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.281
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.410
After features/support/hooks.rb:331 0.915
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
47.445
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.656
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.239
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.033
And the signing key used by the Upgrader is outdated 0.059
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 39.078
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.361
After features/support/hooks.rb:331 0.807
After features/support/hooks.rb:100 0.000