Project Number Date
test_Tails_ISO_tca-misc-improvements 13 20 Apr 2025, 18:01

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:37.651 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:29.798
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.335
And I create a 7200 MiB disk named "old" 0.094
And I plug USB drive "old" 1.066
And I write an old version of the Tails USB image to disk "old" 59.136
When I start Tails from USB drive "old" with network unplugged 1:25.143
Then the boot device has safe access rights 3.053
And Tails is running from USB drive "old" 0.313
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.275
And I unplug USB drive "old" 0.208
After features/support/hooks.rb:330 6.988
After features/support/hooks.rb:100 0.009
Tags: @product
2:7.958
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 "old" with network unplugged and I login 1:24.456
Then Tails is running from USB drive "old" 0.337
And I create a persistent partition 32.304
And I take note of which tps features are available 1.601
Then a Tails persistence partition exists on USB drive "old" 0.830
And I shutdown Tails and wait for the computer to power off 8.200
After features/support/hooks.rb:330 0.187
After features/support/hooks.rb:100 0.009
Tags: @product
2:57.302
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.827
Then Tails is running from USB drive "old" 0.329
And all tps features are active 1.932
When I write some files expected to persist 1.666
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.212
And all persistence configuration files have safe access rights 0.353
And all persistent directories from the old Tails version have safe access rights 2.279
And I take note of which tps features are available 0.896
And I shutdown Tails and wait for the computer to power off 4.444
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.177
After features/support/hooks.rb:330 0.126
After features/support/hooks.rb:100 0.007
Tags: @product
2:32.713
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 9.745
And I log in to a new session 19.697
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.678
And I plug USB drive "to_upgrade" 2.394
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.539
Then the running Tails is installed on USB drive "to_upgrade" 22.252
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:330 2.181
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.037
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.204
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.689
Then all tps features from the old Tails version are active 1.664
And Tails is running from USB drive "to_upgrade" 0.318
And the boot device has safe access rights 3.462
And the expected persistent files created with the old Tails version are present in the filesystem 1.430
And all persistent directories from the old Tails version have safe access rights 2.265
After features/support/hooks.rb:330 1.058
After features/support/hooks.rb:100 0.023
7:34.595
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.598
And no SquashFS delta is installed 0.108
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.269
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.106
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.435
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.396
When the network is plugged 0.061
And Tor is ready 21.201
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.879
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.374
Given I shutdown Tails and wait for the computer to power off 8.506
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.446
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.152
And the file system changes introduced in version 6.2~testoverlayfs are present 0.298
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.311
# 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.303
When the network is plugged 0.067
And Tor is ready 16.041
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.632
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.555
Given I shutdown Tails and wait for the computer to power off 1:1.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.198
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.435
And the file system changes introduced in version 6.3~testoverlayfs are present 0.463
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.338
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.242
When the network is plugged 0.094
And Tor is ready 20.734
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.157
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.672
After features/support/hooks.rb:330 0.711
After features/support/hooks.rb:100 0.015
39.246
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.464
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.461
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the signing key used by the Upgrader is outdated 0.136
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 18.112
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.926
After features/support/hooks.rb:330 0.998
After features/support/hooks.rb:100 0.000