Project Number Date
test_Tails_ISO_stable 5715 14 Jun 2025, 13:15

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 23:14.764 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:43.175
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.192
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 36.506
When I start Tails from USB drive "old" with network unplugged 2:0.842
Then the boot device has safe access rights 3.332
And Tails is running from USB drive "old" 0.391
And there is no persistence partition on USB drive "old" 0.085
And process "udev-watchdog" is running 0.125
And udev-watchdog is monitoring the correct device 0.310
And I unplug USB drive "old" 0.293
After features/support/hooks.rb:330 7.920
After features/support/hooks.rb:100 0.011
Tags: @product
2:34.793
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.270
And I start Tails from USB drive "old" with network unplugged and I login 1:45.512
Then Tails is running from USB drive "old" 0.389
And I create a persistent partition 35.853
And I take note of which tps features are available 2.879
Then a Tails persistence partition exists on USB drive "old" 1.031
And I shutdown Tails and wait for the computer to power off 8.856
After features/support/hooks.rb:330 0.203
After features/support/hooks.rb:100 0.008
Tags: @product
3:28.627
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.219
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:38.892
Then Tails is running from USB drive "old" 0.575
And all tps features are active 3.244
When I write some files expected to persist 2.673
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.331
And all persistence configuration files have safe access rights 0.465
And all persistent directories from the old Tails version have safe access rights 3.666
And I take note of which tps features are available 0.517
And I shutdown Tails and wait for the computer to power off 6.233
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 31.807
After features/support/hooks.rb:330 0.125
After features/support/hooks.rb:100 0.009
Tags: @product
2:49.743
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 12.197
And I log in to a new session 22.654
And I clone USB drive "old" to a new USB drive "to_upgrade" 3.128
And I plug USB drive "to_upgrade" 2.668
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.820
Then the running Tails is installed on USB drive "to_upgrade" 25.825
And I unplug USB drive "to_upgrade" 0.240
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:330 2.425
After features/support/hooks.rb:100 0.000
Tags: @product
2:42.954
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.209
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:30.366
Then all tps features from the old Tails version are active 1.791
And Tails is running from USB drive "to_upgrade" 0.365
And the boot device has safe access rights 3.216
And the expected persistent files created with the old Tails version are present in the filesystem 1.537
And all persistent directories from the old Tails version have safe access rights 5.468
After features/support/hooks.rb:330 0.965
After features/support/hooks.rb:100 0.009
8:11.234
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 15.300
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.463
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.303
And the file system changes introduced in version 6.3~testoverlayfs are not present 3.566
When the network is plugged 0.926
And Tor is ready 50.365
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.615
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.389
Given I shutdown Tails and wait for the computer to power off 8.719
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:28.749
Then Tails is running version 6.2~testoverlayfs 0.042
And all tps features are active 3.308
And the file system changes introduced in version 6.2~testoverlayfs are present 0.531
And only the 6.2~testoverlayfs SquashFS delta is installed 0.113
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.350
# 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.452
When the network is plugged 0.072
And Tor is ready 22.472
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 10.434
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.495
Given I shutdown Tails and wait for the computer to power off 8.001
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:23.975
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.478
And the file system changes introduced in version 6.3~testoverlayfs are present 1.030
And only the 6.3~testoverlayfs SquashFS delta is installed 0.100
# 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 0.457
When the network is plugged 0.073
And Tor is ready 23.498
Then the Upgrader considers the system as up-to-date 0.308
# 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 18.122
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.890
After features/support/hooks.rb:330 0.751
After features/support/hooks.rb:100 0.068
44.235
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 14.054
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.518
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
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.073
And Tor is ready 22.026
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.392
After features/support/hooks.rb:330 2.648
After features/support/hooks.rb:100 0.000