Project Number Date
test_Tails_ISO_tca-misc-improvements 12 19 Apr 2025, 18:21

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:32.562 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.118
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.193
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 34.317
When I start Tails from USB drive "old" with network unplugged 1:30.441
Then the boot device has safe access rights 3.055
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.086
And udev-watchdog is monitoring the correct device 0.327
And I unplug USB drive "old" 0.184
After features/support/hooks.rb:330 6.746
After features/support/hooks.rb:100 0.009
Tags: @product
2:16.340
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login 1:31.019
Then Tails is running from USB drive "old" 0.399
And I create a persistent partition 33.619
And I take note of which tps features are available 1.837
Then a Tails persistence partition exists on USB drive "old" 0.818
And I shutdown Tails and wait for the computer to power off 8.449
After features/support/hooks.rb:330 0.175
After features/support/hooks.rb:100 0.009
Tags: @product
2:55.677
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.215
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.479
Then Tails is running from USB drive "old" 0.396
And all tps features are active 2.278
When I write some files expected to persist 1.910
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.337
And all persistence configuration files have safe access rights 0.450
And all persistent directories from the old Tails version have safe access rights 2.953
And I take note of which tps features are available 0.516
And I shutdown Tails and wait for the computer to power off 4.345
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.793
After features/support/hooks.rb:330 0.126
After features/support/hooks.rb:100 0.013
Tags: @product
2:37.273
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 without a persistent partition and stopped at Tails Greeter's login screen 10.844
And I log in to a new session 19.982
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.579
And I plug USB drive "to_upgrade" 2.418
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.872
Then the running Tails is installed on USB drive "to_upgrade" 26.128
And I unplug USB drive "to_upgrade" 0.217
And I unplug USB drive "__internal" 0.229
After features/support/hooks.rb:330 0.976
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.504
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.206
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.839
Then all tps features from the old Tails version are active 1.661
And Tails is running from USB drive "to_upgrade" 0.364
And the boot device has safe access rights 3.474
And the expected persistent files created with the old Tails version are present in the filesystem 1.415
And all persistent directories from the old Tails version have safe access rights 2.542
After features/support/hooks.rb:330 1.456
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:37.904
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 27.371
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.356
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.594
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.575
When the network is plugged 0.156
And Tor is ready 21.697
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.586
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.842
Given I shutdown Tails and wait for the computer to power off 10.727
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.591
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.160
And the file system changes introduced in version 6.2~testoverlayfs are present 0.297
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.300
# 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.288
When the network is plugged 0.100
And Tor is ready 19.264
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.582
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.041
Given I shutdown Tails and wait for the computer to power off 4.619
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.481
Then Tails is running version 6.3~testoverlayfs 0.033
And all tps features are active 2.365
And the file system changes introduced in version 6.3~testoverlayfs are present 0.680
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.318
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.287
When the network is plugged 0.077
And Tor is ready 48.342
Then the Upgrader considers the system as up-to-date 0.366
# 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.938
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.550
After features/support/hooks.rb:330 0.729
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
35.744
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 10.549
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.067
And the signing key used by the Upgrader is outdated 0.075
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 17.850
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.784
After features/support/hooks.rb:330 1.014
After features/support/hooks.rb:100 0.000