Project Number Date
test_Tails_ISO_stable 4955 18 Jul 2024, 12:28

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 18:22.818 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:0.514
Before features/support/hooks.rb:269 0.006
Given a computer 0.219
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 28.744
When I start Tails from USB drive "old" with network unplugged 1:26.352
Then the boot device has safe access rights 3.074
And Tails is running from USB drive "old" 0.359
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.289
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:326 0.885
After features/support/hooks.rb:100 0.010
Tags: @product
2:3.813
Before features/support/hooks.rb:269 0.007
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login 1:22.139
Then Tails is running from USB drive "old" 0.333
And I create a persistent partition 30.766
And I take note of which tps features are available 1.413
Then a Tails persistence partition exists on USB drive "old" 0.737
And I shutdown Tails and wait for the computer to power off 8.214
After features/support/hooks.rb:326 0.165
After features/support/hooks.rb:100 0.009
Tags: @product
2:52.969
Before features/support/hooks.rb:269 0.006
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.217
Then Tails is running from USB drive "old" 0.407
And all tps features are active 2.054
When I write some files expected to persist 1.723
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.206
And all persistence configuration files have safe access rights 0.360
And all persistent directories from the old Tails version have safe access rights 2.464
And I take note of which tps features are available 0.463
And I shutdown Tails and wait for the computer to power off 4.268
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.607
After features/support/hooks.rb:326 0.154
After features/support/hooks.rb:100 0.010
Tags: @product
2:24.968
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.182
And I log in to a new session 17.504
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.428
And I plug USB drive "to_upgrade" 2.352
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.476
Then the running Tails is installed on USB drive "to_upgrade" 17.618
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:326 6.780
After features/support/hooks.rb:100 0.000
Tags: @product
2:2.900
Before features/support/hooks.rb:269 0.007
Given a computer 0.196
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:53.869
Then all tps features from the old Tails version are active 1.579
And Tails is running from USB drive "to_upgrade" 0.313
And the boot device has safe access rights 3.278
And the expected persistent files created with the old Tails version are present in the filesystem 1.334
And all persistent directories from the old Tails version have safe access rights 2.328
After features/support/hooks.rb:326 0.694
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:22.494
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 10.218
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.273
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.290
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.438
When the network is plugged 0.039
And Tor is ready 18.565
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.578
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.502
Given I shutdown Tails and wait for the computer to power off 8.680
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.767
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.032
And the file system changes introduced in version 6.2~testoverlayfs are present 0.339
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.345
# 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.272
When the network is plugged 0.074
And Tor is ready 18.771
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.381
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.660
Given I shutdown Tails and wait for the computer to power off 4.264
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.054
Then Tails is running version 6.3~testoverlayfs 0.022
And all tps features are active 1.895
And the file system changes introduced in version 6.3~testoverlayfs are present 0.510
And only the 6.3~testoverlayfs SquashFS delta is installed 0.134
# 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.485
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.316
When the network is plugged 0.045
And Tor is ready 19.153
Then the Upgrader considers the system as up-to-date 0.301
# 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.758
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.080
After features/support/hooks.rb:326 0.735
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
35.156
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 9.318
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.277
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 1.176
But a current signing key is available on our website 0.000
When the network is plugged 0.043
And Tor is ready 17.451
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.826
After features/support/hooks.rb:326 0.643
After features/support/hooks.rb:100 0.000