Project Number Date
test_Tails_ISO_stable 4754 28 Mar 2024, 11:54

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 16:48.808 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:35.603
Before features/support/hooks.rb:245 0.005
Given a computer 0.254
And I create a 7200 MiB disk named "old" 0.088
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 22.251
When I start Tails from USB drive "old" with network unplugged 1:7.716
Then the boot device has safe access rights 3.231
And Tails is running from USB drive "old" 0.350
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.109
And udev-watchdog is monitoring the correct device 0.306
And I unplug USB drive "old" 0.171
After features/support/hooks.rb:291 6.845
After features/support/hooks.rb:75 0.008
Tags: @product
2:7.985
Before features/support/hooks.rb:245 0.005
Given a computer 0.164
And I start Tails from USB drive "old" with network unplugged and I login 1:22.317
Then Tails is running from USB drive "old" 0.297
And I create a persistent partition 33.849
And I take note of which tps features are available 1.532
Then a Tails persistence partition exists on USB drive "old" 1.120
And I shutdown Tails and wait for the computer to power off 8.704
After features/support/hooks.rb:291 0.156
After features/support/hooks.rb:75 0.008
Tags: @product
2:26.561
Before features/support/hooks.rb:245 0.005
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:59.140
Then Tails is running from USB drive "old" 0.359
And all tps features are active 2.285
When I write some files expected to persist 1.624
# 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.381
And all persistent directories from the old Tails version have safe access rights 2.732
And I take note of which tps features are available 0.585
And I shutdown Tails and wait for the computer to power off 4.357
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.711
After features/support/hooks.rb:291 0.117
After features/support/hooks.rb:75 0.008
Tags: @product
2:18.520
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 9.524
And I log in to a new session 15.231
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.387
And I plug USB drive "to_upgrade" 2.459
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.627
Then the running Tails is installed on USB drive "to_upgrade" 12.924
And I unplug USB drive "to_upgrade" 0.193
And I unplug USB drive "__internal" 0.173
After features/support/hooks.rb:291 6.450
After features/support/hooks.rb:75 0.000
Tags: @product
2:3.974
Before features/support/hooks.rb:245 0.006
Given a computer 0.168
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:55.906
Then all tps features from the old Tails version are active 1.349
And Tails is running from USB drive "to_upgrade" 0.289
And the boot device has safe access rights 2.638
And the expected persistent files created with the old Tails version are present in the filesystem 1.540
And all persistent directories from the old Tails version have safe access rights 2.082
After features/support/hooks.rb:291 0.752
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
5:42.213
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.720
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.327
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.340
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.400
When the network is plugged 0.027
And Tor is ready 16.814
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.542
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.163
Given I shutdown Tails and wait for the computer to power off 6.735
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:47.605
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.017
And the file system changes introduced in version 6.2~testoverlayfs are present 0.317
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.285
# 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.276
When the network is plugged 0.029
And Tor is ready 14.871
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.493
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.294
Given I shutdown Tails and wait for the computer to power off 4.404
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.563
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 1.621
And the file system changes introduced in version 6.3~testoverlayfs are present 0.485
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.333
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.247
When the network is plugged 0.038
And Tor is ready 17.700
Then the Upgrader considers the system as up-to-date 0.238
# 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.192
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.825
After features/support/hooks.rb:291 0.767
After features/support/hooks.rb:75 0.019
Tags: @product @automatic_upgrade
33.949
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.527
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.315
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.833
But a current signing key is available on our website 0.000
When the network is plugged 0.040
And Tor is ready 17.807
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.377
After features/support/hooks.rb:291 0.605
After features/support/hooks.rb:75 0.000