Project Number Date
test_Tails_ISO_stable 4713 13 Mar 2024, 12:24

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 19:49.415 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:51.779
Before features/support/hooks.rb:245 0.005
Given a computer 0.193
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 21.875
When I start Tails from USB drive "old" with network unplugged 1:24.583
Then the boot device has safe access rights 3.142
And Tails is running from USB drive "old" 0.296
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.080
And udev-watchdog is monitoring the correct device 0.257
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:291 6.829
After features/support/hooks.rb:75 0.010
Tags: @product
2:12.136
Before features/support/hooks.rb:245 0.005
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login 1:17.715
Then Tails is running from USB drive "old" 0.321
And I create a persistent partition 43.369
And I take note of which tps features are available 2.358
Then a Tails persistence partition exists on USB drive "old" 1.142
And I shutdown Tails and wait for the computer to power off 7.042
After features/support/hooks.rb:291 0.197
After features/support/hooks.rb:75 0.018
Tags: @product
2:43.283
Before features/support/hooks.rb:245 0.008
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.922
Then Tails is running from USB drive "old" 0.332
And all tps features are active 1.867
When I write some files expected to persist 1.625
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.179
And all persistence configuration files have safe access rights 0.367
And all persistent directories from the old Tails version have safe access rights 2.360
And I take note of which tps features are available 0.447
And I shutdown Tails and wait for the computer to power off 4.021
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.948
After features/support/hooks.rb:291 0.242
After features/support/hooks.rb:75 0.010
Tags: @product
2:45.424
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 19.446
And I log in to a new session 17.800
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.597
And I plug USB drive "to_upgrade" 2.463
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.151
Then the running Tails is installed on USB drive "to_upgrade" 14.827
And I unplug USB drive "to_upgrade" 0.758
And I unplug USB drive "__internal" 0.378
After features/support/hooks.rb:291 1.871
After features/support/hooks.rb:75 0.000
Tags: @product
2:25.542
Before features/support/hooks.rb:245 0.008
Given a computer 0.286
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.100
Then all tps features from the old Tails version are active 1.589
And Tails is running from USB drive "to_upgrade" 0.322
And the boot device has safe access rights 3.374
And the expected persistent files created with the old Tails version are present in the filesystem 1.491
And all persistent directories from the old Tails version have safe access rights 2.377
After features/support/hooks.rb:291 0.731
After features/support/hooks.rb:75 0.011
Tags: @product @automatic_upgrade
7:15.064
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 11.312
And no SquashFS delta is installed 0.494
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.381
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.255
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.447
When the network is plugged 0.047
And Tor is ready 20.492
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.912
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.553
Given I shutdown Tails and wait for the computer to power off 7.031
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:21.269
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.178
And the file system changes introduced in version 6.2~testoverlayfs are present 0.298
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.375
# 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.253
When the network is plugged 0.059
And Tor is ready 19.017
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.618
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.068
Given I shutdown Tails and wait for the computer to power off 4.024
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.710
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 1.845
And the file system changes introduced in version 6.3~testoverlayfs are present 0.505
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.368
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.279
When the network is plugged 0.038
And Tor is ready 43.158
Then the Upgrader considers the system as up-to-date 0.331
# 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.427
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.057
After features/support/hooks.rb:291 0.811
After features/support/hooks.rb:75 0.021
Tags: @product @automatic_upgrade
36.184
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 12.773
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.271
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.865
But a current signing key is available on our website 0.000
When the network is plugged 0.044
And Tor is ready 16.535
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.649
After features/support/hooks.rb:291 0.861
After features/support/hooks.rb:75 0.000