Project Number Date
test_Tails_ISO_devel 3511 10 Sep 2024, 16:11

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:10.690 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:9.836
Before features/support/hooks.rb:269 0.005
Given a computer 0.188
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 31.698
When I start Tails from USB drive "old" with network unplugged 1:32.366
Then the boot device has safe access rights 3.144
And Tails is running from USB drive "old" 0.398
And there is no persistence partition on USB drive "old" 0.087
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.321
And I unplug USB drive "old" 0.426
After features/support/hooks.rb:326 8.122
After features/support/hooks.rb:100 0.010
Tags: @product
2:13.983
Before features/support/hooks.rb:269 0.006
Given a computer 0.234
And I start Tails from USB drive "old" with network unplugged and I login 1:32.304
Then Tails is running from USB drive "old" 0.437
And I create a persistent partition 32.229
And I take note of which tps features are available 1.717
Then a Tails persistence partition exists on USB drive "old" 0.807
And I shutdown Tails and wait for the computer to power off 6.251
After features/support/hooks.rb:326 0.191
After features/support/hooks.rb:100 0.009
Tags: @product
3:11.073
Before features/support/hooks.rb:269 0.006
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:29.045
Then Tails is running from USB drive "old" 0.470
And all tps features are active 3.566
When I write some files expected to persist 2.019
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.273
And all persistence configuration files have safe access rights 0.575
And all persistent directories from the old Tails version have safe access rights 3.261
And I take note of which tps features are available 0.967
And I shutdown Tails and wait for the computer to power off 4.377
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.290
After features/support/hooks.rb:326 0.117
After features/support/hooks.rb:100 0.010
Tags: @product
2:38.250
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 16.184
And I log in to a new session 19.258
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.583
And I plug USB drive "to_upgrade" 2.454
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.026
Then the running Tails is installed on USB drive "to_upgrade" 23.306
And I unplug USB drive "to_upgrade" 0.223
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:326 2.827
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.017
Before features/support/hooks.rb:269 0.005
Given a computer 0.306
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.156
Then all tps features from the old Tails version are active 1.733
And Tails is running from USB drive "to_upgrade" 0.401
And the boot device has safe access rights 3.494
And the expected persistent files created with the old Tails version are present in the filesystem 1.473
And all persistent directories from the old Tails version have safe access rights 2.451
After features/support/hooks.rb:326 0.968
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:56.260
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.225
And no SquashFS delta is installed 0.212
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.329
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.212
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.341
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.496
When the network is plugged 0.074
And Tor is ready 23.567
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.985
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.203
Given I shutdown Tails and wait for the computer to power off 11.679
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.118
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.964
And the file system changes introduced in version 6.2~testoverlayfs are present 0.390
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.456
# 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.358
When the network is plugged 0.091
And Tor is ready 17.751
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.290
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.031
Given I shutdown Tails and wait for the computer to power off 4.411
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.622
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.454
And the file system changes introduced in version 6.3~testoverlayfs are present 0.505
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.321
When the network is plugged 0.081
And Tor is ready 19.496
Then the Upgrader considers the system as up-to-date 0.332
# 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 14.711
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.041
After features/support/hooks.rb:326 0.773
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
40.270
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.584
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.330
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.834
But a current signing key is available on our website 0.000
When the network is plugged 0.170
And Tor is ready 18.516
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.785
After features/support/hooks.rb:326 0.863
After features/support/hooks.rb:100 0.000