Project Number Date
test_Tails_ISO_stable 5758 04 Jul 2025, 13:09

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 20:27.578 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
2:14.132
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.187
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.067
And I write an old version of the Tails USB image to disk "old" 29.520
When I start Tails from USB drive "old" with network unplugged 1:38.950
Then the boot device has safe access rights 3.410
And Tails is running from USB drive "old" 0.282
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.308
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:330 3.654
After features/support/hooks.rb:100 0.010
Tags: @product
2:14.994
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.333
And I start Tails from USB drive "old" with network unplugged and I login 1:31.955
Then Tails is running from USB drive "old" 0.356
And I create a persistent partition 30.774
And I take note of which tps features are available 2.483
Then a Tails persistence partition exists on USB drive "old" 0.879
And I shutdown Tails and wait for the computer to power off 8.211
After features/support/hooks.rb:330 0.180
After features/support/hooks.rb:100 0.008
Tags: @product
3:11.384
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.237
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:27.463
Then Tails is running from USB drive "old" 1.877
And all tps features are active 2.146
When I write some files expected to persist 1.939
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 1.719
And all persistence configuration files have safe access rights 0.383
And all persistent directories from the old Tails version have safe access rights 2.378
And I take note of which tps features are available 0.478
And I shutdown Tails and wait for the computer to power off 6.977
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.784
After features/support/hooks.rb:330 0.180
After features/support/hooks.rb:100 0.011
Tags: @product
2:34.657
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.700
And I log in to a new session 21.350
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.793
And I plug USB drive "to_upgrade" 2.427
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.695
Then the running Tails is installed on USB drive "to_upgrade" 23.198
And I unplug USB drive "to_upgrade" 0.273
And I unplug USB drive "__internal" 0.218
After features/support/hooks.rb:330 3.552
After features/support/hooks.rb:100 0.000
Tags: @product
2:28.447
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.225
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.292
Then all tps features from the old Tails version are active 1.839
And Tails is running from USB drive "to_upgrade" 0.367
And the boot device has safe access rights 4.178
And the expected persistent files created with the old Tails version are present in the filesystem 1.678
And all persistent directories from the old Tails version have safe access rights 2.866
After features/support/hooks.rb:330 1.264
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:4.566
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.303
And no SquashFS delta is installed 0.239
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.520
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.518
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.452
When the network is plugged 0.075
And Tor is ready 23.297
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.448
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.354
Given I shutdown Tails and wait for the computer to power off 10.245
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.441
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.398
And the file system changes introduced in version 6.2~testoverlayfs are present 0.333
And only the 6.2~testoverlayfs SquashFS delta is installed 0.104
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.377
# 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.669
When the network is plugged 0.135
And Tor is ready 18.567
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.886
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.747
Given I shutdown Tails and wait for the computer to power off 4.624
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.883
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.659
And the file system changes introduced in version 6.3~testoverlayfs are present 0.448
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.407
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.567
When the network is plugged 0.108
And Tor is ready 20.625
Then the Upgrader considers the system as up-to-date 0.342
# 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 15.911
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.711
After features/support/hooks.rb:330 0.860
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
39.394
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.599
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.337
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.074
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 21.632
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.629
After features/support/hooks.rb:330 0.972
After features/support/hooks.rb:100 0.000