Project Number Date
test_Tails_ISO_devel 3272 08 Feb 2024, 17:28

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 88 0 0 0 0 88 7 0 7 18:52.305 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:31.166
Before features/support/hooks.rb:245 0.003
Given a computer 0.114
And I create a 7200 MiB disk named "old" 0.024
And I plug USB drive "old" 1.036
And I write an old version of the Tails USB image to disk "old" 18.675
When I start Tails from USB drive "old" with network unplugged 1:7.082
Then the boot device has safe access rights 3.015
And Tails is running from USB drive "old" 0.423
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.151
And udev-watchdog is monitoring the correct device 0.384
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:291 3.696
After features/support/hooks.rb:75 0.006
Tags: @product
2:9.926
Before features/support/hooks.rb:245 0.002
Given a computer 0.118
And I start Tails from USB drive "old" with network unplugged and I login 1:16.889
Then Tails is running from USB drive "old" 0.334
And I create a persistent partition 42.113
And I take note of which tps features are available 1.581
Then a Tails persistence partition exists on USB drive "old" 0.803
And I shutdown Tails and wait for the computer to power off 8.085
After features/support/hooks.rb:291 0.209
After features/support/hooks.rb:75 0.007
Tags: @product
2:40.386
Before features/support/hooks.rb:245 0.002
Given a computer 0.130
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.358
Then Tails is running from USB drive "old" 0.353
And all tps features are active 1.749
When I write some files expected to persist 1.588
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.218
And all persistence configuration files have safe access rights 0.381
And all persistent directories from the old Tails version have safe access rights 2.342
And I take note of which tps features are available 0.267
And I shutdown Tails and wait for the computer to power off 4.049
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.944
After features/support/hooks.rb:291 0.149
After features/support/hooks.rb:75 0.006
Tags: @product
2:36.555
Before features/support/hooks.rb:245 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.274
And I log in to a new session 18.724
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.448
And I plug USB drive "to_upgrade" 2.376
And I cancel the GNOME authentication prompt 1.799
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.632
Then the running Tails is installed on USB drive "to_upgrade" 12.865
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.221
After features/support/hooks.rb:291 6.885
After features/support/hooks.rb:75 0.000
Tags: @product
2:25.152
Before features/support/hooks.rb:245 0.004
Given a computer 0.107
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.364
Then all tps features from the old Tails version are active 1.514
And Tails is running from USB drive "to_upgrade" 0.392
And the boot device has safe access rights 3.407
And the expected persistent files created with the old Tails version are present in the filesystem 1.628
And all persistent directories from the old Tails version have safe access rights 2.738
After features/support/hooks.rb:291 0.826
After features/support/hooks.rb:75 0.029
Tags: @product @automatic_upgrade
6:54.559
Before features/support/hooks.rb:245 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.396
And no SquashFS delta is installed 0.070
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.270
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.093
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.361
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.462
When the network is plugged 0.028
And Tor is ready 19.471
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.037
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.265
Given I shutdown Tails and wait for the computer to power off 7.517
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.901
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 1.965
And the file system changes introduced in version 6.2~testoverlayfs are present 0.295
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.306
# 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.330
When the network is plugged 0.023
And Tor is ready 20.713
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.588
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.125
Given I shutdown Tails and wait for the computer to power off 4.272
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:20.172
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 1.746
And the file system changes introduced in version 6.3~testoverlayfs are present 0.464
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.362
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.272
When the network is plugged 0.027
And Tor is ready 17.711
Then the Upgrader considers the system as up-to-date 10.713
# 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.364
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.041
After features/support/hooks.rb:291 0.822
After features/support/hooks.rb:75 0.016
Tags: @product @automatic_upgrade
34.558
Before features/support/hooks.rb:245 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.138
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.313
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.458
But a current signing key is available on our website 0.000
When the network is plugged 0.022
And Tor is ready 18.298
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.272
After features/support/hooks.rb:291 1.162
After features/support/hooks.rb:75 0.000