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

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 22:15.924 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:19.717
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.469
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 33.875
When I start Tails from USB drive "old" with network unplugged 1:40.256
Then the boot device has safe access rights 3.001
And Tails is running from USB drive "old" 0.327
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.316
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:330 3.833
After features/support/hooks.rb:100 0.023
Tags: @product
2:27.023
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.408
And I start Tails from USB drive "old" with network unplugged and I login 1:40.919
Then Tails is running from USB drive "old" 0.428
And I create a persistent partition 33.796
And I take note of which tps features are available 1.928
Then a Tails persistence partition exists on USB drive "old" 0.874
And I shutdown Tails and wait for the computer to power off 8.668
After features/support/hooks.rb:330 0.199
After features/support/hooks.rb:100 0.008
Tags: @product
3:3.601
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.258
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.424
Then Tails is running from USB drive "old" 0.951
And all tps features are active 2.386
When I write some files expected to persist 2.357
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.488
And all persistence configuration files have safe access rights 0.379
And all persistent directories from the old Tails version have safe access rights 3.177
And I take note of which tps features are available 0.465
And I shutdown Tails and wait for the computer to power off 6.944
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.766
After features/support/hooks.rb:330 0.130
After features/support/hooks.rb:100 0.010
Tags: @product
2:40.877
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.247
And I log in to a new session 20.829
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.896
And I plug USB drive "to_upgrade" 2.560
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.929
Then the running Tails is installed on USB drive "to_upgrade" 25.873
And I unplug USB drive "to_upgrade" 0.229
And I unplug USB drive "__internal" 0.310
After features/support/hooks.rb:330 6.909
After features/support/hooks.rb:100 0.000
Tags: @product
2:33.457
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:21.028
Then all tps features from the old Tails version are active 2.786
And Tails is running from USB drive "to_upgrade" 0.407
And the boot device has safe access rights 4.164
And the expected persistent files created with the old Tails version are present in the filesystem 1.921
And all persistent directories from the old Tails version have safe access rights 2.951
After features/support/hooks.rb:330 1.576
After features/support/hooks.rb:100 0.010
8:22.721
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 27.494
And no SquashFS delta is installed 0.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.386
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.114
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.451
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.476
When the network is plugged 0.080
And Tor is ready 23.164
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 10.411
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.827
Given I shutdown Tails and wait for the computer to power off 11.651
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:23.588
Then Tails is running version 6.2~testoverlayfs 0.029
And all tps features are active 2.781
And the file system changes introduced in version 6.2~testoverlayfs are present 0.446
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.360
# 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.089
And Tor is ready 21.225
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.656
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.732
Given I shutdown Tails and wait for the computer to power off 4.786
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:27.035
Then Tails is running version 6.3~testoverlayfs 0.022
And all tps features are active 2.467
And the file system changes introduced in version 6.3~testoverlayfs are present 0.571
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.323
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.323
When the network is plugged 0.084
And Tor is ready 48.840
Then the Upgrader considers the system as up-to-date 0.372
# 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.123
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.200
After features/support/hooks.rb:330 1.120
After features/support/hooks.rb:100 0.019
48.524
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 14.970
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.371
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.084
But a current signing key is available on our website 0.000
When the network is plugged 0.121
And Tor is ready 22.123
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 10.795
After features/support/hooks.rb:330 1.393
After features/support/hooks.rb:100 0.000