Project Number Date
test_Tails_ISO_devel 3472 09 Aug 2024, 12:36

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:20.047 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
2:19.860
Before features/support/hooks.rb:269 0.005
Given a computer 0.193
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 30.333
When I start Tails from USB drive "old" with network unplugged 1:44.204
Then the boot device has safe access rights 3.015
And Tails is running from USB drive "old" 0.340
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.313
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:326 6.892
After features/support/hooks.rb:100 0.010
Tags: @product
2:5.979
Before features/support/hooks.rb:269 0.005
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login 1:23.306
Then Tails is running from USB drive "old" 0.352
And I create a persistent partition 31.216
And I take note of which tps features are available 1.469
Then a Tails persistence partition exists on USB drive "old" 0.875
And I shutdown Tails and wait for the computer to power off 8.564
After features/support/hooks.rb:326 0.156
After features/support/hooks.rb:100 0.009
Tags: @product
2:40.352
Before features/support/hooks.rb:269 0.007
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:2.630
Then Tails is running from USB drive "old" 0.384
And all tps features are active 2.020
When I write some files expected to persist 1.663
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.235
And all persistence configuration files have safe access rights 0.415
And all persistent directories from the old Tails version have safe access rights 2.429
And I take note of which tps features are available 0.431
And I shutdown Tails and wait for the computer to power off 4.645
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.286
After features/support/hooks.rb:326 0.113
After features/support/hooks.rb:100 0.011
Tags: @product
2:32.824
Before features/support/hooks.rb:269 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.468
And I log in to a new session 21.504
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.604
And I plug USB drive "to_upgrade" 2.384
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.361
Then the running Tails is installed on USB drive "to_upgrade" 21.836
And I unplug USB drive "to_upgrade" 0.420
And I unplug USB drive "__internal" 0.243
After features/support/hooks.rb:326 2.431
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.385
Before features/support/hooks.rb:269 0.007
Given a computer 0.236
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.772
Then all tps features from the old Tails version are active 1.693
And Tails is running from USB drive "to_upgrade" 0.345
And the boot device has safe access rights 3.181
And the expected persistent files created with the old Tails version are present in the filesystem 1.722
And all persistent directories from the old Tails version have safe access rights 2.432
After features/support/hooks.rb:326 0.636
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
6:53.139
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.726
And no SquashFS delta is installed 0.092
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.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.296
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.437
When the network is plugged 0.075
And Tor is ready 20.673
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.792
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.142
Given I shutdown Tails and wait for the computer to power off 11.112
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.628
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.497
And the file system changes introduced in version 6.2~testoverlayfs are present 0.334
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.435
# 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.286
When the network is plugged 0.081
And Tor is ready 20.778
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.057
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.199
Given I shutdown Tails and wait for the computer to power off 6.592
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.060
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.982
And the file system changes introduced in version 6.3~testoverlayfs are present 0.563
And only the 6.3~testoverlayfs SquashFS delta is installed 0.127
# 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.428
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.289
When the network is plugged 0.076
And Tor is ready 44.651
Then the Upgrader considers the system as up-to-date 0.320
# 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.717
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.200
After features/support/hooks.rb:326 0.770
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
36.506
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.365
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.305
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 1.033
But a current signing key is available on our website 0.000
When the network is plugged 0.216
And Tor is ready 17.696
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.832
After features/support/hooks.rb:326 0.664
After features/support/hooks.rb:100 0.000