Project Number Date
test_Tails_ISO_devel 4321 06 Apr 2026, 11:34

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:34.852 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:25.687
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.057
And I create a 7200 MiB disk named "old" 0.013
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 14.350
When I start Tails from USB drive "old" with network unplugged 1:6.497
Then the boot device has safe access rights 2.994
And Tails is running from USB drive "old" 0.289
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.080
And udev-watchdog is monitoring the correct device 0.186
And I unplug USB drive "old" 0.154
After features/support/hooks.rb:331 1.297
After features/support/hooks.rb:100 0.006
Tags: @product
1:24.256
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login 55.197
Then Tails is running from USB drive "old" 0.284
And I create a persistent partition 24.455
And I take note of which tps features are available 0.719
Then a Tails persistence partition exists on USB drive "old" 0.646
And I shutdown Tails and wait for the computer to power off 2.900
After features/support/hooks.rb:331 0.625
After features/support/hooks.rb:100 0.006
Tags: @product
1:32.344
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.065
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.015
Then Tails is running from USB drive "old" 0.277
And all tps features are active 1.367
When I write some files expected to persist 1.580
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.203
And all persistence configuration files have safe access rights 0.469
And all persistent directories from the old Tails version have safe access rights 2.145
And I take note of which tps features are available 0.183
And I shutdown Tails and wait for the computer to power off 7.957
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.079
After features/support/hooks.rb:331 0.489
After features/support/hooks.rb:100 0.007
Tags: @product
2:22.780
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.746
And I log in to a new session 17.324
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.966
And I plug USB drive "to_upgrade" 2.259
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.926
Then the running Tails is installed on USB drive "to_upgrade" 17.286
And I unplug USB drive "to_upgrade" 0.129
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:331 3.537
After features/support/hooks.rb:100 0.000
Tags: @product
1:13.767
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.067
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.365
Then all tps features from the old Tails version are active 1.113
And Tails is running from USB drive "to_upgrade" 0.292
And the boot device has safe access rights 2.692
And the expected persistent files created with the old Tails version are present in the filesystem 1.130
And all persistent directories from the old Tails version have safe access rights 2.105
After features/support/hooks.rb:331 1.033
After features/support/hooks.rb:100 0.024
4:45.039
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 8.441
And no SquashFS delta is installed 0.130
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.339
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.101
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.249
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.435
When the network is plugged 0.027
And Tor is ready 23.935
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.371
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.468
Given I shutdown Tails and wait for the computer to power off 18.540
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.546
Then Tails is running version 6.2~testoverlayfs 0.026
And all tps features are active 1.074
And the file system changes introduced in version 6.2~testoverlayfs are present 0.236
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.167
# 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.246
When the network is plugged 0.016
And Tor is ready 20.808
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.362
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.971
Given I shutdown Tails and wait for the computer to power off 17.717
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.235
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.158
And the file system changes introduced in version 6.3~testoverlayfs are present 0.456
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.159
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.206
When the network is plugged 0.015
And Tor is ready 22.068
Then the Upgrader considers the system as up-to-date 0.099
# 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.777
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.490
After features/support/hooks.rb:331 1.042
After features/support/hooks.rb:100 0.011
50.976
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 8.237
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.310
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.057
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 41.878
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.428
After features/support/hooks.rb:331 0.872
After features/support/hooks.rb:100 0.000