Project Number Date
test_Tails_ISO_stable 4752 27 Mar 2024, 16:17

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 17:19.973 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:36.135
Before features/support/hooks.rb:245 0.005
Given a computer 0.211
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 17.793
When I start Tails from USB drive "old" with network unplugged 1:12.767
Then the boot device has safe access rights 3.041
And Tails is running from USB drive "old" 0.322
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.085
And udev-watchdog is monitoring the correct device 0.440
And I unplug USB drive "old" 0.312
After features/support/hooks.rb:291 6.798
After features/support/hooks.rb:75 0.011
Tags: @product
1:59.232
Before features/support/hooks.rb:245 0.005
Given a computer 0.709
And I start Tails from USB drive "old" with network unplugged and I login 1:16.741
Then Tails is running from USB drive "old" 0.329
And I create a persistent partition 31.168
And I take note of which tps features are available 1.141
Then a Tails persistence partition exists on USB drive "old" 0.745
And I shutdown Tails and wait for the computer to power off 8.396
After features/support/hooks.rb:291 0.157
After features/support/hooks.rb:75 0.010
Tags: @product
2:29.675
Before features/support/hooks.rb:245 0.007
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:2.576
Then Tails is running from USB drive "old" 0.364
And all tps features are active 2.011
When I write some files expected to persist 1.585
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.190
And all persistence configuration files have safe access rights 0.355
And all persistent directories from the old Tails version have safe access rights 2.594
And I take note of which tps features are available 0.427
And I shutdown Tails and wait for the computer to power off 4.388
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.961
After features/support/hooks.rb:291 0.122
After features/support/hooks.rb:75 0.009
Tags: @product
2:22.752
Before features/support/hooks.rb:245 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 11.217
And I log in to a new session 14.157
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.225
And I plug USB drive "to_upgrade" 2.423
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.660
Then the running Tails is installed on USB drive "to_upgrade" 14.642
And I unplug USB drive "to_upgrade" 0.237
And I unplug USB drive "__internal" 0.187
After features/support/hooks.rb:291 1.857
After features/support/hooks.rb:75 0.000
Tags: @product
2:15.096
Before features/support/hooks.rb:245 0.007
Given a computer 0.186
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.078
Then all tps features from the old Tails version are active 1.508
And Tails is running from USB drive "to_upgrade" 0.358
And the boot device has safe access rights 3.138
And the expected persistent files created with the old Tails version are present in the filesystem 1.617
And all persistent directories from the old Tails version have safe access rights 2.207
After features/support/hooks.rb:291 0.678
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
6:3.429
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.647
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.342
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.259
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.425
When the network is plugged 0.043
And Tor is ready 18.688
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.052
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.237
Given I shutdown Tails and wait for the computer to power off 9.019
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.065
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 1.976
And the file system changes introduced in version 6.2~testoverlayfs are present 0.340
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.304
# 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.255
When the network is plugged 0.053
And Tor is ready 15.450
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.047
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.997
Given I shutdown Tails and wait for the computer to power off 4.356
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.244
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.837
And the file system changes introduced in version 6.3~testoverlayfs are present 0.511
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.357
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.266
When the network is plugged 0.039
And Tor is ready 17.798
Then the Upgrader considers the system as up-to-date 10.681
# 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 12.964
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.849
After features/support/hooks.rb:291 0.812
After features/support/hooks.rb:75 0.041
Tags: @product @automatic_upgrade
33.650
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.141
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.366
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 0.442
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 17.190
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.412
After features/support/hooks.rb:291 0.681
After features/support/hooks.rb:75 0.000