Project Number Date
test_Tails_ISO_tca-remove-cruft 6 13 May 2025, 10:08

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:21.116 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:25.481
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.206
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 30.058
When I start Tails from USB drive "old" with network unplugged 1:49.908
Then the boot device has safe access rights 3.180
And Tails is running from USB drive "old" 0.341
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.311
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:330 3.525
After features/support/hooks.rb:100 0.008
Tags: @product
2:21.637
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login 1:39.318
Then Tails is running from USB drive "old" 0.396
And I create a persistent partition 32.436
And I take note of which tps features are available 2.229
Then a Tails persistence partition exists on USB drive "old" 0.776
And I shutdown Tails and wait for the computer to power off 6.296
After features/support/hooks.rb:330 0.140
After features/support/hooks.rb:100 0.008
Tags: @product
3:3.070
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.628
Then Tails is running from USB drive "old" 0.313
And all tps features are active 1.982
When I write some files expected to persist 2.317
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.236
And all persistence configuration files have safe access rights 0.427
And all persistent directories from the old Tails version have safe access rights 2.615
And I take note of which tps features are available 1.071
And I shutdown Tails and wait for the computer to power off 6.579
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.679
After features/support/hooks.rb:330 0.157
After features/support/hooks.rb:100 0.010
Tags: @product
2:34.259
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 without a persistent partition and stopped at Tails Greeter's login screen 10.687
And I log in to a new session 19.235
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.615
And I plug USB drive "to_upgrade" 2.414
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.681
Then the running Tails is installed on USB drive "to_upgrade" 25.184
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.220
After features/support/hooks.rb:330 2.021
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.785
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.230
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.606
Then all tps features from the old Tails version are active 1.608
And Tails is running from USB drive "to_upgrade" 0.345
And the boot device has safe access rights 3.138
And the expected persistent files created with the old Tails version are present in the filesystem 1.481
And all persistent directories from the old Tails version have safe access rights 2.375
After features/support/hooks.rb:330 1.339
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:3.398
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.941
And no SquashFS delta is installed 0.116
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.300
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.438
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.576
When the network is plugged 0.070
And Tor is ready 49.421
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.594
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.391
Given I shutdown Tails and wait for the computer to power off 8.643
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.939
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.250
And the file system changes introduced in version 6.2~testoverlayfs are present 0.318
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.325
# 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.320
When the network is plugged 0.113
And Tor is ready 19.923
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.875
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.799
Given I shutdown Tails and wait for the computer to power off 4.321
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.222
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.917
And the file system changes introduced in version 6.3~testoverlayfs are present 0.575
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.313
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.318
When the network is plugged 0.077
And Tor is ready 19.329
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 17.303
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.087
After features/support/hooks.rb:330 0.797
After features/support/hooks.rb:100 0.041
Tags: @product @automatic_upgrade
38.483
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 with a persistent partition enabled and logged in 10.892
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.496
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.111
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 18.510
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.348
After features/support/hooks.rb:330 0.958
After features/support/hooks.rb:100 0.000