Project Number Date
test_Tails_ISO_stable 4913 26 Jun 2024, 12:40

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 18:31.034 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:2.934
Before features/support/hooks.rb:269 0.004
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 29.874
When I start Tails from USB drive "old" with network unplugged 1:27.944
Then the boot device has safe access rights 2.839
And Tails is running from USB drive "old" 0.327
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.305
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:326 3.549
After features/support/hooks.rb:100 0.010
Tags: @product
1:58.852
Before features/support/hooks.rb:269 0.006
Given a computer 0.220
And I start Tails from USB drive "old" with network unplugged and I login 1:19.486
Then Tails is running from USB drive "old" 0.280
And I create a persistent partition 30.489
And I take note of which tps features are available 1.425
Then a Tails persistence partition exists on USB drive "old" 0.749
And I shutdown Tails and wait for the computer to power off 6.201
After features/support/hooks.rb:326 0.178
After features/support/hooks.rb:100 0.008
Tags: @product
2:44.384
Before features/support/hooks.rb:269 0.004
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:8.158
Then Tails is running from USB drive "old" 0.368
And all tps features are active 1.871
When I write some files expected to persist 1.688
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.209
And all persistence configuration files have safe access rights 0.388
And all persistent directories from the old Tails version have safe access rights 2.433
And I take note of which tps features are available 0.440
And I shutdown Tails and wait for the computer to power off 4.598
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.019
After features/support/hooks.rb:326 0.147
After features/support/hooks.rb:100 0.009
Tags: @product
2:22.399
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 10.279
And I log in to a new session 17.068
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.334
And I plug USB drive "to_upgrade" 2.377
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.969
Then the running Tails is installed on USB drive "to_upgrade" 14.917
And I unplug USB drive "to_upgrade" 0.245
And I unplug USB drive "__internal" 0.206
After features/support/hooks.rb:326 6.620
After features/support/hooks.rb:100 0.000
Tags: @product
2:2.924
Before features/support/hooks.rb:269 0.006
Given a computer 0.279
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:53.252
Then all tps features from the old Tails version are active 1.664
And Tails is running from USB drive "to_upgrade" 0.320
And the boot device has safe access rights 3.133
And the expected persistent files created with the old Tails version are present in the filesystem 1.830
And all persistent directories from the old Tails version have safe access rights 2.443
After features/support/hooks.rb:326 0.664
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:42.980
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.233
And no SquashFS delta is installed 0.279
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.249
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.282
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.426
When the network is plugged 0.084
And Tor is ready 49.050
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.590
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.626
Given I shutdown Tails and wait for the computer to power off 10.737
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.022
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.053
And the file system changes introduced in version 6.2~testoverlayfs are present 0.278
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.324
# 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.282
When the network is plugged 0.054
And Tor is ready 18.841
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.120
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.670
Given I shutdown Tails and wait for the computer to power off 4.404
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.977
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 1.986
And the file system changes introduced in version 6.3~testoverlayfs are present 0.488
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.317
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.295
When the network is plugged 0.040
And Tor is ready 17.739
Then the Upgrader considers the system as up-to-date 0.292
# 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.114
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.874
After features/support/hooks.rb:326 0.720
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
36.557
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.133
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.406
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.731
But a current signing key is available on our website 0.000
When the network is plugged 0.061
And Tor is ready 20.111
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.059
After features/support/hooks.rb:326 0.678
After features/support/hooks.rb:100 0.000