Project Number Date
test_Tails_ISO_test-suite-options 7 23 Jun 2025, 22:01

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 39:25.571 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
4:56.329
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.242
And I create a 7200 MiB disk named "old" 0.057
And I plug USB drive "old" 1.084
And I write an old version of the Tails USB image to disk "old" 1:16.000
When I start Tails from USB drive "old" with network unplugged 3:23.036
Then the boot device has safe access rights 13.616
And Tails is running from USB drive "old" 1.103
And there is no persistence partition on USB drive "old" 0.177
And process "udev-watchdog" is running 0.179
And udev-watchdog is monitoring the correct device 0.617
And I unplug USB drive "old" 0.213
After features/support/hooks.rb:330 3.914
After features/support/hooks.rb:100 0.059
Tags: @product
4:16.842
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.233
And I start Tails from USB drive "old" with network unplugged and I login 2:55.371
Then Tails is running from USB drive "old" 0.790
And I create a persistent partition 1:2.148
And I take note of which tps features are available 3.334
Then a Tails persistence partition exists on USB drive "old" 1.507
And I shutdown Tails and wait for the computer to power off 13.457
After features/support/hooks.rb:330 0.192
After features/support/hooks.rb:100 0.009
Tags: @product
6:20.909
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.244
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 4:58.025
Then Tails is running from USB drive "old" 0.607
And all tps features are active 2.418
When I write some files expected to persist 2.523
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.326
And all persistence configuration files have safe access rights 0.539
And all persistent directories from the old Tails version have safe access rights 13.146
And I take note of which tps features are available 0.539
And I shutdown Tails and wait for the computer to power off 7.167
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 55.369
After features/support/hooks.rb:330 0.159
After features/support/hooks.rb:100 0.024
Tags: @product
4:35.396
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 22.142
And I log in to a new session 40.125
And I clone USB drive "old" to a new USB drive "to_upgrade" 6.175
And I plug USB drive "to_upgrade" 10.379
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:19.498
Then the running Tails is installed on USB drive "to_upgrade" 54.207
And I unplug USB drive "to_upgrade" 2.419
And I unplug USB drive "__internal" 0.448
After features/support/hooks.rb:330 3.085
After features/support/hooks.rb:100 0.000
Tags: @product
4:5.092
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.187
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:42.327
Then all tps features from the old Tails version are active 3.075
And Tails is running from USB drive "to_upgrade" 1.637
And the boot device has safe access rights 12.354
And the expected persistent files created with the old Tails version are present in the filesystem 1.817
And all persistent directories from the old Tails version have safe access rights 3.692
After features/support/hooks.rb:330 1.135
After features/support/hooks.rb:100 0.109
Tags: @product @automatic_upgrade
13:55.138
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.047
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:22.735
And no SquashFS delta is installed 1.245
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 3.329
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.246
And the file system changes introduced in version 6.2~testoverlayfs are not present 1.074
And the file system changes introduced in version 6.3~testoverlayfs are not present 2.155
When the network is plugged 0.270
And Tor is ready 39.445
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.130
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 35.737
Given I shutdown Tails and wait for the computer to power off 20.867
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:45.033
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 5.964
And the file system changes introduced in version 6.2~testoverlayfs are present 4.854
And only the 6.2~testoverlayfs SquashFS delta is installed 0.481
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 1.092
# 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 1.166
When the network is plugged 0.124
And Tor is ready 59.666
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.467
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 20.582
Given I shutdown Tails and wait for the computer to power off 6.162
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:59.032
Then Tails is running version 6.3~testoverlayfs 0.024
And all tps features are active 10.209
And the file system changes introduced in version 6.3~testoverlayfs are present 2.234
And only the 6.3~testoverlayfs SquashFS delta is installed 0.465
# 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.693
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.584
When the network is plugged 0.095
And Tor is ready 35.123
Then the Upgrader considers the system as up-to-date 1.206
# 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 25.814
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.798
After features/support/hooks.rb:330 0.768
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
1:15.861
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 20.896
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.504
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.169
And the signing key used by the Upgrader is outdated 0.091
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 34.485
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 19.639
After features/support/hooks.rb:330 1.220
After features/support/hooks.rb:100 0.000