Project Number Date
test_Tails_ISO_stable 5245 03 Nov 2024, 12:38

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:48.215 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:26.178
Before features/support/hooks.rb:269 0.006
Given a computer 0.214
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 33.306
When I start Tails from USB drive "old" with network unplugged 1:47.080
Then the boot device has safe access rights 3.360
And Tails is running from USB drive "old" 0.362
And there is no persistence partition on USB drive "old" 0.088
And process "udev-watchdog" is running 0.120
And udev-watchdog is monitoring the correct device 0.361
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:326 3.863
After features/support/hooks.rb:100 0.021
Tags: @product
2:9.564
Before features/support/hooks.rb:269 0.006
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login 1:25.319
Then Tails is running from USB drive "old" 0.372
And I create a persistent partition 32.083
And I take note of which tps features are available 1.878
Then a Tails persistence partition exists on USB drive "old" 0.877
And I shutdown Tails and wait for the computer to power off 8.825
After features/support/hooks.rb:326 0.207
After features/support/hooks.rb:100 0.010
Tags: @product
3:2.803
Before features/support/hooks.rb:269 0.007
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.409
Then Tails is running from USB drive "old" 1.652
And all tps features are active 2.198
When I write some files expected to persist 2.299
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.487
And all persistence configuration files have safe access rights 0.480
And all persistent directories from the old Tails version have safe access rights 2.614
And I take note of which tps features are available 0.480
And I shutdown Tails and wait for the computer to power off 4.537
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.440
After features/support/hooks.rb:326 0.147
After features/support/hooks.rb:100 0.011
Tags: @product
2:38.388
Before features/support/hooks.rb:269 0.010
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.376
And I log in to a new session 23.488
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.867
And I plug USB drive "to_upgrade" 2.411
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.384
Then the running Tails is installed on USB drive "to_upgrade" 22.406
And I unplug USB drive "to_upgrade" 0.230
And I unplug USB drive "__internal" 0.223
After features/support/hooks.rb:326 2.227
After features/support/hooks.rb:100 0.000
Tags: @product
2:31.530
Before features/support/hooks.rb:269 0.007
Given a computer 0.221
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:22.020
Then all tps features from the old Tails version are active 1.787
And Tails is running from USB drive "to_upgrade" 0.363
And the boot device has safe access rights 3.296
And the expected persistent files created with the old Tails version are present in the filesystem 1.331
And all persistent directories from the old Tails version have safe access rights 2.509
After features/support/hooks.rb:326 0.682
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
8:0.486
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 11.833
And no SquashFS delta is installed 0.174
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.478
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.264
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.414
When the network is plugged 0.102
And Tor is ready 19.400
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.544
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.076
Given I shutdown Tails and wait for the computer to power off 1:20.522
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.659
Then Tails is running version 6.2~testoverlayfs 0.039
And all tps features are active 3.814
And the file system changes introduced in version 6.2~testoverlayfs are present 0.392
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.372
# 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.366
When the network is plugged 0.077
And Tor is ready 22.317
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.867
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.251
Given I shutdown Tails and wait for the computer to power off 4.678
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.453
Then Tails is running version 6.3~testoverlayfs 0.024
And all tps features are active 2.496
And the file system changes introduced in version 6.3~testoverlayfs are present 0.682
And only the 6.3~testoverlayfs SquashFS delta is installed 0.084
# 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.414
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.302
When the network is plugged 0.099
And Tor is ready 15.367
Then the Upgrader considers the system as up-to-date 10.935
# 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.987
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.838
After features/support/hooks.rb:326 0.736
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
59.264
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.098
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.481
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 0.925
But a current signing key is available on our website 0.000
When the network is plugged 0.127
And Tor is ready 45.913
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.647
After features/support/hooks.rb:326 0.764
After features/support/hooks.rb:100 0.000