Project Number Date
test_Tails_ISO_devel 4145 01 Jan 2026, 11:49

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:30.633 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:27.775
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.042
And I write an old version of the Tails USB image to disk "old" 27.071
When I start Tails from USB drive "old" with network unplugged 55.461
Then the boot device has safe access rights 3.110
And Tails is running from USB drive "old" 0.272
And there is no persistence partition on USB drive "old" 0.055
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.235
And I unplug USB drive "old" 0.226
After features/support/hooks.rb:331 3.496
After features/support/hooks.rb:100 0.014
Tags: @product
1:39.052
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.246
And I start Tails from USB drive "old" with network unplugged and I login 1:0.086
Then Tails is running from USB drive "old" 0.319
And I create a persistent partition 29.101
And I take note of which tps features are available 1.103
Then a Tails persistence partition exists on USB drive "old" 0.674
And I shutdown Tails and wait for the computer to power off 7.520
After features/support/hooks.rb:331 0.486
After features/support/hooks.rb:100 0.009
Tags: @product
1:45.288
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:12.051
Then Tails is running from USB drive "old" 0.310
And all tps features are active 1.792
When I write some files expected to persist 1.643
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.212
And all persistence configuration files have safe access rights 0.377
And all persistent directories from the old Tails version have safe access rights 2.397
And I take note of which tps features are available 0.581
And I shutdown Tails and wait for the computer to power off 7.912
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.790
After features/support/hooks.rb:331 0.672
After features/support/hooks.rb:100 0.013
Tags: @product
2:23.763
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.037
And I log in to a new session 9.815
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.841
And I plug USB drive "to_upgrade" 3.192
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.945
Then the running Tails is installed on USB drive "to_upgrade" 19.532
And I unplug USB drive "to_upgrade" 0.199
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:331 3.588
After features/support/hooks.rb:100 0.000
Tags: @product
1:24.531
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.179
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:14.489
Then all tps features from the old Tails version are active 2.175
And Tails is running from USB drive "to_upgrade" 0.277
And the boot device has safe access rights 2.946
And the expected persistent files created with the old Tails version are present in the filesystem 1.642
And all persistent directories from the old Tails version have safe access rights 2.821
After features/support/hooks.rb:331 0.926
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
4:28.439
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.105
And no SquashFS delta is installed 0.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.235
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.288
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.460
When the network is plugged 0.054
And Tor is ready 13.821
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.611
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.353
Given I shutdown Tails and wait for the computer to power off 7.719
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.831
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.043
And the file system changes introduced in version 6.2~testoverlayfs are present 0.288
And only the 6.2~testoverlayfs SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.164
# 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.307
When the network is plugged 0.052
And Tor is ready 12.687
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.740
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.512
Given I shutdown Tails and wait for the computer to power off 4.941
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.053
Then Tails is running version 6.3~testoverlayfs 0.034
And all tps features are active 2.162
And the file system changes introduced in version 6.3~testoverlayfs are present 0.434
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.170
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.321
When the network is plugged 0.096
And Tor is ready 41.737
Then the Upgrader considers the system as up-to-date 0.121
# 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.214
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.556
After features/support/hooks.rb:331 0.810
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
21.782
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 9.042
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.198
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.110
But a current signing key is available on our website 0.000
When the network is plugged 0.080
And Tor is ready 10.576
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.724
After features/support/hooks.rb:331 1.146
After features/support/hooks.rb:100 0.000