Project Number Date
test_Tails_ISO_stable 5155 07 Oct 2024, 19:32

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:53.294 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:20.784
Before features/support/hooks.rb:269 0.005
Given a computer 0.199
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 28.102
When I start Tails from USB drive "old" with network unplugged 1:47.363
Then the boot device has safe access rights 3.019
And Tails is running from USB drive "old" 0.328
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.310
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:326 3.556
After features/support/hooks.rb:100 0.009
Tags: @product
2:7.974
Before features/support/hooks.rb:269 0.007
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login 1:23.593
Then Tails is running from USB drive "old" 0.360
And I create a persistent partition 32.653
And I take note of which tps features are available 1.622
Then a Tails persistence partition exists on USB drive "old" 0.926
And I shutdown Tails and wait for the computer to power off 8.607
After features/support/hooks.rb:326 0.168
After features/support/hooks.rb:100 0.009
Tags: @product
2:54.347
Before features/support/hooks.rb:269 0.006
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.525
Then Tails is running from USB drive "old" 0.484
And all tps features are active 2.033
When I write some files expected to persist 2.093
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.490
And all persistence configuration files have safe access rights 0.439
And all persistent directories from the old Tails version have safe access rights 2.489
And I take note of which tps features are available 0.514
And I shutdown Tails and wait for the computer to power off 4.328
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.755
After features/support/hooks.rb:326 0.131
After features/support/hooks.rb:100 0.012
Tags: @product
2:33.852
Before features/support/hooks.rb:269 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 11.756
And I log in to a new session 21.330
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.638
And I plug USB drive "to_upgrade" 2.401
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.759
Then the running Tails is installed on USB drive "to_upgrade" 21.554
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.214
After features/support/hooks.rb:326 7.056
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.145
Before features/support/hooks.rb:269 0.014
Given a computer 0.673
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.733
Then all tps features from the old Tails version are active 2.040
And Tails is running from USB drive "to_upgrade" 0.445
And the boot device has safe access rights 3.875
And the expected persistent files created with the old Tails version are present in the filesystem 1.659
And all persistent directories from the old Tails version have safe access rights 2.717
After features/support/hooks.rb:326 0.688
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:0.098
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.500
And no SquashFS delta is installed 0.104
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.544
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.135
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.543
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.458
When the network is plugged 0.099
And Tor is ready 26.364
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.817
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.029
Given I shutdown Tails and wait for the computer to power off 11.252
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.631
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.338
And the file system changes introduced in version 6.2~testoverlayfs are present 0.314
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.475
# 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.430
When the network is plugged 0.072
And Tor is ready 19.231
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.389
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.522
Given I shutdown Tails and wait for the computer to power off 4.507
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.229
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 3.638
And the file system changes introduced in version 6.3~testoverlayfs are present 0.589
And only the 6.3~testoverlayfs SquashFS delta is installed 0.104
# 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.523
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.433
When the network is plugged 0.100
And Tor is ready 18.428
Then the Upgrader considers the system as up-to-date 10.967
# 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 15.889
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.325
After features/support/hooks.rb:326 0.792
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
41.091
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.832
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.486
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.081
And the signing key used by the Upgrader is outdated 1.005
But a current signing key is available on our website 0.000
When the network is plugged 0.115
And Tor is ready 20.658
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.910
After features/support/hooks.rb:326 0.992
After features/support/hooks.rb:100 0.000