Project Number Date
test_Tails_ISO_devel 3381 09 May 2024, 12:31

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:48.234 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:57.537
Before features/support/hooks.rb:259 0.005
Given a computer 0.177
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 30.858
When I start Tails from USB drive "old" with network unplugged 1:21.463
Then the boot device has safe access rights 2.946
And Tails is running from USB drive "old" 0.366
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.088
And udev-watchdog is monitoring the correct device 0.321
And I unplug USB drive "old" 0.175
After features/support/hooks.rb:305 3.622
After features/support/hooks.rb:89 0.031
Tags: @product
2:5.441
Before features/support/hooks.rb:259 0.007
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login 1:22.162
Then Tails is running from USB drive "old" 0.342
And I create a persistent partition 34.063
And I take note of which tps features are available 1.337
Then a Tails persistence partition exists on USB drive "old" 0.855
And I shutdown Tails and wait for the computer to power off 6.504
After features/support/hooks.rb:305 0.154
After features/support/hooks.rb:89 0.011
Tags: @product
2:52.809
Before features/support/hooks.rb:259 0.006
Given a computer 0.172
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.806
Then Tails is running from USB drive "old" 0.354
And all tps features are active 1.880
When I write some files expected to persist 1.802
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.259
And all persistence configuration files have safe access rights 0.451
And all persistent directories from the old Tails version have safe access rights 2.337
And I take note of which tps features are available 0.418
And I shutdown Tails and wait for the computer to power off 4.134
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.192
After features/support/hooks.rb:305 0.129
After features/support/hooks.rb:89 0.010
Tags: @product
2:28.398
Before features/support/hooks.rb:259 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 12.305
And I log in to a new session 18.128
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.691
And I plug USB drive "to_upgrade" 2.533
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.113
Then the running Tails is installed on USB drive "to_upgrade" 19.228
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.180
After features/support/hooks.rb:305 3.860
After features/support/hooks.rb:89 0.000
Tags: @product
2:14.037
Before features/support/hooks.rb:259 0.007
Given a computer 0.448
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.174
Then all tps features from the old Tails version are active 1.578
And Tails is running from USB drive "to_upgrade" 0.297
And the boot device has safe access rights 3.238
And the expected persistent files created with the old Tails version are present in the filesystem 1.811
And all persistent directories from the old Tails version have safe access rights 2.488
After features/support/hooks.rb:305 0.679
After features/support/hooks.rb:89 0.009
Tags: @product @automatic_upgrade
8:3.187
Before features/support/hooks.rb:259 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.441
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.493
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.274
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.293
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.520
When the network is plugged 0.033
And Tor is ready 48.815
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.681
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.907
Given I shutdown Tails and wait for the computer to power off 8.852
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.188
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.344
And the file system changes introduced in version 6.2~testoverlayfs are present 0.321
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.323
# 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.282
When the network is plugged 0.041
And Tor is ready 21.449
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.321
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.512
Given I shutdown Tails and wait for the computer to power off 5.730
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:24.985
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.373
And the file system changes introduced in version 6.3~testoverlayfs are present 0.519
And only the 6.3~testoverlayfs SquashFS delta is installed 0.088
# 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.350
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.305
When the network is plugged 0.037
And Tor is ready 48.007
Then the Upgrader considers the system as up-to-date 0.377
# 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 20.666
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.461
After features/support/hooks.rb:305 0.952
After features/support/hooks.rb:89 0.030
Tags: @product @automatic_upgrade
1:6.821
Before features/support/hooks.rb:259 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.364
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.396
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.136
And the signing key used by the Upgrader is outdated 0.666
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 49.513
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.707
After features/support/hooks.rb:305 0.826
After features/support/hooks.rb:89 0.000