Project Number Date
test_Tails_ISO_tca-remove-cruft 8 15 May 2025, 10:17

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:44.670 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:3.488
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.176
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 34.176
When I start Tails from USB drive "old" with network unplugged 1:23.820
Then the boot device has safe access rights 3.106
And Tails is running from USB drive "old" 0.375
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.345
And I unplug USB drive "old" 0.244
After features/support/hooks.rb:330 3.515
After features/support/hooks.rb:100 0.009
Tags: @product
2:11.411
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login 1:28.154
Then Tails is running from USB drive "old" 0.379
And I create a persistent partition 31.826
And I take note of which tps features are available 1.818
Then a Tails persistence partition exists on USB drive "old" 0.745
And I shutdown Tails and wait for the computer to power off 8.301
After features/support/hooks.rb:330 0.185
After features/support/hooks.rb:100 0.008
Tags: @product
2:56.659
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:16.443
Then Tails is running from USB drive "old" 0.761
And all tps features are active 2.252
When I write some files expected to persist 1.944
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.358
And all persistence configuration files have safe access rights 0.556
And all persistent directories from the old Tails version have safe access rights 2.689
And I take note of which tps features are available 0.569
And I shutdown Tails and wait for the computer to power off 6.250
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.617
After features/support/hooks.rb:330 0.161
After features/support/hooks.rb:100 0.011
Tags: @product
2:29.597
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.842
And I log in to a new session 18.801
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.675
And I plug USB drive "to_upgrade" 2.446
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.392
Then the running Tails is installed on USB drive "to_upgrade" 20.864
And I unplug USB drive "to_upgrade" 0.242
And I unplug USB drive "__internal" 0.331
After features/support/hooks.rb:330 2.146
After features/support/hooks.rb:100 0.000
Tags: @product
2:31.283
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.405
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:21.666
Then all tps features from the old Tails version are active 1.973
And Tails is running from USB drive "to_upgrade" 0.345
And the boot device has safe access rights 3.134
And the expected persistent files created with the old Tails version are present in the filesystem 1.391
And all persistent directories from the old Tails version have safe access rights 2.367
After features/support/hooks.rb:330 1.746
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:51.778
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.682
And no SquashFS delta is installed 0.158
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.490
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.309
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.513
When the network is plugged 0.080
And Tor is ready 21.733
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.991
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.847
Given I shutdown Tails and wait for the computer to power off 8.608
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.545
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.218
And the file system changes introduced in version 6.2~testoverlayfs are present 0.327
And only the 6.2~testoverlayfs SquashFS delta is installed 0.092
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.314
# 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.256
When the network is plugged 0.072
And Tor is ready 17.145
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.762
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.958
Given I shutdown Tails and wait for the computer to power off 4.344
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.833
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 5.596
And the file system changes introduced in version 6.3~testoverlayfs are present 0.500
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.336
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.357
When the network is plugged 0.282
And Tor is ready 24.564
Then the Upgrader considers the system as up-to-date 0.345
# 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.577
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.774
After features/support/hooks.rb:330 0.884
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
40.452
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 13.549
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.644
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.109
And the signing key used by the Upgrader is outdated 0.114
But a current signing key is available on our website 0.000
When the network is plugged 0.979
And Tor is ready 18.003
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.051
After features/support/hooks.rb:330 1.045
After features/support/hooks.rb:100 0.000