Project Number Date
test_Tails_ISO_stable 5460 15 Feb 2025, 12:51

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:54.097 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:14.286
Before features/support/hooks.rb:269 0.005
Given a computer 0.274
And I create a 7200 MiB disk named "old" 0.076
And I plug USB drive "old" 1.062
And I write an old version of the Tails USB image to disk "old" 30.105
When I start Tails from USB drive "old" with network unplugged 1:38.621
Then the boot device has safe access rights 3.193
And Tails is running from USB drive "old" 0.293
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.310
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:326 6.964
After features/support/hooks.rb:100 0.007
Tags: @product
2:8.554
Before features/support/hooks.rb:269 0.003
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login 1:25.478
Then Tails is running from USB drive "old" 0.346
And I create a persistent partition 32.092
And I take note of which tps features are available 1.423
Then a Tails persistence partition exists on USB drive "old" 0.808
And I shutdown Tails and wait for the computer to power off 8.223
After features/support/hooks.rb:326 0.218
After features/support/hooks.rb:100 0.007
Tags: @product
3:5.148
Before features/support/hooks.rb:269 0.004
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.571
Then Tails is running from USB drive "old" 0.506
And all tps features are active 2.063
When I write some files expected to persist 1.829
# 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.426
And all persistent directories from the old Tails version have safe access rights 2.741
And I take note of which tps features are available 0.474
And I shutdown Tails and wait for the computer to power off 4.401
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.697
After features/support/hooks.rb:326 0.120
After features/support/hooks.rb:100 0.008
Tags: @product
2:27.908
Before features/support/hooks.rb:269 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.449
And I log in to a new session 18.349
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.949
And I plug USB drive "to_upgrade" 2.543
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.508
Then the running Tails is installed on USB drive "to_upgrade" 18.647
And I unplug USB drive "to_upgrade" 0.249
And I unplug USB drive "__internal" 0.210
After features/support/hooks.rb:326 8.105
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.123
Before features/support/hooks.rb:269 0.005
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.555
Then all tps features from the old Tails version are active 1.733
And Tails is running from USB drive "to_upgrade" 0.331
And the boot device has safe access rights 3.351
And the expected persistent files created with the old Tails version are present in the filesystem 1.535
And all persistent directories from the old Tails version have safe access rights 2.421
After features/support/hooks.rb:326 0.984
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
6:14.355
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.409
And no SquashFS delta is installed 0.102
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.551
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.352
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.505
When the network is plugged 0.087
And Tor is ready 20.972
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.978
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.489
Given I shutdown Tails and wait for the computer to power off 8.600
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.889
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.191
And the file system changes introduced in version 6.2~testoverlayfs are present 0.311
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.325
# 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.326
When the network is plugged 0.062
And Tor is ready 16.960
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.353
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.485
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:59.388
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.058
And the file system changes introduced in version 6.3~testoverlayfs are present 0.493
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.366
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.305
When the network is plugged 0.070
And Tor is ready 19.733
Then the Upgrader considers the system as up-to-date 0.295
# 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 14.985
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.187
After features/support/hooks.rb:326 0.753
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
33.719
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.470
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.293
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the signing key used by the Upgrader is outdated 0.079
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 17.607
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.118
After features/support/hooks.rb:326 0.714
After features/support/hooks.rb:100 0.000