Project Number Date
test_Tails_ISO_stable 5528 24 Mar 2025, 13:05

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:14.324 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:11.496
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.214
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 36.243
When I start Tails from USB drive "old" with network unplugged 1:29.932
Then the boot device has safe access rights 2.927
And Tails is running from USB drive "old" 0.335
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.113
And udev-watchdog is monitoring the correct device 0.352
And I unplug USB drive "old" 0.205
After features/support/hooks.rb:330 3.687
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.436
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login 1:23.080
Then Tails is running from USB drive "old" 0.377
And I create a persistent partition 30.923
And I take note of which tps features are available 2.530
Then a Tails persistence partition exists on USB drive "old" 0.869
And I shutdown Tails and wait for the computer to power off 8.455
After features/support/hooks.rb:330 0.143
After features/support/hooks.rb:100 0.013
Tags: @product
3:12.582
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.433
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:31.846
Then Tails is running from USB drive "old" 0.478
And all tps features are active 2.674
When I write some files expected to persist 1.952
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.270
And all persistence configuration files have safe access rights 0.443
And all persistent directories from the old Tails version have safe access rights 2.897
And I take note of which tps features are available 0.656
And I shutdown Tails and wait for the computer to power off 4.139
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.787
After features/support/hooks.rb:330 0.174
After features/support/hooks.rb:100 0.011
Tags: @product
2:57.254
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 without a persistent partition and stopped at Tails Greeter's login screen 23.002
And I log in to a new session 21.091
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.749
And I plug USB drive "to_upgrade" 2.595
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.134
Then the running Tails is installed on USB drive "to_upgrade" 26.218
And I unplug USB drive "to_upgrade" 0.229
And I unplug USB drive "__internal" 0.233
After features/support/hooks.rb:330 2.695
After features/support/hooks.rb:100 0.000
Tags: @product
2:51.716
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.253
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:38.553
Then all tps features from the old Tails version are active 3.676
And Tails is running from USB drive "to_upgrade" 0.367
And the boot device has safe access rights 3.680
And the expected persistent files created with the old Tails version are present in the filesystem 1.642
And all persistent directories from the old Tails version have safe access rights 3.543
After features/support/hooks.rb:330 1.925
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:14.565
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 29.117
And no SquashFS delta is installed 0.096
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.628
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.145
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.434
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.532
When the network is plugged 0.145
And Tor is ready 23.476
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.041
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.764
Given I shutdown Tails and wait for the computer to power off 12.807
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:20.806
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.213
And the file system changes introduced in version 6.2~testoverlayfs are present 0.415
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.279
# 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.256
When the network is plugged 0.109
And Tor is ready 20.182
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.466
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.064
Given I shutdown Tails and wait for the computer to power off 4.408
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.273
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.759
And the file system changes introduced in version 6.3~testoverlayfs are present 0.520
And only the 6.3~testoverlayfs SquashFS delta is installed 0.084
# 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.328
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.281
When the network is plugged 0.092
And Tor is ready 18.273
Then the Upgrader considers the system as up-to-date 0.342
# 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.096
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.018
After features/support/hooks.rb:330 0.753
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
40.273
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.525
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.339
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
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.066
And Tor is ready 22.743
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.477
After features/support/hooks.rb:330 0.924
After features/support/hooks.rb:100 0.000