Project Number Date
test_Tails_ISO_stable 5367 05 Jan 2025, 12:23

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:15.224 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:20.278
Before features/support/hooks.rb:269 0.004
Given a computer 0.183
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 32.133
When I start Tails from USB drive "old" with network unplugged 1:42.905
Then the boot device has safe access rights 3.003
And Tails is running from USB drive "old" 0.305
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.304
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:326 10.329
After features/support/hooks.rb:100 0.010
Tags: @product
2:10.484
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:26.742
Then Tails is running from USB drive "old" 0.313
And I create a persistent partition 32.494
And I take note of which tps features are available 1.418
Then a Tails persistence partition exists on USB drive "old" 0.848
And I shutdown Tails and wait for the computer to power off 8.479
After features/support/hooks.rb:326 0.184
After features/support/hooks.rb:100 0.009
Tags: @product
2:50.363
Before features/support/hooks.rb:269 0.006
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.347
Then Tails is running from USB drive "old" 0.403
And all tps features are active 1.906
When I write some files expected to persist 2.354
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.203
And all persistence configuration files have safe access rights 0.365
And all persistent directories from the old Tails version have safe access rights 3.363
And I take note of which tps features are available 0.434
And I shutdown Tails and wait for the computer to power off 4.351
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.428
After features/support/hooks.rb:326 0.102
After features/support/hooks.rb:100 0.009
Tags: @product
2:34.333
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 11.277
And I log in to a new session 20.466
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.640
And I plug USB drive "to_upgrade" 2.412
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.038
Then the running Tails is installed on USB drive "to_upgrade" 23.081
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:326 3.071
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.044
Before features/support/hooks.rb:269 0.006
Given a computer 0.212
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.664
Then all tps features from the old Tails version are active 1.622
And Tails is running from USB drive "to_upgrade" 0.349
And the boot device has safe access rights 3.131
And the expected persistent files created with the old Tails version are present in the filesystem 1.565
And all persistent directories from the old Tails version have safe access rights 2.500
After features/support/hooks.rb:326 0.704
After features/support/hooks.rb:100 0.032
Tags: @product @automatic_upgrade
6:31.296
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 13.741
And no SquashFS delta is installed 0.147
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.492
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.087
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.430
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.450
When the network is plugged 0.074
And Tor is ready 22.964
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.874
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.824
Given I shutdown Tails and wait for the computer to power off 15.011
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.208
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.018
And the file system changes introduced in version 6.2~testoverlayfs are present 0.375
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.351
# 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.353
When the network is plugged 0.079
And Tor is ready 17.701
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.444
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.475
Given I shutdown Tails and wait for the computer to power off 4.282
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.163
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.980
And the file system changes introduced in version 6.3~testoverlayfs are present 0.473
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.285
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.273
When the network is plugged 0.081
And Tor is ready 19.782
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.345
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.026
After features/support/hooks.rb:326 0.752
After features/support/hooks.rb:100 0.061
Tags: @product @automatic_upgrade
37.424
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 11.062
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.381
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the signing key used by the Upgrader is outdated 0.138
But a current signing key is available on our website 0.000
When the network is plugged 0.115
And Tor is ready 18.746
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.908
After features/support/hooks.rb:326 1.055
After features/support/hooks.rb:100 0.000