Project Number Date
test_Tails_ISO_stable 4731 20 Mar 2024, 14:02

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 17:39.075 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
1:46.529
Before features/support/hooks.rb:245 0.006
Given a computer 0.259
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 25.016
When I start Tails from USB drive "old" with network unplugged 1:15.946
Then the boot device has safe access rights 3.225
And Tails is running from USB drive "old" 0.351
And there is no persistence partition on USB drive "old" 0.055
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.292
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:291 6.907
After features/support/hooks.rb:75 0.008
Tags: @product
2:5.651
Before features/support/hooks.rb:245 0.004
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login 1:21.386
Then Tails is running from USB drive "old" 0.312
And I create a persistent partition 34.272
And I take note of which tps features are available 1.570
Then a Tails persistence partition exists on USB drive "old" 0.885
And I shutdown Tails and wait for the computer to power off 7.040
After features/support/hooks.rb:291 0.189
After features/support/hooks.rb:75 0.009
Tags: @product
2:43.449
Before features/support/hooks.rb:245 0.006
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.088
Then Tails is running from USB drive "old" 0.325
And all tps features are active 2.061
When I write some files expected to persist 1.747
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.231
And all persistence configuration files have safe access rights 0.611
And all persistent directories from the old Tails version have safe access rights 2.728
And I take note of which tps features are available 0.507
And I shutdown Tails and wait for the computer to power off 4.027
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.931
After features/support/hooks.rb:291 0.169
After features/support/hooks.rb:75 0.009
Tags: @product
2:20.052
Before features/support/hooks.rb:245 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 9.986
And I log in to a new session 17.549
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.615
And I plug USB drive "to_upgrade" 2.487
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.380
Then the running Tails is installed on USB drive "to_upgrade" 13.459
And I unplug USB drive "to_upgrade" 0.393
And I unplug USB drive "__internal" 0.178
After features/support/hooks.rb:291 6.543
After features/support/hooks.rb:75 0.000
Tags: @product
2:5.143
Before features/support/hooks.rb:245 0.008
Given a computer 0.397
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:55.855
Then all tps features from the old Tails version are active 1.468
And Tails is running from USB drive "to_upgrade" 0.308
And the boot device has safe access rights 3.033
And the expected persistent files created with the old Tails version are present in the filesystem 1.455
And all persistent directories from the old Tails version have safe access rights 2.624
After features/support/hooks.rb:291 0.772
After features/support/hooks.rb:75 0.008
Tags: @product @automatic_upgrade
6:5.907
Before features/support/hooks.rb:245 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.091
And no SquashFS delta is installed 0.115
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.293
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.331
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.412
When the network is plugged 0.037
And Tor is ready 18.084
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.408
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.633
Given I shutdown Tails and wait for the computer to power off 8.031
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.121
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.083
And the file system changes introduced in version 6.2~testoverlayfs are present 0.295
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.317
# 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.264
When the network is plugged 0.034
And Tor is ready 15.579
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.682
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.942
Given I shutdown Tails and wait for the computer to power off 4.020
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.828
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.009
And the file system changes introduced in version 6.3~testoverlayfs are present 0.570
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.304
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.234
When the network is plugged 0.049
And Tor is ready 13.831
Then the Upgrader considers the system as up-to-date 10.694
# 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.490
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.900
After features/support/hooks.rb:291 0.767
After features/support/hooks.rb:75 0.020
Tags: @product @automatic_upgrade
32.341
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.718
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.349
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the signing key used by the Upgrader is outdated 0.775
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 14.712
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.675
After features/support/hooks.rb:291 1.782
After features/support/hooks.rb:75 0.000