Project Number Date
test_Tails_ISO_stable 5670 22 May 2025, 12:34

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 18:41.712 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:0.572
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.169
And I create a 7200 MiB disk named "old" 0.036
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 30.924
When I start Tails from USB drive "old" with network unplugged 1:24.487
Then the boot device has safe access rights 2.948
And Tails is running from USB drive "old" 0.322
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.080
And udev-watchdog is monitoring the correct device 0.274
And I unplug USB drive "old" 0.206
After features/support/hooks.rb:330 7.111
After features/support/hooks.rb:100 0.008
Tags: @product
2:4.130
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.169
And I start Tails from USB drive "old" with network unplugged and I login 1:21.281
Then Tails is running from USB drive "old" 0.293
And I create a persistent partition 31.742
And I take note of which tps features are available 1.626
Then a Tails persistence partition exists on USB drive "old" 0.730
And I shutdown Tails and wait for the computer to power off 8.286
After features/support/hooks.rb:330 0.176
After features/support/hooks.rb:100 0.009
Tags: @product
2:46.708
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.341
Then Tails is running from USB drive "old" 0.372
And all tps features are active 1.914
When I write some files expected to persist 1.546
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.203
And all persistence configuration files have safe access rights 0.412
And all persistent directories from the old Tails version have safe access rights 2.298
And I take note of which tps features are available 0.364
And I shutdown Tails and wait for the computer to power off 4.290
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.778
After features/support/hooks.rb:330 0.153
After features/support/hooks.rb:100 0.008
Tags: @product
2:27.147
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.306
And I log in to a new session 18.295
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.778
And I plug USB drive "to_upgrade" 2.381
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.904
Then the running Tails is installed on USB drive "to_upgrade" 20.083
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.191
After features/support/hooks.rb:330 2.425
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.889
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.172
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.841
Then all tps features from the old Tails version are active 1.611
And Tails is running from USB drive "to_upgrade" 0.327
And the boot device has safe access rights 3.263
And the expected persistent files created with the old Tails version are present in the filesystem 1.339
And all persistent directories from the old Tails version have safe access rights 2.333
After features/support/hooks.rb:330 1.243
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:38.110
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.658
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.497
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.258
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.407
When the network is plugged 0.065
And Tor is ready 24.619
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.868
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.038
Given I shutdown Tails and wait for the computer to power off 8.398
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.084
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.036
And the file system changes introduced in version 6.2~testoverlayfs are present 0.347
And only the 6.2~testoverlayfs SquashFS delta is installed 0.094
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.297
# 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.309
When the network is plugged 0.070
And Tor is ready 19.696
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.285
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.755
Given I shutdown Tails and wait for the computer to power off 4.276
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.941
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.764
And the file system changes introduced in version 6.3~testoverlayfs are present 0.473
And only the 6.3~testoverlayfs SquashFS delta is installed 0.083
# 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.286
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.234
When the network is plugged 0.066
And Tor is ready 46.496
Then the Upgrader considers the system as up-to-date 0.353
# 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.530
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.653
After features/support/hooks.rb:330 0.675
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
35.153
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 9.875
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.487
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.075
But a current signing key is available on our website 0.000
When the network is plugged 0.063
And Tor is ready 16.816
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.784
After features/support/hooks.rb:330 1.329
After features/support/hooks.rb:100 0.000