Project Number Date
test_Tails_ISO_devel 3513 11 Sep 2024, 12:34

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:52.307 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:2.200
Before features/support/hooks.rb:269 0.006
Given a computer 0.183
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 29.518
When I start Tails from USB drive "old" with network unplugged 1:26.989
Then the boot device has safe access rights 3.236
And Tails is running from USB drive "old" 0.433
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.112
And udev-watchdog is monitoring the correct device 0.353
And I unplug USB drive "old" 0.205
After features/support/hooks.rb:326 6.953
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.008
Before features/support/hooks.rb:269 0.004
Given a computer 0.241
And I start Tails from USB drive "old" with network unplugged and I login 1:23.838
Then Tails is running from USB drive "old" 0.347
And I create a persistent partition 31.018
And I take note of which tps features are available 1.438
Then a Tails persistence partition exists on USB drive "old" 0.800
And I shutdown Tails and wait for the computer to power off 8.322
After features/support/hooks.rb:326 0.171
After features/support/hooks.rb:100 0.009
Tags: @product
2:54.404
Before features/support/hooks.rb:269 0.006
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.208
Then Tails is running from USB drive "old" 0.431
And all tps features are active 1.993
When I write some files expected to persist 1.590
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.251
And all persistence configuration files have safe access rights 0.401
And all persistent directories from the old Tails version have safe access rights 2.898
And I take note of which tps features are available 0.464
And I shutdown Tails and wait for the computer to power off 4.312
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.652
After features/support/hooks.rb:326 0.135
After features/support/hooks.rb:100 0.013
Tags: @product
2:39.658
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.032
And I log in to a new session 23.265
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.663
And I plug USB drive "to_upgrade" 2.421
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.115
Then the running Tails is installed on USB drive "to_upgrade" 21.722
And I unplug USB drive "to_upgrade" 0.227
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:326 3.483
After features/support/hooks.rb:100 0.000
Tags: @product
2:7.745
Before features/support/hooks.rb:269 0.007
Given a computer 0.211
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:58.290
Then all tps features from the old Tails version are active 1.631
And Tails is running from USB drive "to_upgrade" 0.336
And the boot device has safe access rights 3.228
And the expected persistent files created with the old Tails version are present in the filesystem 1.370
And all persistent directories from the old Tails version have safe access rights 2.676
After features/support/hooks.rb:326 0.853
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:25.942
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.803
And no SquashFS delta is installed 0.156
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.316
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.342
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.439
When the network is plugged 0.083
And Tor is ready 24.260
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.298
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.812
Given I shutdown Tails and wait for the computer to power off 8.608
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.739
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.351
And the file system changes introduced in version 6.2~testoverlayfs are present 0.306
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.308
# 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.259
When the network is plugged 0.069
And Tor is ready 21.078
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.174
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.684
Given I shutdown Tails and wait for the computer to power off 4.633
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.486
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.195
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.067
# 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.302
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.251
When the network is plugged 0.078
And Tor is ready 17.163
Then the Upgrader considers the system as up-to-date 0.329
# 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 13.744
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.943
After features/support/hooks.rb:326 0.724
After features/support/hooks.rb:100 0.027
Tags: @product @automatic_upgrade
36.346
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.151
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.354
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.976
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 19.095
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.639
After features/support/hooks.rb:326 0.989
After features/support/hooks.rb:100 0.000