Project Number Date
test_Tails_ISO_devel 3760 29 Mar 2025, 13:22

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 21:16.804 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:51.211
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.270
And I create a 7200 MiB disk named "old" 0.059
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 38.922
When I start Tails from USB drive "old" with network unplugged 2:6.621
Then the boot device has safe access rights 3.235
And Tails is running from USB drive "old" 0.326
And there is no persistence partition on USB drive "old" 0.088
And process "udev-watchdog" is running 0.112
And udev-watchdog is monitoring the correct device 0.324
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:330 3.537
After features/support/hooks.rb:100 0.068
Tags: @product
2:19.010
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login 1:33.703
Then Tails is running from USB drive "old" 0.365
And I create a persistent partition 33.341
And I take note of which tps features are available 1.816
Then a Tails persistence partition exists on USB drive "old" 0.961
And I shutdown Tails and wait for the computer to power off 8.615
After features/support/hooks.rb:330 0.194
After features/support/hooks.rb:100 0.008
Tags: @product
3:10.494
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.221
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:28.202
Then Tails is running from USB drive "old" 0.379
And all tps features are active 2.495
When I write some files expected to persist 3.436
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.237
And all persistence configuration files have safe access rights 0.760
And all persistent directories from the old Tails version have safe access rights 2.687
And I take note of which tps features are available 0.514
And I shutdown Tails and wait for the computer to power off 6.706
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.850
After features/support/hooks.rb:330 0.106
After features/support/hooks.rb:100 0.008
Tags: @product
2:47.317
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.099
And I log in to a new session 24.313
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.376
And I plug USB drive "to_upgrade" 2.513
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.630
Then the running Tails is installed on USB drive "to_upgrade" 27.889
And I unplug USB drive "to_upgrade" 0.224
And I unplug USB drive "__internal" 0.270
After features/support/hooks.rb:330 1.188
After features/support/hooks.rb:100 0.000
Tags: @product
2:35.712
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:24.489
Then all tps features from the old Tails version are active 1.758
And Tails is running from USB drive "to_upgrade" 0.450
And the boot device has safe access rights 4.122
And the expected persistent files created with the old Tails version are present in the filesystem 1.756
And all persistent directories from the old Tails version have safe access rights 2.942
After features/support/hooks.rb:330 2.005
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
6:52.498
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.230
And no SquashFS delta is installed 0.421
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.402
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.112
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.422
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.493
When the network is plugged 0.082
And Tor is ready 23.738
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.337
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.264
Given I shutdown Tails and wait for the computer to power off 9.134
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.780
Then Tails is running version 6.2~testoverlayfs 0.028
And all tps features are active 2.411
And the file system changes introduced in version 6.2~testoverlayfs are present 0.379
And only the 6.2~testoverlayfs SquashFS delta is installed 0.090
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.300
# 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.329
When the network is plugged 0.095
And Tor is ready 21.266
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.925
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.808
Given I shutdown Tails and wait for the computer to power off 4.464
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.039
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.335
And the file system changes introduced in version 6.3~testoverlayfs are present 0.594
And only the 6.3~testoverlayfs SquashFS delta is installed 0.102
# 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.375
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.305
When the network is plugged 0.076
And Tor is ready 19.230
Then the Upgrader considers the system as up-to-date 0.380
# 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 16.274
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.246
After features/support/hooks.rb:330 0.790
After features/support/hooks.rb:100 0.027
Tags: @product @automatic_upgrade
40.559
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.884
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.094
And the signing key used by the Upgrader is outdated 0.103
But a current signing key is available on our website 0.000
When the network is plugged 0.081
And Tor is ready 21.779
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.129
After features/support/hooks.rb:330 1.992
After features/support/hooks.rb:100 0.000