Project Number Date
test_Tails_ISO_stable 6024 27 Dec 2025, 11:46

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 14:12.575 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:36.734
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.186
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 30.146
When I start Tails from USB drive "old" with network unplugged 1:1.388
Then the boot device has safe access rights 3.036
And Tails is running from USB drive "old" 0.339
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.221
And I unplug USB drive "old" 0.166
After features/support/hooks.rb:331 4.221
After features/support/hooks.rb:100 0.009
Tags: @product
1:35.934
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.158
And I start Tails from USB drive "old" with network unplugged and I login 1:0.340
Then Tails is running from USB drive "old" 0.265
And I create a persistent partition 26.093
And I take note of which tps features are available 1.012
Then a Tails persistence partition exists on USB drive "old" 0.626
And I shutdown Tails and wait for the computer to power off 7.437
After features/support/hooks.rb:331 0.457
After features/support/hooks.rb:100 0.009
Tags: @product
1:42.265
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:10.571
Then Tails is running from USB drive "old" 0.289
And all tps features are active 1.731
When I write some files expected to persist 1.399
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.189
And all persistence configuration files have safe access rights 0.357
And all persistent directories from the old Tails version have safe access rights 2.204
And I take note of which tps features are available 0.421
And I shutdown Tails and wait for the computer to power off 7.529
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.382
After features/support/hooks.rb:331 0.602
After features/support/hooks.rb:100 0.009
Tags: @product
2:50.816
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.616
And I log in to a new session 14.674
And I clone USB drive "old" to a new USB drive "to_upgrade" 6.791
And I plug USB drive "to_upgrade" 2.683
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:54.716
Then the running Tails is installed on USB drive "to_upgrade" 18.936
And I unplug USB drive "to_upgrade" 0.183
And I unplug USB drive "__internal" 0.214
After features/support/hooks.rb:331 4.204
After features/support/hooks.rb:100 0.000
Tags: @product
1:20.275
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.166
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:12.572
Then all tps features from the old Tails version are active 1.297
And Tails is running from USB drive "to_upgrade" 0.256
And the boot device has safe access rights 2.726
And the expected persistent files created with the old Tails version are present in the filesystem 1.244
And all persistent directories from the old Tails version have safe access rights 2.011
After features/support/hooks.rb:331 0.656
After features/support/hooks.rb:100 0.082
4:43.785
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.849
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.278
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.245
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.389
When the network is plugged 0.047
And Tor is ready 13.843
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.648
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.774
Given I shutdown Tails and wait for the computer to power off 7.965
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.447
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.034
And the file system changes introduced in version 6.2~testoverlayfs are present 0.290
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.146
# 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.199
When the network is plugged 0.065
And Tor is ready 44.373
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.568
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.297
Given I shutdown Tails and wait for the computer to power off 7.423
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.386
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.908
And the file system changes introduced in version 6.3~testoverlayfs are present 0.452
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.154
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.242
When the network is plugged 0.051
And Tor is ready 11.016
Then the Upgrader considers the system as up-to-date 10.571
# 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 5.262
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.551
After features/support/hooks.rb:331 0.869
After features/support/hooks.rb:100 0.028
22.763
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.009
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.246
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.067
But a current signing key is available on our website 0.000
When the network is plugged 0.061
And Tor is ready 11.745
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.575
After features/support/hooks.rb:331 1.071
After features/support/hooks.rb:100 0.000