Project Number Date
test_Tails_ISO_stable 5478 23 Feb 2025, 12:28

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 19:45.997 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:2.132
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.188
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 31.270
When I start Tails from USB drive "old" with network unplugged 1:25.576
Then the boot device has safe access rights 2.972
And Tails is running from USB drive "old" 0.318
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.313
And I unplug USB drive "old" 0.215
After features/support/hooks.rb:330 3.539
After features/support/hooks.rb:100 0.008
Tags: @product
2:11.992
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 1:27.927
Then Tails is running from USB drive "old" 0.334
And I create a persistent partition 32.808
And I take note of which tps features are available 1.427
Then a Tails persistence partition exists on USB drive "old" 0.879
And I shutdown Tails and wait for the computer to power off 8.428
After features/support/hooks.rb:330 0.187
After features/support/hooks.rb:100 0.009
Tags: @product
2:56.411
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.242
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.927
Then Tails is running from USB drive "old" 0.367
And all tps features are active 1.890
When I write some files expected to persist 2.290
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.229
And all persistence configuration files have safe access rights 0.398
And all persistent directories from the old Tails version have safe access rights 2.510
And I take note of which tps features are available 0.410
And I shutdown Tails and wait for the computer to power off 4.489
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.653
After features/support/hooks.rb:330 0.138
After features/support/hooks.rb:100 0.011
Tags: @product
2:32.078
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 10.454
And I log in to a new session 17.514
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.747
And I plug USB drive "to_upgrade" 2.361
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.702
Then the running Tails is installed on USB drive "to_upgrade" 24.861
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.224
After features/support/hooks.rb:330 1.153
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.271
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.227
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.814
Then all tps features from the old Tails version are active 1.646
And Tails is running from USB drive "to_upgrade" 0.330
And the boot device has safe access rights 3.242
And the expected persistent files created with the old Tails version are present in the filesystem 1.564
And all persistent directories from the old Tails version have safe access rights 2.444
After features/support/hooks.rb:330 1.461
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
7:4.643
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.024
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 27.690
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.368
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.116
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.395
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.442
When the network is plugged 0.072
And Tor is ready 49.841
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.608
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.682
Given I shutdown Tails and wait for the computer to power off 8.847
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.354
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.286
And the file system changes introduced in version 6.2~testoverlayfs are present 0.350
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.322
# 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.296
When the network is plugged 0.090
And Tor is ready 21.268
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.735
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.107
Given I shutdown Tails and wait for the computer to power off 4.515
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.854
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.060
And the file system changes introduced in version 6.3~testoverlayfs are present 0.490
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.333
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.301
When the network is plugged 0.076
And Tor is ready 17.573
Then the Upgrader considers the system as up-to-date 0.306
# 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.832
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.143
After features/support/hooks.rb:330 0.700
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
36.467
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 9.365
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.326
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.072
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 21.628
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.933
After features/support/hooks.rb:330 0.717
After features/support/hooks.rb:100 0.000