Project Number Date
test_Tails_ISO_stable 5184 15 Oct 2024, 12: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 20:15.795 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:12.222
Before features/support/hooks.rb:269 0.004
Given a computer 0.194
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 29.194
When I start Tails from USB drive "old" with network unplugged 1:37.605
Then the boot device has safe access rights 3.092
And Tails is running from USB drive "old" 0.372
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.314
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:326 3.499
After features/support/hooks.rb:100 0.010
Tags: @product
2:6.003
Before features/support/hooks.rb:269 0.006
Given a computer 0.227
And I start Tails from USB drive "old" with network unplugged and I login 1:21.176
Then Tails is running from USB drive "old" 0.350
And I create a persistent partition 33.124
And I take note of which tps features are available 1.625
Then a Tails persistence partition exists on USB drive "old" 0.923
And I shutdown Tails and wait for the computer to power off 8.574
After features/support/hooks.rb:326 0.229
After features/support/hooks.rb:100 0.009
Tags: @product
2:51.547
Before features/support/hooks.rb:269 0.006
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.762
Then Tails is running from USB drive "old" 0.609
And all tps features are active 2.222
When I write some files expected to persist 1.702
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.227
And all persistence configuration files have safe access rights 0.414
And all persistent directories from the old Tails version have safe access rights 2.790
And I take note of which tps features are available 0.548
And I shutdown Tails and wait for the computer to power off 4.304
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.753
After features/support/hooks.rb:326 0.125
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.438
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.923
And I log in to a new session 19.369
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.851
And I plug USB drive "to_upgrade" 2.376
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.793
Then the running Tails is installed on USB drive "to_upgrade" 23.618
And I unplug USB drive "to_upgrade" 0.275
And I unplug USB drive "__internal" 0.228
After features/support/hooks.rb:326 7.156
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.128
Before features/support/hooks.rb:269 0.005
Given a computer 0.209
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.858
Then all tps features from the old Tails version are active 1.704
And Tails is running from USB drive "to_upgrade" 0.339
And the boot device has safe access rights 3.263
And the expected persistent files created with the old Tails version are present in the filesystem 2.092
And all persistent directories from the old Tails version have safe access rights 2.661
After features/support/hooks.rb:326 1.002
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:44.260
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.889
And no SquashFS delta is installed 0.454
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.336
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.182
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.314
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.495
When the network is plugged 0.080
And Tor is ready 22.443
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.186
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.884
Given I shutdown Tails and wait for the computer to power off 1:32.770
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.960
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.326
And the file system changes introduced in version 6.2~testoverlayfs are present 0.308
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.308
# 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.310
When the network is plugged 0.107
And Tor is ready 21.429
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.640
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.213
Given I shutdown Tails and wait for the computer to power off 4.317
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.808
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.179
And the file system changes introduced in version 6.3~testoverlayfs are present 0.576
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.296
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.314
When the network is plugged 0.086
And Tor is ready 18.572
Then the Upgrader considers the system as up-to-date 0.315
# 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.948
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.026
After features/support/hooks.rb:326 0.766
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
34.195
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.167
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.300
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 0.768
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 16.590
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.230
After features/support/hooks.rb:326 1.618
After features/support/hooks.rb:100 0.000