Project Number Date
test_Tails_ISO_improved-new-identity-scenario 14 13 May 2025, 13:52

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:52.618 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:11.723
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.175
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 33.016
When I start Tails from USB drive "old" with network unplugged 1:33.025
Then the boot device has safe access rights 3.315
And Tails is running from USB drive "old" 0.349
And there is no persistence partition on USB drive "old" 0.091
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.337
And I unplug USB drive "old" 0.217
After features/support/hooks.rb:330 3.806
After features/support/hooks.rb:100 0.008
Tags: @product
2:12.651
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login 1:26.613
Then Tails is running from USB drive "old" 0.341
And I create a persistent partition 34.556
And I take note of which tps features are available 1.726
Then a Tails persistence partition exists on USB drive "old" 0.789
And I shutdown Tails and wait for the computer to power off 8.443
After features/support/hooks.rb:330 0.165
After features/support/hooks.rb:100 0.009
Tags: @product
2:56.734
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.164
Then Tails is running from USB drive "old" 0.357
And all tps features are active 1.977
When I write some files expected to persist 1.927
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.236
And all persistence configuration files have safe access rights 0.386
And all persistent directories from the old Tails version have safe access rights 2.517
And I take note of which tps features are available 0.824
And I shutdown Tails and wait for the computer to power off 4.822
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.316
After features/support/hooks.rb:330 0.148
After features/support/hooks.rb:100 0.009
Tags: @product
2:39.029
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 without a persistent partition and stopped at Tails Greeter's login screen 11.306
And I log in to a new session 21.507
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.145
And I plug USB drive "to_upgrade" 2.434
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.250
Then the running Tails is installed on USB drive "to_upgrade" 25.942
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.237
After features/support/hooks.rb:330 1.884
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.274
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.175
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.270
Then all tps features from the old Tails version are active 1.734
And Tails is running from USB drive "to_upgrade" 0.343
And the boot device has safe access rights 3.665
And the expected persistent files created with the old Tails version are present in the filesystem 1.585
And all persistent directories from the old Tails version have safe access rights 2.500
After features/support/hooks.rb:330 1.365
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:53.564
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 11.356
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.380
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.304
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.810
When the network is plugged 0.090
And Tor is ready 20.980
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.401
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.078
Given I shutdown Tails and wait for the computer to power off 8.711
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.682
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 2.152
And the file system changes introduced in version 6.2~testoverlayfs are present 0.292
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.331
# 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.351
When the network is plugged 0.069
And Tor is ready 17.691
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.214
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.552
Given I shutdown Tails and wait for the computer to power off 6.461
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.851
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.226
And the file system changes introduced in version 6.3~testoverlayfs are present 0.523
And only the 6.3~testoverlayfs SquashFS delta is installed 0.107
# 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.294
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.264
When the network is plugged 0.066
And Tor is ready 21.647
Then the Upgrader considers the system as up-to-date 0.301
# 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.579
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.514
After features/support/hooks.rb:330 0.720
After features/support/hooks.rb:100 0.031
Tags: @product @automatic_upgrade
40.640
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.322
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.333
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.102
But a current signing key is available on our website 0.000
When the network is plugged 0.104
And Tor is ready 21.622
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.090
After features/support/hooks.rb:330 0.716
After features/support/hooks.rb:100 0.000