Project Number Date
test_Tails_ISO_stable 4693 02 Mar 2024, 12:30

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:31.501 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:26.462
Before features/support/hooks.rb:245 0.006
Given a computer 0.208
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" 1:3.969
When I start Tails from USB drive "old" with network unplugged 1:16.990
Then the boot device has safe access rights 3.210
And Tails is running from USB drive "old" 0.312
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.309
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:291 3.536
After features/support/hooks.rb:75 0.013
Tags: @product
2:8.485
Before features/support/hooks.rb:245 0.007
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login 1:15.769
Then Tails is running from USB drive "old" 0.331
And I create a persistent partition 41.716
And I take note of which tps features are available 1.683
Then a Tails persistence partition exists on USB drive "old" 0.761
And I shutdown Tails and wait for the computer to power off 8.034
After features/support/hooks.rb:291 0.154
After features/support/hooks.rb:75 0.009
Tags: @product
2:37.345
Before features/support/hooks.rb:245 0.008
Given a computer 0.166
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.339
Then Tails is running from USB drive "old" 0.401
And all tps features are active 1.697
When I write some files expected to persist 1.744
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.194
And all persistence configuration files have safe access rights 0.347
And all persistent directories from the old Tails version have safe access rights 2.389
And I take note of which tps features are available 0.330
And I shutdown Tails and wait for the computer to power off 4.016
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.717
After features/support/hooks.rb:291 0.131
After features/support/hooks.rb:75 0.010
Tags: @product
2:42.631
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.431
And I log in to a new session 15.741
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.668
And I plug USB drive "to_upgrade" 2.398
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:51.963
Then the running Tails is installed on USB drive "to_upgrade" 19.060
And I unplug USB drive "to_upgrade" 0.193
And I unplug USB drive "__internal" 0.174
After features/support/hooks.rb:291 1.794
After features/support/hooks.rb:75 0.000
Tags: @product
2:18.880
Before features/support/hooks.rb:245 0.007
Given a computer 0.220
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.279
Then all tps features from the old Tails version are active 1.382
And Tails is running from USB drive "to_upgrade" 0.328
And the boot device has safe access rights 2.948
And the expected persistent files created with the old Tails version are present in the filesystem 1.405
And all persistent directories from the old Tails version have safe access rights 2.315
After features/support/hooks.rb:291 0.929
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
6:43.450
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.429
And no SquashFS delta is installed 0.168
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.344
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.254
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.460
When the network is plugged 0.032
And Tor is ready 18.527
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.402
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.923
Given I shutdown Tails and wait for the computer to power off 7.031
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.276
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.802
And the file system changes introduced in version 6.2~testoverlayfs are present 0.374
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.316
# 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.281
When the network is plugged 0.029
And Tor is ready 18.774
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.193
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.625
Given I shutdown Tails and wait for the computer to power off 5.029
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.709
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 1.960
And the file system changes introduced in version 6.3~testoverlayfs are present 0.509
And only the 6.3~testoverlayfs SquashFS delta is installed 0.093
# 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.287
When the network is plugged 0.032
And Tor is ready 15.104
Then the Upgrader considers the system as up-to-date 10.728
# 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.502
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.775
After features/support/hooks.rb:291 0.772
After features/support/hooks.rb:75 0.021
Tags: @product @automatic_upgrade
34.245
Before features/support/hooks.rb:245 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.746
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.324
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 0.447
But a current signing key is available on our website 0.000
When the network is plugged 0.031
And Tor is ready 16.196
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.429
After features/support/hooks.rb:291 0.855
After features/support/hooks.rb:75 0.000