Project Number Date
test_Tails_ISO_tca-misc-improvements 11 18 Apr 2025, 18:30

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:6.263 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:15.848
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.047
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 30.095
When I start Tails from USB drive "old" with network unplugged 1:40.294
Then the boot device has safe access rights 3.083
And Tails is running from USB drive "old" 0.402
And there is no persistence partition on USB drive "old" 0.097
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.287
And I unplug USB drive "old" 0.200
After features/support/hooks.rb:330 7.774
After features/support/hooks.rb:100 0.010
Tags: @product
2:14.336
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.223
And I start Tails from USB drive "old" with network unplugged and I login 1:29.789
Then Tails is running from USB drive "old" 0.390
And I create a persistent partition 32.128
And I take note of which tps features are available 2.382
Then a Tails persistence partition exists on USB drive "old" 0.795
And I shutdown Tails and wait for the computer to power off 8.627
After features/support/hooks.rb:330 0.181
After features/support/hooks.rb:100 0.008
Tags: @product
2:56.514
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.665
Then Tails is running from USB drive "old" 0.326
And all tps features are active 2.249
When I write some files expected to persist 2.140
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.269
And all persistence configuration files have safe access rights 0.459
And all persistent directories from the old Tails version have safe access rights 2.708
And I take note of which tps features are available 0.544
And I shutdown Tails and wait for the computer to power off 4.510
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.428
After features/support/hooks.rb:330 0.145
After features/support/hooks.rb:100 0.008
Tags: @product
2:35.137
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 11.345
And I log in to a new session 18.450
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.658
And I plug USB drive "to_upgrade" 2.357
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.470
Then the running Tails is installed on USB drive "to_upgrade" 25.359
And I unplug USB drive "to_upgrade" 0.223
And I unplug USB drive "__internal" 0.273
After features/support/hooks.rb:330 2.141
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.162
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.202
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.102
Then all tps features from the old Tails version are active 1.748
And Tails is running from USB drive "to_upgrade" 0.339
And the boot device has safe access rights 3.698
And the expected persistent files created with the old Tails version are present in the filesystem 1.499
And all persistent directories from the old Tails version have safe access rights 2.571
After features/support/hooks.rb:330 1.278
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
7:7.284
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 11.764
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.296
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.339
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.536
When the network is plugged 0.068
And Tor is ready 50.476
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.609
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.937
Given I shutdown Tails and wait for the computer to power off 11.164
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.285
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.398
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.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.441
# 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.378
When the network is plugged 0.085
And Tor is ready 19.775
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.650
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.822
Given I shutdown Tails and wait for the computer to power off 4.575
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.214
Then Tails is running version 6.3~testoverlayfs 0.024
And all tps features are active 2.172
And the file system changes introduced in version 6.3~testoverlayfs are present 0.807
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.342
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.297
When the network is plugged 0.068
And Tor is ready 20.015
Then the Upgrader considers the system as up-to-date 0.394
# 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.713
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.974
After features/support/hooks.rb:330 1.034
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
42.979
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 11.336
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.341
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.078
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 24.011
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.080
After features/support/hooks.rb:330 1.074
After features/support/hooks.rb:100 0.000