Project Number Date
test_Tails_ISO_stable 5535 27 Mar 2025, 13:09

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 20:7.741 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:18.974
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.213
And I create a 7200 MiB disk named "old" 0.062
And I plug USB drive "old" 1.079
And I write an old version of the Tails USB image to disk "old" 33.184
When I start Tails from USB drive "old" with network unplugged 1:39.812
Then the boot device has safe access rights 3.431
And Tails is running from USB drive "old" 0.390
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.368
And I unplug USB drive "old" 0.244
After features/support/hooks.rb:330 3.951
After features/support/hooks.rb:100 0.013
Tags: @product
2:14.046
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 1:31.604
Then Tails is running from USB drive "old" 0.447
And I create a persistent partition 32.002
And I take note of which tps features are available 1.934
Then a Tails persistence partition exists on USB drive "old" 0.889
And I shutdown Tails and wait for the computer to power off 6.975
After features/support/hooks.rb:330 0.194
After features/support/hooks.rb:100 0.021
Tags: @product
2:57.976
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.554
Then Tails is running from USB drive "old" 0.618
And all tps features are active 1.999
When I write some files expected to persist 2.026
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.262
And all persistence configuration files have safe access rights 0.413
And all persistent directories from the old Tails version have safe access rights 2.886
And I take note of which tps features are available 0.537
And I shutdown Tails and wait for the computer to power off 4.298
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.161
After features/support/hooks.rb:330 0.108
After features/support/hooks.rb:100 0.010
Tags: @product
2:45.165
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 17.294
And I log in to a new session 19.391
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.095
And I plug USB drive "to_upgrade" 2.434
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.592
Then the running Tails is installed on USB drive "to_upgrade" 27.911
And I unplug USB drive "to_upgrade" 0.231
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:330 2.083
After features/support/hooks.rb:100 0.000
Tags: @product
2:29.588
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.177
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:19.244
Then all tps features from the old Tails version are active 1.661
And Tails is running from USB drive "to_upgrade" 0.394
And the boot device has safe access rights 3.819
And the expected persistent files created with the old Tails version are present in the filesystem 1.550
And all persistent directories from the old Tails version have safe access rights 2.742
After features/support/hooks.rb:330 1.495
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:46.828
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.216
And no SquashFS delta is installed 0.098
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.393
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.245
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.580
When the network is plugged 0.078
And Tor is ready 19.963
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.519
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.233
Given I shutdown Tails and wait for the computer to power off 11.681
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.735
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.101
And the file system changes introduced in version 6.2~testoverlayfs are present 0.355
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.365
# 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.310
When the network is plugged 0.076
And Tor is ready 20.701
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.264
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.105
Given I shutdown Tails and wait for the computer to power off 4.389
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.670
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.105
And the file system changes introduced in version 6.3~testoverlayfs are present 0.557
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.348
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.284
When the network is plugged 0.062
And Tor is ready 20.936
Then the Upgrader considers the system as up-to-date 0.325
# 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.130
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.760
After features/support/hooks.rb:330 1.010
After features/support/hooks.rb:100 0.034
Tags: @product @automatic_upgrade
35.162
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 10.107
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.525
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.076
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 17.394
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.923
After features/support/hooks.rb:330 0.836
After features/support/hooks.rb:100 0.000