Project Number Date
test_Tails_ISO_stable 4960 22 Jul 2024, 12:26

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:47.241 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:7.353
Before features/support/hooks.rb:269 0.006
Given a computer 0.215
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 29.129
When I start Tails from USB drive "old" with network unplugged 1:32.950
Then the boot device has safe access rights 2.984
And Tails is running from USB drive "old" 0.343
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.282
And I unplug USB drive "old" 0.178
After features/support/hooks.rb:326 3.540
After features/support/hooks.rb:100 0.008
Tags: @product
2:0.502
Before features/support/hooks.rb:269 0.006
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login 1:18.167
Then Tails is running from USB drive "old" 0.349
And I create a persistent partition 31.023
And I take note of which tps features are available 1.425
Then a Tails persistence partition exists on USB drive "old" 0.767
And I shutdown Tails and wait for the computer to power off 8.582
After features/support/hooks.rb:326 0.128
After features/support/hooks.rb:100 0.010
Tags: @product
2:50.777
Before features/support/hooks.rb:269 0.005
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.377
Then Tails is running from USB drive "old" 0.319
And all tps features are active 2.058
When I write some files expected to persist 1.717
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.224
And all persistence configuration files have safe access rights 0.378
And all persistent directories from the old Tails version have safe access rights 2.454
And I take note of which tps features are available 0.462
And I shutdown Tails and wait for the computer to power off 4.309
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.263
After features/support/hooks.rb:326 0.156
After features/support/hooks.rb:100 0.010
Tags: @product
2:24.925
Before features/support/hooks.rb:269 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 10.165
And I log in to a new session 17.808
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.222
And I plug USB drive "to_upgrade" 2.361
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.127
Then the running Tails is installed on USB drive "to_upgrade" 16.821
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.215
After features/support/hooks.rb:326 4.327
After features/support/hooks.rb:100 0.000
Tags: @product
2:8.994
Before features/support/hooks.rb:269 0.006
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.826
Then all tps features from the old Tails version are active 1.637
And Tails is running from USB drive "to_upgrade" 0.325
And the boot device has safe access rights 3.011
And the expected persistent files created with the old Tails version are present in the filesystem 1.634
And all persistent directories from the old Tails version have safe access rights 2.366
After features/support/hooks.rb:326 0.694
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:38.907
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.218
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.277
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.305
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.463
When the network is plugged 0.041
And Tor is ready 48.131
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.600
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.184
Given I shutdown Tails and wait for the computer to power off 8.596
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.281
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.145
And the file system changes introduced in version 6.2~testoverlayfs are present 0.307
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.363
# 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.245
When the network is plugged 0.043
And Tor is ready 48.980
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.571
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.991
Given I shutdown Tails and wait for the computer to power off 4.321
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.471
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.905
And the file system changes introduced in version 6.3~testoverlayfs are present 0.460
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.421
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.275
When the network is plugged 0.037
And Tor is ready 18.343
Then the Upgrader considers the system as up-to-date 0.398
# 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.341
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.882
After features/support/hooks.rb:326 0.750
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
35.780
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.767
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.294
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.757
But a current signing key is available on our website 0.000
When the network is plugged 0.062
And Tor is ready 18.072
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.764
After features/support/hooks.rb:326 0.870
After features/support/hooks.rb:100 0.000