Project Number Date
test_Tails_ISO_devel 3605 07 Dec 2024, 13:16

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 19:43.707 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:16.186
Before features/support/hooks.rb:269 0.006
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 32.226
When I start Tails from USB drive "old" with network unplugged 1:38.547
Then the boot device has safe access rights 3.055
And Tails is running from USB drive "old" 0.334
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.118
And udev-watchdog is monitoring the correct device 0.307
And I unplug USB drive "old" 0.235
After features/support/hooks.rb:326 3.775
After features/support/hooks.rb:100 0.008
Tags: @product
2:5.529
Before features/support/hooks.rb:269 0.006
Given a computer 0.300
And I start Tails from USB drive "old" with network unplugged and I login 1:23.753
Then Tails is running from USB drive "old" 0.344
And I create a persistent partition 31.633
And I take note of which tps features are available 2.435
Then a Tails persistence partition exists on USB drive "old" 0.877
And I shutdown Tails and wait for the computer to power off 6.185
After features/support/hooks.rb:326 0.164
After features/support/hooks.rb:100 0.010
Tags: @product
2:50.046
Before features/support/hooks.rb:269 0.005
Given a computer 0.233
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.619
Then Tails is running from USB drive "old" 1.184
And all tps features are active 2.044
When I write some files expected to persist 2.665
# 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.392
And all persistent directories from the old Tails version have safe access rights 2.529
And I take note of which tps features are available 0.428
And I shutdown Tails and wait for the computer to power off 4.416
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.309
After features/support/hooks.rb:326 0.146
After features/support/hooks.rb:100 0.011
Tags: @product
2:31.968
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.941
And I log in to a new session 18.744
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.721
And I plug USB drive "to_upgrade" 2.590
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.255
Then the running Tails is installed on USB drive "to_upgrade" 22.287
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.222
After features/support/hooks.rb:326 2.408
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.826
Before features/support/hooks.rb:269 0.005
Given a computer 0.175
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.062
Then all tps features from the old Tails version are active 1.606
And Tails is running from USB drive "to_upgrade" 0.350
And the boot device has safe access rights 2.975
And the expected persistent files created with the old Tails version are present in the filesystem 1.430
And all persistent directories from the old Tails version have safe access rights 2.226
After features/support/hooks.rb:326 0.866
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:40.285
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.749
And no SquashFS delta is installed 0.106
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.468
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.581
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.306
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.465
When the network is plugged 0.061
And Tor is ready 22.579
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.690
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.318
Given I shutdown Tails and wait for the computer to power off 10.960
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.009
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.182
And the file system changes introduced in version 6.2~testoverlayfs are present 0.298
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.282
# 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.285
When the network is plugged 0.077
And Tor is ready 17.173
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.737
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.255
Given I shutdown Tails and wait for the computer to power off 4.183
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.071
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.204
And the file system changes introduced in version 6.3~testoverlayfs are present 0.483
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.273
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.288
When the network is plugged 0.068
And Tor is ready 16.567
Then the Upgrader considers the system as up-to-date 0.326
# 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.087
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.977
After features/support/hooks.rb:326 0.806
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
1:1.864
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.215
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.961
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 1.624
But a current signing key is available on our website 0.000
When the network is plugged 0.064
And Tor is ready 47.351
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.585
After features/support/hooks.rb:326 0.728
After features/support/hooks.rb:100 0.000