Project Number Date
test_Tails_ISO_improved-new-identity-scenario 9 08 May 2025, 13:27

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:45.336 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:7.115
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.163
And I create a 7200 MiB disk named "old" 0.035
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 30.392
When I start Tails from USB drive "old" with network unplugged 1:31.392
Then the boot device has safe access rights 3.072
And Tails is running from USB drive "old" 0.357
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.300
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:330 7.132
After features/support/hooks.rb:100 0.007
Tags: @product
2:10.780
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login 1:27.336
Then Tails is running from USB drive "old" 0.349
And I create a persistent partition 32.066
And I take note of which tps features are available 1.769
Then a Tails persistence partition exists on USB drive "old" 0.734
And I shutdown Tails and wait for the computer to power off 8.349
After features/support/hooks.rb:330 0.214
After features/support/hooks.rb:100 0.008
Tags: @product
2:51.688
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.606
Then Tails is running from USB drive "old" 0.504
And all tps features are active 1.952
When I write some files expected to persist 1.669
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.231
And all persistence configuration files have safe access rights 0.390
And all persistent directories from the old Tails version have safe access rights 2.724
And I take note of which tps features are available 0.385
And I shutdown Tails and wait for the computer to power off 4.322
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.709
After features/support/hooks.rb:330 0.134
After features/support/hooks.rb:100 0.009
Tags: @product
2:31.686
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.531
And I log in to a new session 20.975
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.876
And I plug USB drive "to_upgrade" 2.521
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.181
Then the running Tails is installed on USB drive "to_upgrade" 21.188
And I unplug USB drive "to_upgrade" 0.199
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:330 1.737
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.216
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.171
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.733
Then all tps features from the old Tails version are active 1.651
And Tails is running from USB drive "to_upgrade" 0.389
And the boot device has safe access rights 3.321
And the expected persistent files created with the old Tails version are present in the filesystem 1.406
And all persistent directories from the old Tails version have safe access rights 2.543
After features/support/hooks.rb:330 1.445
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:59.723
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 25.459
And no SquashFS delta is installed 0.125
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.275
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.349
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.882
When the network is plugged 0.090
And Tor is ready 22.839
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.826
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.968
Given I shutdown Tails and wait for the computer to power off 8.582
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.118
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.563
And the file system changes introduced in version 6.2~testoverlayfs are present 0.435
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.315
# 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.280
When the network is plugged 0.064
And Tor is ready 18.667
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.377
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.499
Given I shutdown Tails and wait for the computer to power off 1:3.042
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.625
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.162
And the file system changes introduced in version 6.3~testoverlayfs are present 0.539
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.334
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.321
When the network is plugged 0.089
And Tor is ready 19.669
Then the Upgrader considers the system as up-to-date 0.319
# 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.539
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.097
After features/support/hooks.rb:330 0.693
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
39.125
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 9.600
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.311
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the signing key used by the Upgrader is outdated 0.112
But a current signing key is available on our website 0.000
When the network is plugged 0.124
And Tor is ready 20.826
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.070
After features/support/hooks.rb:330 0.787
After features/support/hooks.rb:100 0.000