Project Number Date
test_Tails_ISO_20979-pdfarranger 4 30 May 2025, 02:37

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:34.409 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:10.608
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.187
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.064
And I write an old version of the Tails USB image to disk "old" 30.397
When I start Tails from USB drive "old" with network unplugged 1:34.633
Then the boot device has safe access rights 3.229
And Tails is running from USB drive "old" 0.342
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.348
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:330 3.712
After features/support/hooks.rb:100 0.007
Tags: @product
2:9.888
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.226
And I start Tails from USB drive "old" with network unplugged and I login 1:24.716
Then Tails is running from USB drive "old" 0.356
And I create a persistent partition 32.993
And I take note of which tps features are available 1.872
Then a Tails persistence partition exists on USB drive "old" 0.861
And I shutdown Tails and wait for the computer to power off 8.862
After features/support/hooks.rb:330 0.308
After features/support/hooks.rb:100 0.011
Tags: @product
3:2.739
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.487
Then Tails is running from USB drive "old" 0.469
And all tps features are active 4.100
When I write some files expected to persist 1.890
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.243
And all persistence configuration files have safe access rights 0.456
And all persistent directories from the old Tails version have safe access rights 2.823
And I take note of which tps features are available 1.029
And I shutdown Tails and wait for the computer to power off 6.453
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.559
After features/support/hooks.rb:330 0.151
After features/support/hooks.rb:100 0.010
Tags: @product
2:32.371
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.759
And I log in to a new session 18.461
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.695
And I plug USB drive "to_upgrade" 2.440
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.650
Then the running Tails is installed on USB drive "to_upgrade" 23.922
And I unplug USB drive "to_upgrade" 0.233
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:330 0.906
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.675
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.222
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.498
Then all tps features from the old Tails version are active 1.604
And Tails is running from USB drive "to_upgrade" 0.300
And the boot device has safe access rights 3.010
And the expected persistent files created with the old Tails version are present in the filesystem 1.563
And all persistent directories from the old Tails version have safe access rights 2.475
After features/support/hooks.rb:330 1.402
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:42.882
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 with a persistent partition enabled and logged in 12.796
And no SquashFS delta is installed 0.197
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.077
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.277
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.421
When the network is plugged 0.085
And Tor is ready 23.214
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.795
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.273
Given I shutdown Tails and wait for the computer to power off 8.717
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.276
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.391
And the file system changes introduced in version 6.2~testoverlayfs are present 0.329
And only the 6.2~testoverlayfs SquashFS delta is installed 0.095
# 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.294
When the network is plugged 0.064
And Tor is ready 20.859
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.729
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.713
Given I shutdown Tails and wait for the computer to power off 4.537
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.350
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 1.973
And the file system changes introduced in version 6.3~testoverlayfs are present 0.468
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.350
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.353
When the network is plugged 0.071
And Tor is ready 19.078
Then the Upgrader considers the system as up-to-date 0.328
# 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.885
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.837
After features/support/hooks.rb:330 0.822
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
40.242
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.272
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.270
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.065
But a current signing key is available on our website 0.000
When the network is plugged 0.082
And Tor is ready 21.647
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.844
After features/support/hooks.rb:330 0.706
After features/support/hooks.rb:100 0.000