Project Number Date
test_Tails_ISO_stable 5767 15 Jul 2025, 13:13

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 19:55.284 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:59.994
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.229
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 29.440
When I start Tails from USB drive "old" with network unplugged 1:24.845
Then the boot device has safe access rights 3.340
And Tails is running from USB drive "old" 0.342
And there is no persistence partition on USB drive "old" 0.091
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.303
And I unplug USB drive "old" 0.208
After features/support/hooks.rb:330 1.232
After features/support/hooks.rb:100 0.009
Tags: @product
2:16.375
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login 1:31.292
Then Tails is running from USB drive "old" 0.416
And I create a persistent partition 32.418
And I take note of which tps features are available 2.508
Then a Tails persistence partition exists on USB drive "old" 0.866
And I shutdown Tails and wait for the computer to power off 8.681
After features/support/hooks.rb:330 0.137
After features/support/hooks.rb:100 0.009
Tags: @product
2:59.605
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.273
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.468
Then Tails is running from USB drive "old" 1.631
And all tps features are active 2.905
When I write some files expected to persist 2.707
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.225
And all persistence configuration files have safe access rights 0.415
And all persistent directories from the old Tails version have safe access rights 3.523
And I take note of which tps features are available 0.488
And I shutdown Tails and wait for the computer to power off 4.692
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.272
After features/support/hooks.rb:330 0.132
After features/support/hooks.rb:100 0.009
Tags: @product
2:41.687
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 10.244
And I log in to a new session 18.940
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.578
And I plug USB drive "to_upgrade" 2.552
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.051
Then the running Tails is installed on USB drive "to_upgrade" 26.835
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.273
After features/support/hooks.rb:330 2.482
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.685
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.265
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.602
Then all tps features from the old Tails version are active 2.140
And Tails is running from USB drive "to_upgrade" 0.337
And the boot device has safe access rights 3.678
And the expected persistent files created with the old Tails version are present in the filesystem 1.711
And all persistent directories from the old Tails version have safe access rights 2.949
After features/support/hooks.rb:330 1.151
After features/support/hooks.rb:100 0.009
6:59.046
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.492
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.338
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.114
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.390
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.535
When the network is plugged 0.097
And Tor is ready 20.676
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.004
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.435
Given I shutdown Tails and wait for the computer to power off 8.986
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.430
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.324
And the file system changes introduced in version 6.2~testoverlayfs are present 0.377
And only the 6.2~testoverlayfs SquashFS delta is installed 0.119
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.438
# 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.350
When the network is plugged 0.080
And Tor is ready 49.291
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.651
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.303
Given I shutdown Tails and wait for the computer to power off 4.556
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.566
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.957
And the file system changes introduced in version 6.3~testoverlayfs are present 0.447
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.329
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.298
When the network is plugged 0.077
And Tor is ready 17.705
Then the Upgrader considers the system as up-to-date 0.316
# 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.451
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.712
After features/support/hooks.rb:330 0.742
After features/support/hooks.rb:100 0.020
35.890
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 9.798
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.323
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.091
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 18.099
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.439
After features/support/hooks.rb:330 1.483
After features/support/hooks.rb:100 0.000