Project Number Date
test_Tails_ISO_stable 5649 15 May 2025, 12:31

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:30.331 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:16.656
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.206
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 31.084
When I start Tails from USB drive "old" with network unplugged 1:39.978
Then the boot device has safe access rights 3.230
And Tails is running from USB drive "old" 0.350
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.109
And udev-watchdog is monitoring the correct device 0.335
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:330 3.594
After features/support/hooks.rb:100 0.010
Tags: @product
2:10.413
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login 1:28.372
Then Tails is running from USB drive "old" 0.397
And I create a persistent partition 31.848
And I take note of which tps features are available 2.153
Then a Tails persistence partition exists on USB drive "old" 0.846
And I shutdown Tails and wait for the computer to power off 6.617
After features/support/hooks.rb:330 0.222
After features/support/hooks.rb:100 0.009
Tags: @product
3:7.626
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.168
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:29.032
Then Tails is running from USB drive "old" 0.726
And all tps features are active 2.633
When I write some files expected to persist 2.808
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.285
And all persistence configuration files have safe access rights 0.412
And all persistent directories from the old Tails version have safe access rights 2.462
And I take note of which tps features are available 0.426
And I shutdown Tails and wait for the computer to power off 4.228
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.440
After features/support/hooks.rb:330 0.108
After features/support/hooks.rb:100 0.009
Tags: @product
2:31.353
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 without a persistent partition and stopped at Tails Greeter's login screen 10.980
And I log in to a new session 17.959
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.025
And I plug USB drive "to_upgrade" 2.906
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.738
Then the running Tails is installed on USB drive "to_upgrade" 21.274
And I unplug USB drive "to_upgrade" 0.248
And I unplug USB drive "__internal" 0.218
After features/support/hooks.rb:330 0.749
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.033
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.172
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.637
Then all tps features from the old Tails version are active 1.514
And Tails is running from USB drive "to_upgrade" 0.321
And the boot device has safe access rights 3.510
And the expected persistent files created with the old Tails version are present in the filesystem 1.457
And all persistent directories from the old Tails version have safe access rights 2.419
After features/support/hooks.rb:330 1.096
After features/support/hooks.rb:100 0.007
6:35.717
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.116
And no SquashFS delta is installed 0.109
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.331
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.259
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.449
When the network is plugged 0.073
And Tor is ready 20.558
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.575
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.886
Given I shutdown Tails and wait for the computer to power off 10.835
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.214
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.249
And the file system changes introduced in version 6.2~testoverlayfs are present 0.298
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.296
# 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.340
When the network is plugged 0.065
And Tor is ready 18.177
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.636
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.882
Given I shutdown Tails and wait for the computer to power off 4.187
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.934
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.101
And the file system changes introduced in version 6.3~testoverlayfs are present 0.561
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.303
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.308
When the network is plugged 0.081
And Tor is ready 16.840
Then the Upgrader considers the system as up-to-date 0.302
# 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.598
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.924
After features/support/hooks.rb:330 0.722
After features/support/hooks.rb:100 0.017
35.530
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 9.946
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.330
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.066
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 18.498
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.561
After features/support/hooks.rb:330 0.721
After features/support/hooks.rb:100 0.000