Project Number Date
test_Tails_ISO_devel 3752 25 Mar 2025, 10:01

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:34.797 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:6.937
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.206
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 29.450
When I start Tails from USB drive "old" with network unplugged 1:32.033
Then the boot device has safe access rights 3.130
And Tails is running from USB drive "old" 0.359
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.293
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:330 3.735
After features/support/hooks.rb:100 0.009
Tags: @product
2:8.194
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login 1:25.798
Then Tails is running from USB drive "old" 0.311
And I create a persistent partition 30.881
And I take note of which tps features are available 1.786
Then a Tails persistence partition exists on USB drive "old" 0.784
And I shutdown Tails and wait for the computer to power off 8.444
After features/support/hooks.rb:330 0.184
After features/support/hooks.rb:100 0.008
Tags: @product
2:53.927
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.969
Then Tails is running from USB drive "old" 0.960
And all tps features are active 2.140
When I write some files expected to persist 1.791
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.220
And all persistence configuration files have safe access rights 0.429
And all persistent directories from the old Tails version have safe access rights 2.336
And I take note of which tps features are available 0.452
And I shutdown Tails and wait for the computer to power off 6.186
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.252
After features/support/hooks.rb:330 0.424
After features/support/hooks.rb:100 0.051
Tags: @product
2:30.752
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.034
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.354
And I log in to a new session 19.837
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.665
And I plug USB drive "to_upgrade" 2.429
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.752
Then the running Tails is installed on USB drive "to_upgrade" 22.252
And I unplug USB drive "to_upgrade" 0.231
And I unplug USB drive "__internal" 0.228
After features/support/hooks.rb:330 2.175
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.409
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.230
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.904
Then all tps features from the old Tails version are active 1.679
And Tails is running from USB drive "to_upgrade" 0.311
And the boot device has safe access rights 3.469
And the expected persistent files created with the old Tails version are present in the filesystem 1.465
And all persistent directories from the old Tails version have safe access rights 2.347
After features/support/hooks.rb:330 1.393
After features/support/hooks.rb:100 0.009
6:46.413
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 with a persistent partition enabled and logged in 13.675
And no SquashFS delta is installed 0.062
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.363
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.104
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.621
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.446
When the network is plugged 0.116
And Tor is ready 22.920
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.472
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.434
Given I shutdown Tails and wait for the computer to power off 11.210
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.943
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.418
And the file system changes introduced in version 6.2~testoverlayfs are present 0.517
And only the 6.2~testoverlayfs SquashFS delta is installed 0.095
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.306
# 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.307
When the network is plugged 0.082
And Tor is ready 18.647
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.225
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.945
Given I shutdown Tails and wait for the computer to power off 4.267
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.151
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.221
And the file system changes introduced in version 6.3~testoverlayfs are present 0.497
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.311
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.332
When the network is plugged 0.080
And Tor is ready 19.314
Then the Upgrader considers the system as up-to-date 0.321
# 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 14.737
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.156
After features/support/hooks.rb:330 0.975
After features/support/hooks.rb:100 0.018
41.163
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 with a persistent partition enabled and logged in 11.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.357
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.119
And the signing key used by the Upgrader is outdated 0.098
But a current signing key is available on our website 0.000
When the network is plugged 0.087
And Tor is ready 22.690
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.744
After features/support/hooks.rb:330 0.692
After features/support/hooks.rb:100 0.000