Project Number Date
test_Tails_ISO_20979-pdfarranger 2 29 May 2025, 01:26

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 20:28.984 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:39.362
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 39.118
When I start Tails from USB drive "old" with network unplugged 1:54.549
Then the boot device has safe access rights 3.310
And Tails is running from USB drive "old" 0.317
And there is no persistence partition on USB drive "old" 0.087
And process "udev-watchdog" is running 0.111
And udev-watchdog is monitoring the correct device 0.348
And I unplug USB drive "old" 0.222
After features/support/hooks.rb:330 7.005
After features/support/hooks.rb:100 0.011
Tags: @product
2:5.701
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login 1:24.267
Then Tails is running from USB drive "old" 0.386
And I create a persistent partition 31.196
And I take note of which tps features are available 2.532
Then a Tails persistence partition exists on USB drive "old" 0.759
And I shutdown Tails and wait for the computer to power off 6.361
After features/support/hooks.rb:330 0.163
After features/support/hooks.rb:100 0.009
Tags: @product
3:3.168
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.091
Then Tails is running from USB drive "old" 0.329
And all tps features are active 2.049
When I write some files expected to persist 1.692
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.228
And all persistence configuration files have safe access rights 0.407
And all persistent directories from the old Tails version have safe access rights 2.880
And I take note of which tps features are available 0.496
And I shutdown Tails and wait for the computer to power off 4.511
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.290
After features/support/hooks.rb:330 0.127
After features/support/hooks.rb:100 0.012
Tags: @product
2:41.414
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 11.886
And I log in to a new session 20.616
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.631
And I plug USB drive "to_upgrade" 2.604
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.257
Then the running Tails is installed on USB drive "to_upgrade" 26.964
And I unplug USB drive "to_upgrade" 0.235
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:330 3.575
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.681
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.193
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.812
Then all tps features from the old Tails version are active 1.678
And Tails is running from USB drive "to_upgrade" 0.287
And the boot device has safe access rights 3.589
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.584
After features/support/hooks.rb:330 1.064
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:59.573
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 12.507
And no SquashFS delta is installed 0.101
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.615
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.311
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.493
When the network is plugged 0.069
And Tor is ready 24.450
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.563
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.698
Given I shutdown Tails and wait for the computer to power off 8.618
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.445
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.243
And the file system changes introduced in version 6.2~testoverlayfs are present 0.340
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.298
# 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.419
When the network is plugged 0.095
And Tor is ready 48.226
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.617
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.898
Given I shutdown Tails and wait for the computer to power off 4.290
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.236
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.052
And the file system changes introduced in version 6.3~testoverlayfs are present 0.510
And only the 6.3~testoverlayfs SquashFS delta is installed 0.091
# 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.289
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.284
When the network is plugged 0.065
And Tor is ready 17.690
Then the Upgrader considers the system as up-to-date 0.322
# 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.861
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.707
After features/support/hooks.rb:330 0.767
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
38.082
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.297
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.590
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.081
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 17.987
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.989
After features/support/hooks.rb:330 0.652
After features/support/hooks.rb:100 0.000