Project Number Date
test_Tails_ISO_devel 3905 14 Jul 2025, 19:38

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 24:43.411 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:39.632
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.250
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 35.795
When I start Tails from USB drive "old" with network unplugged 1:56.960
Then the boot device has safe access rights 4.316
And Tails is running from USB drive "old" 0.355
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.121
And udev-watchdog is monitoring the correct device 0.378
And I unplug USB drive "old" 0.273
After features/support/hooks.rb:330 3.731
After features/support/hooks.rb:100 0.010
Tags: @product
2:39.775
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.272
And I start Tails from USB drive "old" with network unplugged and I login 1:51.719
Then Tails is running from USB drive "old" 0.386
And I create a persistent partition 34.403
And I take note of which tps features are available 3.102
Then a Tails persistence partition exists on USB drive "old" 1.048
And I shutdown Tails and wait for the computer to power off 8.842
After features/support/hooks.rb:330 0.202
After features/support/hooks.rb:100 0.018
Tags: @product
3:44.874
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.230
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:54.298
Then Tails is running from USB drive "old" 2.456
And all tps features are active 2.145
When I write some files expected to persist 2.122
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.288
And all persistence configuration files have safe access rights 0.421
And all persistent directories from the old Tails version have safe access rights 3.964
And I take note of which tps features are available 0.636
And I shutdown Tails and wait for the computer to power off 5.614
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 32.696
After features/support/hooks.rb:330 0.458
After features/support/hooks.rb:100 0.084
Tags: @product
3:3.927
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.026
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 15.179
And I log in to a new session 23.186
And I clone USB drive "old" to a new USB drive "to_upgrade" 5.476
And I plug USB drive "to_upgrade" 2.733
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.485
Then the running Tails is installed on USB drive "to_upgrade" 34.354
And I unplug USB drive "to_upgrade" 0.235
And I unplug USB drive "__internal" 0.276
After features/support/hooks.rb:330 7.102
After features/support/hooks.rb:100 0.000
Tags: @product
2:46.974
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.208
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:34.516
Then all tps features from the old Tails version are active 3.038
And Tails is running from USB drive "to_upgrade" 0.636
And the boot device has safe access rights 3.570
And the expected persistent files created with the old Tails version are present in the filesystem 1.813
And all persistent directories from the old Tails version have safe access rights 3.190
After features/support/hooks.rb:330 3.292
After features/support/hooks.rb:100 0.061
8:53.101
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.030
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.726
And no SquashFS delta is installed 0.176
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.598
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.614
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.443
When the network is plugged 0.076
And Tor is ready 22.875
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 12.467
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 19.723
Given I shutdown Tails and wait for the computer to power off 14.409
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:42.923
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.778
And the file system changes introduced in version 6.2~testoverlayfs are present 0.335
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.308
# 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.373
When the network is plugged 0.065
And Tor is ready 25.528
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 11.046
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 14.112
Given I shutdown Tails and wait for the computer to power off 8.414
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:43.909
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 4.806
And the file system changes introduced in version 6.3~testoverlayfs are present 3.002
And only the 6.3~testoverlayfs SquashFS delta is installed 0.138
# 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.452
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 1.156
When the network is plugged 0.126
And Tor is ready 24.427
Then the Upgrader considers the system as up-to-date 0.336
# 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 21.817
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.783
After features/support/hooks.rb:330 1.064
After features/support/hooks.rb:100 0.023
55.125
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 18.907
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.668
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.100
And the signing key used by the Upgrader is outdated 0.174
But a current signing key is available on our website 0.000
When the network is plugged 0.152
And Tor is ready 28.375
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.747
After features/support/hooks.rb:330 2.229
After features/support/hooks.rb:100 0.000