Project Number Date
test_Tails_ISO_stable 5293 26 Nov 2024, 13:04

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 21:47.392 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:5.894
Before features/support/hooks.rb:269 0.009
Given a computer 0.449
And I create a 7200 MiB disk named "old" 0.058
And I plug USB drive "old" 1.081
And I write an old version of the Tails USB image to disk "old" 1:5.855
When I start Tails from USB drive "old" with network unplugged 1:53.305
Then the boot device has safe access rights 3.889
And Tails is running from USB drive "old" 0.387
And there is no persistence partition on USB drive "old" 0.095
And process "udev-watchdog" is running 0.149
And udev-watchdog is monitoring the correct device 0.411
And I unplug USB drive "old" 0.210
After features/support/hooks.rb:326 7.564
After features/support/hooks.rb:100 0.012
Tags: @product
2:15.092
Before features/support/hooks.rb:269 0.007
Given a computer 0.268
And I start Tails from USB drive "old" with network unplugged and I login 1:27.706
Then Tails is running from USB drive "old" 0.400
And I create a persistent partition 35.020
And I take note of which tps features are available 2.032
Then a Tails persistence partition exists on USB drive "old" 1.008
And I shutdown Tails and wait for the computer to power off 8.655
After features/support/hooks.rb:326 0.663
After features/support/hooks.rb:100 0.021
Tags: @product
3:11.353
Before features/support/hooks.rb:269 0.012
Given a computer 0.303
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:31.427
Then Tails is running from USB drive "old" 0.446
And all tps features are active 2.584
When I write some files expected to persist 1.719
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.247
And all persistence configuration files have safe access rights 0.389
And all persistent directories from the old Tails version have safe access rights 2.579
And I take note of which tps features are available 0.741
And I shutdown Tails and wait for the computer to power off 4.477
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.435
After features/support/hooks.rb:326 0.181
After features/support/hooks.rb:100 0.012
Tags: @product
2:56.949
Before features/support/hooks.rb:269 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 30.185
And I log in to a new session 22.156
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.992
And I plug USB drive "to_upgrade" 2.524
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.364
Then the running Tails is installed on USB drive "to_upgrade" 24.251
And I unplug USB drive "to_upgrade" 0.250
And I unplug USB drive "__internal" 0.223
After features/support/hooks.rb:326 1.954
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.227
Before features/support/hooks.rb:269 0.006
Given a computer 0.258
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.088
Then all tps features from the old Tails version are active 1.812
And Tails is running from USB drive "to_upgrade" 0.327
And the boot device has safe access rights 3.685
And the expected persistent files created with the old Tails version are present in the filesystem 1.454
And all persistent directories from the old Tails version have safe access rights 2.601
After features/support/hooks.rb:326 0.841
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:17.471
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 12.395
And no SquashFS delta is installed 0.117
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.465
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.153
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.305
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.493
When the network is plugged 0.083
And Tor is ready 49.712
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.674
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.825
Given I shutdown Tails and wait for the computer to power off 11.031
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.529
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.470
And the file system changes introduced in version 6.2~testoverlayfs are present 0.345
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.401
# 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.327
When the network is plugged 0.085
And Tor is ready 23.010
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.418
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.187
Given I shutdown Tails and wait for the computer to power off 4.297
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.043
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.766
And the file system changes introduced in version 6.3~testoverlayfs are present 0.529
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.330
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.271
When the network is plugged 0.063
And Tor is ready 18.725
Then the Upgrader considers the system as up-to-date 10.871
# 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.395
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.983
After features/support/hooks.rb:326 0.701
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
41.403
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 10.230
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.611
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.157
And the signing key used by the Upgrader is outdated 0.919
But a current signing key is available on our website 0.000
When the network is plugged 0.571
And Tor is ready 20.821
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.091
After features/support/hooks.rb:326 1.352
After features/support/hooks.rb:100 0.000