Project Number Date
test_Tails_ISO_devel 3522 27 Sep 2024, 12:37

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 18:29.932 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:8.926
Before features/support/hooks.rb:269 0.006
Given a computer 0.179
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 29.050
When I start Tails from USB drive "old" with network unplugged 1:34.653
Then the boot device has safe access rights 2.952
And Tails is running from USB drive "old" 0.331
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.296
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:326 3.756
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.083
Before features/support/hooks.rb:269 0.005
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login 1:23.578
Then Tails is running from USB drive "old" 0.330
And I create a persistent partition 31.388
And I take note of which tps features are available 1.511
Then a Tails persistence partition exists on USB drive "old" 0.778
And I shutdown Tails and wait for the computer to power off 8.306
After features/support/hooks.rb:326 0.161
After features/support/hooks.rb:100 0.009
Tags: @product
2:50.078
Before features/support/hooks.rb:269 0.006
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.283
Then Tails is running from USB drive "old" 0.339
And all tps features are active 2.039
When I write some files expected to persist 1.715
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.212
And all persistence configuration files have safe access rights 0.382
And all persistent directories from the old Tails version have safe access rights 2.603
And I take note of which tps features are available 0.556
And I shutdown Tails and wait for the computer to power off 4.280
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.478
After features/support/hooks.rb:326 0.132
After features/support/hooks.rb:100 0.011
Tags: @product
2:30.465
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 11.317
And I log in to a new session 21.395
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.416
And I plug USB drive "to_upgrade" 2.400
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.967
Then the running Tails is installed on USB drive "to_upgrade" 20.511
And I unplug USB drive "to_upgrade" 0.249
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:326 1.024
After features/support/hooks.rb:100 0.000
Tags: @product
2:4.843
Before features/support/hooks.rb:269 0.005
Given a computer 0.182
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:55.655
Then all tps features from the old Tails version are active 1.625
And Tails is running from USB drive "to_upgrade" 0.349
And the boot device has safe access rights 3.196
And the expected persistent files created with the old Tails version are present in the filesystem 1.408
And all persistent directories from the old Tails version have safe access rights 2.425
After features/support/hooks.rb:326 0.988
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:17.542
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 11.255
And no SquashFS delta is installed 0.486
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.317
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.283
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.469
When the network is plugged 0.151
And Tor is ready 19.797
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.190
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.261
Given I shutdown Tails and wait for the computer to power off 10.752
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.323
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.386
And the file system changes introduced in version 6.2~testoverlayfs are present 0.341
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.349
# 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.276
When the network is plugged 0.090
And Tor is ready 16.733
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.925
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.072
Given I shutdown Tails and wait for the computer to power off 4.314
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.501
Then Tails is running version 6.3~testoverlayfs 0.040
And all tps features are active 1.975
And the file system changes introduced in version 6.3~testoverlayfs are present 0.475
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.266
When the network is plugged 0.085
And Tor is ready 19.031
Then the Upgrader considers the system as up-to-date 0.317
# 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.671
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.892
After features/support/hooks.rb:326 0.796
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
31.992
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.825
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.238
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.816
But a current signing key is available on our website 0.000
When the network is plugged 0.063
And Tor is ready 14.721
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.275
After features/support/hooks.rb:326 1.090
After features/support/hooks.rb:100 0.000