Project Number Date
test_Tails_ISO_stable 5722 18 Jun 2025, 15:32

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:21.476 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:34.121
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given a computer 0.273
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 39.992
When I start Tails from USB drive "old" with network unplugged 1:45.729
Then the boot device has safe access rights 5.697
And Tails is running from USB drive "old" 0.504
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.463
And I unplug USB drive "old" 0.220
After features/support/hooks.rb:330 11.635
After features/support/hooks.rb:100 0.017
Tags: @product
2:35.454
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given a computer 0.363
And I start Tails from USB drive "old" with network unplugged and I login 1:43.228
Then Tails is running from USB drive "old" 1.689
And I create a persistent partition 36.003
And I take note of which tps features are available 2.802
Then a Tails persistence partition exists on USB drive "old" 2.401
And I shutdown Tails and wait for the computer to power off 8.967
After features/support/hooks.rb:330 0.197
After features/support/hooks.rb:100 0.009
Tags: @product
3:31.588
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:41.847
Then Tails is running from USB drive "old" 0.535
And all tps features are active 2.807
When I write some files expected to persist 2.142
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.230
And all persistence configuration files have safe access rights 1.052
And all persistent directories from the old Tails version have safe access rights 4.562
And I take note of which tps features are available 0.644
And I shutdown Tails and wait for the computer to power off 6.570
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 31.007
After features/support/hooks.rb:330 0.497
After features/support/hooks.rb:100 0.015
Tags: @product
3:1.772
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.705
And I log in to a new session 22.810
And I clone USB drive "old" to a new USB drive "to_upgrade" 4.096
And I plug USB drive "to_upgrade" 3.212
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.159
Then the running Tails is installed on USB drive "to_upgrade" 34.193
And I unplug USB drive "to_upgrade" 0.339
And I unplug USB drive "__internal" 0.255
After features/support/hooks.rb:330 1.147
After features/support/hooks.rb:100 0.000
Tags: @product
2:44.743
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.278
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:30.632
Then all tps features from the old Tails version are active 2.959
And Tails is running from USB drive "to_upgrade" 2.025
And the boot device has safe access rights 4.005
And the expected persistent files created with the old Tails version are present in the filesystem 1.816
And all persistent directories from the old Tails version have safe access rights 3.025
After features/support/hooks.rb:330 1.274
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
9:5.363
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 15.722
And no SquashFS delta is installed 0.100
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.743
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.534
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.512
When the network is plugged 0.069
And Tor is ready 25.190
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.928
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 15.760
Given I shutdown Tails and wait for the computer to power off 1:30.693
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:28.864
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 4.692
And the file system changes introduced in version 6.2~testoverlayfs are present 0.555
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.371
# 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.368
When the network is plugged 0.069
And Tor is ready 22.836
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.659
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 13.845
Given I shutdown Tails and wait for the computer to power off 6.689
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.839
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 3.126
And the file system changes introduced in version 6.3~testoverlayfs are present 0.618
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.287
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.398
When the network is plugged 0.069
And Tor is ready 23.104
Then the Upgrader considers the system as up-to-date 0.328
# 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.731
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.420
After features/support/hooks.rb:330 0.719
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
48.431
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 14.753
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.278
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
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.070
And Tor is ready 28.510
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.688
After features/support/hooks.rb:330 1.788
After features/support/hooks.rb:100 0.000