Project Number Date
test_Tails_ISO_devel 3501 03 Sep 2024, 13:06

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:37.920 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:20.612
Before features/support/hooks.rb:269 0.009
Given a computer 0.221
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 31.590
When I start Tails from USB drive "old" with network unplugged 1:41.917
Then the boot device has safe access rights 3.186
And Tails is running from USB drive "old" 1.337
And there is no persistence partition on USB drive "old" 0.371
And process "udev-watchdog" is running 0.310
And udev-watchdog is monitoring the correct device 0.340
And I unplug USB drive "old" 0.223
After features/support/hooks.rb:326 3.595
After features/support/hooks.rb:100 0.012
Tags: @product
2:8.447
Before features/support/hooks.rb:269 0.009
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login 1:25.354
Then Tails is running from USB drive "old" 0.324
And I create a persistent partition 31.957
And I take note of which tps features are available 1.471
Then a Tails persistence partition exists on USB drive "old" 0.821
And I shutdown Tails and wait for the computer to power off 8.293
After features/support/hooks.rb:326 0.161
After features/support/hooks.rb:100 0.013
Tags: @product
3:2.559
Before features/support/hooks.rb:269 0.009
Given a computer 0.234
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.932
Then Tails is running from USB drive "old" 0.318
And all tps features are active 2.437
When I write some files expected to persist 1.652
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.222
And all persistence configuration files have safe access rights 0.434
And all persistent directories from the old Tails version have safe access rights 2.486
And I take note of which tps features are available 0.446
And I shutdown Tails and wait for the computer to power off 4.437
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.956
After features/support/hooks.rb:326 0.171
After features/support/hooks.rb:100 0.013
Tags: @product
2:38.828
Before features/support/hooks.rb:269 0.013
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.169
And I log in to a new session 20.856
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.971
And I plug USB drive "to_upgrade" 2.492
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.464
Then the running Tails is installed on USB drive "to_upgrade" 23.442
And I unplug USB drive "to_upgrade" 0.223
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:326 1.843
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.718
Before features/support/hooks.rb:269 0.006
Given a computer 0.212
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.694
Then all tps features from the old Tails version are active 1.787
And Tails is running from USB drive "to_upgrade" 0.340
And the boot device has safe access rights 3.579
And the expected persistent files created with the old Tails version are present in the filesystem 1.437
And all persistent directories from the old Tails version have safe access rights 2.667
After features/support/hooks.rb:326 1.546
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
7:19.493
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 25.102
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.368
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.309
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.488
When the network is plugged 0.081
And Tor is ready 23.082
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.662
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.104
Given I shutdown Tails and wait for the computer to power off 11.209
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.905
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.728
And the file system changes introduced in version 6.2~testoverlayfs are present 0.364
And only the 6.2~testoverlayfs SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.352
# 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.317
When the network is plugged 0.112
And Tor is ready 18.025
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.776
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.031
Given I shutdown Tails and wait for the computer to power off 4.732
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.681
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.469
And the file system changes introduced in version 6.3~testoverlayfs are present 0.540
And only the 6.3~testoverlayfs SquashFS delta is installed 0.088
# 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.351
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.321
When the network is plugged 0.071
And Tor is ready 20.775
Then the Upgrader considers the system as up-to-date 0.318
# 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.657
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.188
After features/support/hooks.rb:326 1.131
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
40.261
Before features/support/hooks.rb:269 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.520
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.364
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.472
And the signing key used by the Upgrader is outdated 1.005
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 18.943
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.886
After features/support/hooks.rb:326 0.671
After features/support/hooks.rb:100 0.000