Project Number Date
test_Tails_ISO_stable 5025 13 Aug 2024, 17:42

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:28.250 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.429
Before features/support/hooks.rb:269 0.006
Given a computer 0.414
And I create a 7200 MiB disk named "old" 0.108
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 33.208
When I start Tails from USB drive "old" with network unplugged 1:37.542
Then the boot device has safe access rights 3.114
And Tails is running from USB drive "old" 0.329
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.307
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:326 3.552
After features/support/hooks.rb:100 0.034
Tags: @product
2:8.056
Before features/support/hooks.rb:269 0.009
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login 1:23.442
Then Tails is running from USB drive "old" 0.367
And I create a persistent partition 33.047
And I take note of which tps features are available 1.964
Then a Tails persistence partition exists on USB drive "old" 0.796
And I shutdown Tails and wait for the computer to power off 8.260
After features/support/hooks.rb:326 0.393
After features/support/hooks.rb:100 0.030
Tags: @product
2:59.789
Before features/support/hooks.rb:269 0.050
Given a computer 0.500
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.890
Then Tails is running from USB drive "old" 0.387
And all tps features are active 2.315
When I write some files expected to persist 1.768
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.247
And all persistence configuration files have safe access rights 0.457
And all persistent directories from the old Tails version have safe access rights 2.689
And I take note of which tps features are available 0.395
And I shutdown Tails and wait for the computer to power off 4.382
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.753
After features/support/hooks.rb:326 0.569
After features/support/hooks.rb:100 0.012
Tags: @product
2:30.718
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.540
And I log in to a new session 18.717
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.962
And I plug USB drive "to_upgrade" 2.480
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.852
Then the running Tails is installed on USB drive "to_upgrade" 20.705
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.243
After features/support/hooks.rb:326 2.005
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.613
Before features/support/hooks.rb:269 0.007
Given a computer 0.269
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.396
Then all tps features from the old Tails version are active 1.553
And Tails is running from USB drive "to_upgrade" 0.327
And the boot device has safe access rights 3.210
And the expected persistent files created with the old Tails version are present in the filesystem 1.410
And all persistent directories from the old Tails version have safe access rights 2.446
After features/support/hooks.rb:326 1.116
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:41.547
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 11.480
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.382
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.102
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.411
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.442
When the network is plugged 0.146
And Tor is ready 18.614
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.855
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.343
Given I shutdown Tails and wait for the computer to power off 15.343
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.136
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.136
And the file system changes introduced in version 6.2~testoverlayfs are present 0.276
And only the 6.2~testoverlayfs SquashFS delta is installed 0.086
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.412
# 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.306
When the network is plugged 0.067
And Tor is ready 19.214
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.329
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.615
Given I shutdown Tails and wait for the computer to power off 4.680
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.725
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.006
And the file system changes introduced in version 6.3~testoverlayfs are present 0.522
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.300
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.325
When the network is plugged 0.061
And Tor is ready 17.021
Then the Upgrader considers the system as up-to-date 10.812
# 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.176
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.026
After features/support/hooks.rb:326 0.794
After features/support/hooks.rb:100 0.028
Tags: @product @automatic_upgrade
35.095
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 10.052
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.301
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.095
And the signing key used by the Upgrader is outdated 0.913
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 16.809
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.854
After features/support/hooks.rb:326 0.722
After features/support/hooks.rb:100 0.000