Project Number Date
test_Tails_ISO_stable 5180 13 Oct 2024, 13:15

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:58.039 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:9.395
Before features/support/hooks.rb:269 0.005
Given a computer 0.202
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 31.912
When I start Tails from USB drive "old" with network unplugged 1:31.817
Then the boot device has safe access rights 3.300
And Tails is running from USB drive "old" 0.384
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.331
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:326 3.750
After features/support/hooks.rb:100 0.017
Tags: @product
2:12.682
Before features/support/hooks.rb:269 0.007
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login 1:27.675
Then Tails is running from USB drive "old" 0.372
And I create a persistent partition 33.079
And I take note of which tps features are available 1.789
Then a Tails persistence partition exists on USB drive "old" 0.893
And I shutdown Tails and wait for the computer to power off 8.665
After features/support/hooks.rb:326 0.176
After features/support/hooks.rb:100 0.007
Tags: @product
3:2.155
Before features/support/hooks.rb:269 0.006
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.693
Then Tails is running from USB drive "old" 0.403
And all tps features are active 2.113
When I write some files expected to persist 1.937
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.233
And all persistence configuration files have safe access rights 0.407
And all persistent directories from the old Tails version have safe access rights 2.712
And I take note of which tps features are available 0.585
And I shutdown Tails and wait for the computer to power off 4.783
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.084
After features/support/hooks.rb:326 0.112
After features/support/hooks.rb:100 0.011
Tags: @product
2:41.650
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 11.397
And I log in to a new session 27.790
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.036
And I plug USB drive "to_upgrade" 2.486
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.288
Then the running Tails is installed on USB drive "to_upgrade" 20.984
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.465
After features/support/hooks.rb:326 7.251
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.531
Before features/support/hooks.rb:269 0.005
Given a computer 0.210
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.364
Then all tps features from the old Tails version are active 1.783
And Tails is running from USB drive "to_upgrade" 0.388
And the boot device has safe access rights 3.729
And the expected persistent files created with the old Tails version are present in the filesystem 1.445
And all persistent directories from the old Tails version have safe access rights 2.611
After features/support/hooks.rb:326 1.057
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
8:46.962
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 14.558
And no SquashFS delta is installed 0.841
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.366
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.337
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.650
When the network is plugged 0.077
And Tor is ready 51.036
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.614
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.803
Given I shutdown Tails and wait for the computer to power off 1:38.183
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.332
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.901
And the file system changes introduced in version 6.2~testoverlayfs are present 0.353
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.325
# 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.298
When the network is plugged 0.102
And Tor is ready 22.301
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.808
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.480
Given I shutdown Tails and wait for the computer to power off 6.806
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.462
Then Tails is running version 6.3~testoverlayfs 0.023
And all tps features are active 4.305
And the file system changes introduced in version 6.3~testoverlayfs are present 0.565
And only the 6.3~testoverlayfs SquashFS delta is installed 0.086
# 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.466
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.541
When the network is plugged 0.293
And Tor is ready 19.294
Then the Upgrader considers the system as up-to-date 0.357
# 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.028
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.193
After features/support/hooks.rb:326 0.836
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
40.661
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.913
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.939
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 1.128
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 18.219
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.327
After features/support/hooks.rb:326 1.163
After features/support/hooks.rb:100 0.000