Project Number Date
test_Tails_ISO_devel 3427 15 Jun 2024, 13:04

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:21.011 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:14.978
Before features/support/hooks.rb:269 0.007
Given a computer 0.276
And I create a 7200 MiB disk named "old" 0.061
And I plug USB drive "old" 1.067
And I write an old version of the Tails USB image to disk "old" 41.477
When I start Tails from USB drive "old" with network unplugged 1:28.114
Then the boot device has safe access rights 2.923
And Tails is running from USB drive "old" 0.356
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.083
And udev-watchdog is monitoring the correct device 0.369
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:315 7.029
After features/support/hooks.rb:100 0.013
Tags: @product
2:27.545
Before features/support/hooks.rb:269 0.008
Given a computer 1.222
And I start Tails from USB drive "old" with network unplugged and I login 1:32.376
Then Tails is running from USB drive "old" 0.390
And I create a persistent partition 40.010
And I take note of which tps features are available 2.036
Then a Tails persistence partition exists on USB drive "old" 0.850
And I shutdown Tails and wait for the computer to power off 10.658
After features/support/hooks.rb:315 0.186
After features/support/hooks.rb:100 0.011
Tags: @product
3:0.465
Before features/support/hooks.rb:269 0.007
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.278
Then Tails is running from USB drive "old" 0.380
And all tps features are active 2.534
When I write some files expected to persist 1.856
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.231
And all persistence configuration files have safe access rights 0.425
And all persistent directories from the old Tails version have safe access rights 2.738
And I take note of which tps features are available 0.524
And I shutdown Tails and wait for the computer to power off 4.190
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.080
After features/support/hooks.rb:315 0.147
After features/support/hooks.rb:100 0.010
Tags: @product
2:36.471
Before features/support/hooks.rb:269 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 11.737
And I log in to a new session 20.544
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.475
And I plug USB drive "to_upgrade" 2.465
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.420
Then the running Tails is installed on USB drive "to_upgrade" 20.413
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:315 6.983
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.203
Before features/support/hooks.rb:269 0.009
Given a computer 0.262
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.512
Then all tps features from the old Tails version are active 1.645
And Tails is running from USB drive "to_upgrade" 0.372
And the boot device has safe access rights 3.526
And the expected persistent files created with the old Tails version are present in the filesystem 1.484
And all persistent directories from the old Tails version have safe access rights 2.398
After features/support/hooks.rb:315 0.684
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
7:5.651
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 25.042
And no SquashFS delta is installed 0.108
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.362
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.362
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.498
When the network is plugged 0.043
And Tor is ready 20.504
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.120
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.169
Given I shutdown Tails and wait for the computer to power off 8.792
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.141
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.715
And the file system changes introduced in version 6.2~testoverlayfs are present 0.433
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.488
# 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.338
When the network is plugged 0.040
And Tor is ready 17.799
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.699
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.600
Given I shutdown Tails and wait for the computer to power off 4.476
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.644
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.466
And the file system changes introduced in version 6.3~testoverlayfs are present 0.592
And only the 6.3~testoverlayfs SquashFS delta is installed 0.091
# 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.409
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.330
When the network is plugged 0.043
And Tor is ready 19.898
Then the Upgrader considers the system as up-to-date 0.365
# 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.794
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.080
After features/support/hooks.rb:315 0.970
After features/support/hooks.rb:100 0.028
Tags: @product @automatic_upgrade
38.695
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 10.941
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.375
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 1.262
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 19.026
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.988
After features/support/hooks.rb:315 0.802
After features/support/hooks.rb:100 0.000