Project Number Date
test_Tails_ISO_stable 5231 29 Oct 2024, 20:56

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:43.314 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:11.598
Before features/support/hooks.rb:269 0.007
Given a computer 0.181
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 32.043
When I start Tails from USB drive "old" with network unplugged 1:33.862
Then the boot device has safe access rights 3.314
And Tails is running from USB drive "old" 0.312
And there is no persistence partition on USB drive "old" 0.085
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.353
And I unplug USB drive "old" 0.243
After features/support/hooks.rb:326 3.917
After features/support/hooks.rb:100 0.012
Tags: @product
2:7.738
Before features/support/hooks.rb:269 0.005
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login 1:23.953
Then Tails is running from USB drive "old" 0.382
And I create a persistent partition 32.362
And I take note of which tps features are available 1.509
Then a Tails persistence partition exists on USB drive "old" 0.858
And I shutdown Tails and wait for the computer to power off 8.471
After features/support/hooks.rb:326 0.162
After features/support/hooks.rb:100 0.008
Tags: @product
2:48.689
Before features/support/hooks.rb:269 0.005
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.095
Then Tails is running from USB drive "old" 0.377
And all tps features are active 2.465
When I write some files expected to persist 1.773
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.230
And all persistence configuration files have safe access rights 0.420
And all persistent directories from the old Tails version have safe access rights 3.121
And I take note of which tps features are available 0.467
And I shutdown Tails and wait for the computer to power off 4.392
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.150
After features/support/hooks.rb:326 0.118
After features/support/hooks.rb:100 0.009
Tags: @product
2:31.057
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 10.368
And I log in to a new session 19.535
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.888
And I plug USB drive "to_upgrade" 2.495
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.288
Then the running Tails is installed on USB drive "to_upgrade" 22.074
And I unplug USB drive "to_upgrade" 0.192
And I unplug USB drive "__internal" 0.214
After features/support/hooks.rb:326 2.168
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.237
Before features/support/hooks.rb:269 0.006
Given a computer 0.211
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.704
Then all tps features from the old Tails version are active 1.574
And Tails is running from USB drive "to_upgrade" 0.366
And the boot device has safe access rights 3.456
And the expected persistent files created with the old Tails version are present in the filesystem 1.642
And all persistent directories from the old Tails version have safe access rights 2.280
After features/support/hooks.rb:326 1.030
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:17.884
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.968
And no SquashFS delta is installed 0.196
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.403
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.106
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.344
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.534
When the network is plugged 0.089
And Tor is ready 20.907
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.769
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.883
Given I shutdown Tails and wait for the computer to power off 8.687
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.470
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.297
And the file system changes introduced in version 6.2~testoverlayfs are present 0.320
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.324
# 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.254
When the network is plugged 0.131
And Tor is ready 17.828
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.526
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.556
Given I shutdown Tails and wait for the computer to power off 4.209
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.902
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.058
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.081
# 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.330
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.274
When the network is plugged 0.079
And Tor is ready 18.482
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.851
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.063
After features/support/hooks.rb:326 0.748
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
36.108
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.139
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.350
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 1.068
But a current signing key is available on our website 0.000
When the network is plugged 0.060
And Tor is ready 19.066
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.356
After features/support/hooks.rb:326 0.670
After features/support/hooks.rb:100 0.000