Project Number Date
test_Tails_ISO_stable 4909 22 Jun 2024, 12:25

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 20:23.531 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:33.408
Before features/support/hooks.rb:269 0.004
Given a computer 0.213
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 31.347
When I start Tails from USB drive "old" with network unplugged 1:56.806
Then the boot device has safe access rights 3.023
And Tails is running from USB drive "old" 0.304
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.310
And I unplug USB drive "old" 0.170
After features/support/hooks.rb:326 7.376
After features/support/hooks.rb:100 0.008
Tags: @product
2:1.863
Before features/support/hooks.rb:269 0.004
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login 1:18.571
Then Tails is running from USB drive "old" 0.317
And I create a persistent partition 32.282
And I take note of which tps features are available 1.365
Then a Tails persistence partition exists on USB drive "old" 0.834
And I shutdown Tails and wait for the computer to power off 8.289
After features/support/hooks.rb:326 0.188
After features/support/hooks.rb:100 0.010
Tags: @product
2:55.500
Before features/support/hooks.rb:269 0.007
Given a computer 0.656
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.199
Then Tails is running from USB drive "old" 0.334
And all tps features are active 1.917
When I write some files expected to persist 1.627
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.261
And all persistence configuration files have safe access rights 0.365
And all persistent directories from the old Tails version have safe access rights 2.394
And I take note of which tps features are available 0.460
And I shutdown Tails and wait for the computer to power off 4.267
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.015
After features/support/hooks.rb:326 0.100
After features/support/hooks.rb:100 0.009
Tags: @product
2:25.764
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.573
And I log in to a new session 21.449
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.433
And I plug USB drive "to_upgrade" 2.411
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.945
Then the running Tails is installed on USB drive "to_upgrade" 16.389
And I unplug USB drive "to_upgrade" 0.227
And I unplug USB drive "__internal" 0.333
After features/support/hooks.rb:326 2.535
After features/support/hooks.rb:100 0.000
Tags: @product
2:6.471
Before features/support/hooks.rb:269 0.006
Given a computer 0.244
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:56.827
Then all tps features from the old Tails version are active 1.626
And Tails is running from USB drive "to_upgrade" 0.346
And the boot device has safe access rights 3.132
And the expected persistent files created with the old Tails version are present in the filesystem 1.765
And all persistent directories from the old Tails version have safe access rights 2.529
After features/support/hooks.rb:326 0.620
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:39.234
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.484
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.318
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.328
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.404
When the network is plugged 0.033
And Tor is ready 48.845
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.611
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.482
Given I shutdown Tails and wait for the computer to power off 1:12.513
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.677
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.110
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.349
# 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.267
When the network is plugged 0.054
And Tor is ready 18.257
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.145
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.686
Given I shutdown Tails and wait for the computer to power off 4.399
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.584
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.042
And the file system changes introduced in version 6.3~testoverlayfs are present 0.465
And only the 6.3~testoverlayfs SquashFS delta is installed 0.091
# 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.353
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.364
When the network is plugged 0.055
And Tor is ready 18.277
Then the Upgrader considers the system as up-to-date 0.355
# 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.226
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.926
After features/support/hooks.rb:326 0.780
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
41.288
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 15.009
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.359
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
And the signing key used by the Upgrader is outdated 1.187
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 18.018
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.590
After features/support/hooks.rb:326 0.663
After features/support/hooks.rb:100 0.000