Project Number Date
test_Tails_ISO_devel 3455 11 Jul 2024, 13:03

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 22:2.287 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
3:21.561
Before features/support/hooks.rb:269 0.006
Given a computer 0.249
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 50.981
When I start Tails from USB drive "old" with network unplugged 2:25.301
Then the boot device has safe access rights 2.963
And Tails is running from USB drive "old" 0.298
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.303
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:326 7.047
After features/support/hooks.rb:100 0.010
Tags: @product
2:6.905
Before features/support/hooks.rb:269 0.006
Given a computer 1.858
And I start Tails from USB drive "old" with network unplugged and I login 1:24.929
Then Tails is running from USB drive "old" 0.398
And I create a persistent partition 30.554
And I take note of which tps features are available 1.811
Then a Tails persistence partition exists on USB drive "old" 0.884
And I shutdown Tails and wait for the computer to power off 6.468
After features/support/hooks.rb:326 0.152
After features/support/hooks.rb:100 0.010
Tags: @product
3:1.936
Before features/support/hooks.rb:269 0.008
Given a computer 0.319
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.285
Then Tails is running from USB drive "old" 0.418
And all tps features are active 2.389
When I write some files expected to persist 1.742
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.191
And all persistence configuration files have safe access rights 0.436
And all persistent directories from the old Tails version have safe access rights 2.737
And I take note of which tps features are available 0.602
And I shutdown Tails and wait for the computer to power off 4.518
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.294
After features/support/hooks.rb:326 0.166
After features/support/hooks.rb:100 0.014
Tags: @product
3:7.442
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 35.353
And I log in to a new session 22.119
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.852
And I plug USB drive "to_upgrade" 2.584
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.681
Then the running Tails is installed on USB drive "to_upgrade" 23.295
And I unplug USB drive "to_upgrade" 0.295
And I unplug USB drive "__internal" 0.259
After features/support/hooks.rb:326 3.488
After features/support/hooks.rb:100 0.000
Tags: @product
2:29.726
Before features/support/hooks.rb:269 0.011
Given a computer 0.307
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:19.127
Then all tps features from the old Tails version are active 1.766
And Tails is running from USB drive "to_upgrade" 0.326
And the boot device has safe access rights 3.927
And the expected persistent files created with the old Tails version are present in the filesystem 1.564
And all persistent directories from the old Tails version have safe access rights 2.707
After features/support/hooks.rb:326 0.882
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:9.134
Before features/support/hooks.rb:269 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 25.162
And no SquashFS delta is installed 0.111
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.406
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.457
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.516
When the network is plugged 0.058
And Tor is ready 23.519
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.453
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.278
Given I shutdown Tails and wait for the computer to power off 9.241
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.707
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 12.298
And the file system changes introduced in version 6.2~testoverlayfs are present 0.359
And only the 6.2~testoverlayfs SquashFS delta is installed 0.091
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.363
# 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.316
When the network is plugged 0.102
And Tor is ready 16.610
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.292
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.560
Given I shutdown Tails and wait for the computer to power off 6.542
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.587
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.556
And the file system changes introduced in version 6.3~testoverlayfs are present 0.674
And only the 6.3~testoverlayfs SquashFS delta is installed 0.093
# 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.398
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.323
When the network is plugged 0.068
And Tor is ready 19.517
Then the Upgrader considers the system as up-to-date 0.465
# 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 17.519
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.388
After features/support/hooks.rb:326 0.955
After features/support/hooks.rb:100 0.029
Tags: @product @automatic_upgrade
45.580
Before features/support/hooks.rb:269 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.338
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.428
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 1.607
But a current signing key is available on our website 0.000
When the network is plugged 0.046
And Tor is ready 20.153
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.938
After features/support/hooks.rb:326 0.842
After features/support/hooks.rb:100 0.000