Project Number Date
test_Tails_ISO_devel 4112 10 Dec 2025, 10:30

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 15:11.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:52.789
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.160
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 32.660
When I start Tails from USB drive "old" with network unplugged 1:14.664
Then the boot device has safe access rights 3.347
And Tails is running from USB drive "old" 0.324
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.074
And udev-watchdog is monitoring the correct device 0.211
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:331 4.039
After features/support/hooks.rb:100 0.009
Tags: @product
2:4.220
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login 1:24.825
Then Tails is running from USB drive "old" 0.433
And I create a persistent partition 29.395
And I take note of which tps features are available 1.192
Then a Tails persistence partition exists on USB drive "old" 0.690
And I shutdown Tails and wait for the computer to power off 7.506
After features/support/hooks.rb:331 0.388
After features/support/hooks.rb:100 0.017
Tags: @product
2:10.752
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.264
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:36.685
Then Tails is running from USB drive "old" 0.383
And all tps features are active 1.778
When I write some files expected to persist 1.804
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.243
And all persistence configuration files have safe access rights 0.443
And all persistent directories from the old Tails version have safe access rights 2.514
And I take note of which tps features are available 0.469
And I shutdown Tails and wait for the computer to power off 7.732
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.433
After features/support/hooks.rb:331 0.231
After features/support/hooks.rb:100 0.009
Tags: @product
2:39.559
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 11.130
And I log in to a new session 15.412
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.049
And I plug USB drive "to_upgrade" 2.982
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.408
Then the running Tails is installed on USB drive "to_upgrade" 23.119
And I unplug USB drive "to_upgrade" 0.186
And I unplug USB drive "__internal" 0.270
After features/support/hooks.rb:331 4.009
After features/support/hooks.rb:100 0.000
Tags: @product
1:30.143
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.177
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:20.533
Then all tps features from the old Tails version are active 1.580
And Tails is running from USB drive "to_upgrade" 0.340
And the boot device has safe access rights 3.435
And the expected persistent files created with the old Tails version are present in the filesystem 1.788
And all persistent directories from the old Tails version have safe access rights 2.288
After features/support/hooks.rb:331 0.793
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
4:30.095
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.429
And no SquashFS delta is installed 0.119
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.300
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.085
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.397
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.772
When the network is plugged 0.114
And Tor is ready 13.787
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.819
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.396
Given I shutdown Tails and wait for the computer to power off 11.703
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:26.340
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.949
And the file system changes introduced in version 6.2~testoverlayfs are present 0.390
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.220
# 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.264
When the network is plugged 0.059
And Tor is ready 11.187
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.902
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.376
Given I shutdown Tails and wait for the computer to power off 8.088
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.870
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.031
And the file system changes introduced in version 6.3~testoverlayfs are present 0.534
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.166
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.344
When the network is plugged 0.059
And Tor is ready 12.659
Then the Upgrader considers the system as up-to-date 0.165
# 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.750
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.648
After features/support/hooks.rb:331 1.168
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
24.292
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 11.538
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.270
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 0.065
But a current signing key is available on our website 0.000
When the network is plugged 0.057
And Tor is ready 11.560
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.731
After features/support/hooks.rb:331 1.308
After features/support/hooks.rb:100 0.000