Project Number Date
test_Tails_ISO_stable 4770 04 Apr 2024, 18:25

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:11.748 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:56.098
Before features/support/hooks.rb:245 0.004
Given a computer 0.179
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.065
And I write an old version of the Tails USB image to disk "old" 22.519
When I start Tails from USB drive "old" with network unplugged 1:28.175
Then the boot device has safe access rights 3.096
And Tails is running from USB drive "old" 0.306
And there is no persistence partition on USB drive "old" 0.086
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.317
And I unplug USB drive "old" 0.205
After features/support/hooks.rb:291 6.831
After features/support/hooks.rb:75 0.009
Tags: @product
2:2.214
Before features/support/hooks.rb:245 0.007
Given a computer 0.237
And I start Tails from USB drive "old" with network unplugged and I login 1:17.067
Then Tails is running from USB drive "old" 0.319
And I create a persistent partition 34.079
And I take note of which tps features are available 1.422
Then a Tails persistence partition exists on USB drive "old" 0.763
And I shutdown Tails and wait for the computer to power off 8.324
After features/support/hooks.rb:291 0.206
After features/support/hooks.rb:75 0.009
Tags: @product
2:29.101
Before features/support/hooks.rb:245 0.004
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:1.341
Then Tails is running from USB drive "old" 0.318
And all tps features are active 2.056
When I write some files expected to persist 1.565
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.371
And all persistent directories from the old Tails version have safe access rights 2.423
And I take note of which tps features are available 0.457
And I shutdown Tails and wait for the computer to power off 4.352
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.779
After features/support/hooks.rb:291 0.170
After features/support/hooks.rb:75 0.009
Tags: @product
2:19.133
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.054
And I log in to a new session 15.403
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.411
And I plug USB drive "to_upgrade" 2.393
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.037
Then the running Tails is installed on USB drive "to_upgrade" 14.450
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.176
After features/support/hooks.rb:291 2.748
After features/support/hooks.rb:75 0.000
Tags: @product
2:3.489
Before features/support/hooks.rb:245 0.014
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:54.500
Then all tps features from the old Tails version are active 1.507
And Tails is running from USB drive "to_upgrade" 0.304
And the boot device has safe access rights 3.062
And the expected persistent files created with the old Tails version are present in the filesystem 1.325
And all persistent directories from the old Tails version have safe access rights 2.590
After features/support/hooks.rb:291 0.834
After features/support/hooks.rb:75 0.035
Tags: @product @automatic_upgrade
5:48.838
Before features/support/hooks.rb:245 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.893
And no SquashFS delta is installed 0.147
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.274
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.285
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.444
When the network is plugged 0.037
And Tor is ready 19.423
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.172
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.373
Given I shutdown Tails and wait for the computer to power off 6.653
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.160
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.213
And the file system changes introduced in version 6.2~testoverlayfs are present 0.287
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.288
# 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.273
When the network is plugged 0.037
And Tor is ready 17.009
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.233
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.173
Given I shutdown Tails and wait for the computer to power off 4.461
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.675
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.829
And the file system changes introduced in version 6.3~testoverlayfs are present 0.416
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.275
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.231
When the network is plugged 0.044
And Tor is ready 15.819
Then the Upgrader considers the system as up-to-date 0.263
# 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 14.400
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.841
After features/support/hooks.rb:291 0.671
After features/support/hooks.rb:75 0.018
Tags: @product @automatic_upgrade
32.871
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.015
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.279
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.544
But a current signing key is available on our website 0.000
When the network is plugged 0.044
And Tor is ready 15.586
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.335
After features/support/hooks.rb:291 0.870
After features/support/hooks.rb:75 0.000