Project Number Date
test_Tails_ISO_devel 3623 26 Dec 2024, 12:30

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:18.620 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:4.590
Before features/support/hooks.rb:269 0.006
Given a computer 0.189
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 29.355
When I start Tails from USB drive "old" with network unplugged 1:29.868
Then the boot device has safe access rights 3.126
And Tails is running from USB drive "old" 0.298
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.307
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:326 12.143
After features/support/hooks.rb:100 0.010
Tags: @product
2:6.694
Before features/support/hooks.rb:269 0.005
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login 1:23.709
Then Tails is running from USB drive "old" 0.313
And I create a persistent partition 31.986
And I take note of which tps features are available 1.308
Then a Tails persistence partition exists on USB drive "old" 0.844
And I shutdown Tails and wait for the computer to power off 8.356
After features/support/hooks.rb:326 0.171
After features/support/hooks.rb:100 0.007
Tags: @product
2:51.855
Before features/support/hooks.rb:269 0.005
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.787
Then Tails is running from USB drive "old" 0.611
And all tps features are active 2.085
When I write some files expected to persist 1.694
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.210
And all persistence configuration files have safe access rights 0.386
And all persistent directories from the old Tails version have safe access rights 2.959
And I take note of which tps features are available 0.518
And I shutdown Tails and wait for the computer to power off 4.289
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.079
After features/support/hooks.rb:326 0.141
After features/support/hooks.rb:100 0.023
Tags: @product
2:31.320
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.855
And I log in to a new session 18.724
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.447
And I plug USB drive "to_upgrade" 2.396
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.901
Then the running Tails is installed on USB drive "to_upgrade" 18.593
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:326 2.394
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.027
Before features/support/hooks.rb:269 0.005
Given a computer 0.191
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.753
Then all tps features from the old Tails version are active 1.681
And Tails is running from USB drive "to_upgrade" 0.336
And the boot device has safe access rights 3.233
And the expected persistent files created with the old Tails version are present in the filesystem 1.441
And all persistent directories from the old Tails version have safe access rights 2.389
After features/support/hooks.rb:326 0.617
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:58.198
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 12.295
And no SquashFS delta is installed 0.109
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.306
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.302
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.430
When the network is plugged 0.088
And Tor is ready 21.305
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.998
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.177
Given I shutdown Tails and wait for the computer to power off 11.150
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.003
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.081
And the file system changes introduced in version 6.2~testoverlayfs are present 0.370
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.514
# 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.288
When the network is plugged 0.066
And Tor is ready 17.972
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.202
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.089
Given I shutdown Tails and wait for the computer to power off 4.326
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.921
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.989
And the file system changes introduced in version 6.3~testoverlayfs are present 0.461
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.286
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.309
When the network is plugged 0.082
And Tor is ready 46.046
Then the Upgrader considers the system as up-to-date 0.345
# 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.463
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.980
After features/support/hooks.rb:326 0.854
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
32.933
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 9.728
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.332
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 0.723
But a current signing key is available on our website 0.000
When the network is plugged 0.060
And Tor is ready 15.409
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.609
After features/support/hooks.rb:326 0.879
After features/support/hooks.rb:100 0.000