Project Number Date
test_Tails_ISO_stable 5264 14 Nov 2024, 12:49

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:15.099 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:21.594
Before features/support/hooks.rb:269 0.004
Given a computer 0.220
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 34.413
When I start Tails from USB drive "old" with network unplugged 1:41.529
Then the boot device has safe access rights 3.272
And Tails is running from USB drive "old" 0.378
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.109
And udev-watchdog is monitoring the correct device 0.310
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:326 7.322
After features/support/hooks.rb:100 0.010
Tags: @product
2:11.495
Before features/support/hooks.rb:269 0.006
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login 1:26.442
Then Tails is running from USB drive "old" 0.415
And I create a persistent partition 33.273
And I take note of which tps features are available 1.817
Then a Tails persistence partition exists on USB drive "old" 0.984
And I shutdown Tails and wait for the computer to power off 8.349
After features/support/hooks.rb:326 0.222
After features/support/hooks.rb:100 0.012
Tags: @product
2:56.243
Before features/support/hooks.rb:269 0.007
Given a computer 0.204
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.738
Then Tails is running from USB drive "old" 0.874
And all tps features are active 2.186
When I write some files expected to persist 2.010
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.364
And all persistence configuration files have safe access rights 0.774
And all persistent directories from the old Tails version have safe access rights 3.156
And I take note of which tps features are available 0.496
And I shutdown Tails and wait for the computer to power off 4.063
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.373
After features/support/hooks.rb:326 0.095
After features/support/hooks.rb:100 0.009
Tags: @product
2:39.900
Before features/support/hooks.rb:269 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 12.803
And I log in to a new session 20.709
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.802
And I plug USB drive "to_upgrade" 2.471
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.823
Then the running Tails is installed on USB drive "to_upgrade" 24.855
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.226
After features/support/hooks.rb:326 3.517
After features/support/hooks.rb:100 0.000
Tags: @product
2:32.594
Before features/support/hooks.rb:269 0.007
Given a computer 0.197
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:21.796
Then all tps features from the old Tails version are active 1.851
And Tails is running from USB drive "to_upgrade" 0.415
And the boot device has safe access rights 3.947
And the expected persistent files created with the old Tails version are present in the filesystem 1.644
And all persistent directories from the old Tails version have safe access rights 2.739
After features/support/hooks.rb:326 0.936
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
6:53.114
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.910
And no SquashFS delta is installed 0.129
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.433
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.105
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.304
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.475
When the network is plugged 0.108
And Tor is ready 29.188
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.497
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.375
Given I shutdown Tails and wait for the computer to power off 8.771
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.070
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.518
And the file system changes introduced in version 6.2~testoverlayfs are present 0.354
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.361
# 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.523
When the network is plugged 0.105
And Tor is ready 17.590
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.669
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.684
Given I shutdown Tails and wait for the computer to power off 4.556
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.524
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 2.371
And the file system changes introduced in version 6.3~testoverlayfs are present 0.539
And only the 6.3~testoverlayfs SquashFS delta is installed 0.087
# 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.415
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.358
When the network is plugged 0.074
And Tor is ready 22.455
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 15.993
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.124
After features/support/hooks.rb:326 0.789
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
40.157
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 10.638
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.641
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.100
And the signing key used by the Upgrader is outdated 1.326
But a current signing key is available on our website 0.000
When the network is plugged 0.081
And Tor is ready 21.905
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.464
After features/support/hooks.rb:326 0.692
After features/support/hooks.rb:100 0.000