Project Number Date
test_Tails_ISO_18215-update-chutney-force-all-tests 9 27 Mar 2025, 13:20

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 21:47.329 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:41.355
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.249
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 36.058
When I start Tails from USB drive "old" with network unplugged 1:59.245
Then the boot device has safe access rights 3.559
And Tails is running from USB drive "old" 0.374
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.342
And I unplug USB drive "old" 0.248
After features/support/hooks.rb:330 3.511
After features/support/hooks.rb:100 0.065
Tags: @product
2:19.807
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.227
And I start Tails from USB drive "old" with network unplugged and I login 1:34.818
Then Tails is running from USB drive "old" 0.394
And I create a persistent partition 32.567
And I take note of which tps features are available 1.974
Then a Tails persistence partition exists on USB drive "old" 0.952
And I shutdown Tails and wait for the computer to power off 8.872
After features/support/hooks.rb:330 0.197
After features/support/hooks.rb:100 0.010
Tags: @product
3:12.807
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:31.519
Then Tails is running from USB drive "old" 0.582
And all tps features are active 2.363
When I write some files expected to persist 1.752
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.241
And all persistence configuration files have safe access rights 0.432
And all persistent directories from the old Tails version have safe access rights 2.746
And I take note of which tps features are available 0.500
And I shutdown Tails and wait for the computer to power off 4.561
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 27.881
After features/support/hooks.rb:330 0.152
After features/support/hooks.rb:100 0.014
Tags: @product
2:44.479
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 without a persistent partition and stopped at Tails Greeter's login screen 12.135
And I log in to a new session 23.076
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.918
And I plug USB drive "to_upgrade" 2.479
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.087
Then the running Tails is installed on USB drive "to_upgrade" 24.194
And I unplug USB drive "to_upgrade" 0.242
And I unplug USB drive "__internal" 0.343
After features/support/hooks.rb:330 2.341
After features/support/hooks.rb:100 0.000
Tags: @product
2:56.312
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.218
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:44.172
Then all tps features from the old Tails version are active 2.260
And Tails is running from USB drive "to_upgrade" 0.553
And the boot device has safe access rights 4.467
And the expected persistent files created with the old Tails version are present in the filesystem 1.763
And all persistent directories from the old Tails version have safe access rights 2.877
After features/support/hooks.rb:330 1.506
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
7:11.244
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 12.775
And no SquashFS delta is installed 0.152
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.649
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.316
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.456
When the network is plugged 0.079
And Tor is ready 26.477
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.282
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.543
Given I shutdown Tails and wait for the computer to power off 11.361
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:22.416
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.332
And the file system changes introduced in version 6.2~testoverlayfs are present 0.375
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# 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.265
When the network is plugged 0.064
And Tor is ready 21.038
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.701
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.787
Given I shutdown Tails and wait for the computer to power off 4.652
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.094
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.437
And the file system changes introduced in version 6.3~testoverlayfs are present 0.507
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.284
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.289
When the network is plugged 0.066
And Tor is ready 20.158
Then the Upgrader considers the system as up-to-date 0.355
# 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.224
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.546
After features/support/hooks.rb:330 0.679
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
41.322
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.244
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.334
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.069
But a current signing key is available on our website 0.000
When the network is plugged 0.074
And Tor is ready 22.215
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.320
After features/support/hooks.rb:330 1.190
After features/support/hooks.rb:100 0.000