Project Number Date
test_Tails_ISO_stable 5110 23 Sep 2024, 08: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 19:31.386 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:7.243
Before features/support/hooks.rb:269 0.005
Given a computer 0.210
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 31.651
When I start Tails from USB drive "old" with network unplugged 1:30.342
Then the boot device has safe access rights 2.903
And Tails is running from USB drive "old" 0.333
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.116
And udev-watchdog is monitoring the correct device 0.319
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:326 3.749
After features/support/hooks.rb:100 0.008
Tags: @product
2:6.831
Before features/support/hooks.rb:269 0.005
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login 1:26.647
Then Tails is running from USB drive "old" 0.385
And I create a persistent partition 30.706
And I take note of which tps features are available 1.849
Then a Tails persistence partition exists on USB drive "old" 0.847
And I shutdown Tails and wait for the computer to power off 6.190
After features/support/hooks.rb:326 0.175
After features/support/hooks.rb:100 0.008
Tags: @product
3:3.026
Before features/support/hooks.rb:269 0.005
Given a computer 0.234
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.889
Then Tails is running from USB drive "old" 0.356
And all tps features are active 2.138
When I write some files expected to persist 1.850
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.222
And all persistence configuration files have safe access rights 0.422
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.457
And I shutdown Tails and wait for the computer to power off 4.501
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.164
After features/support/hooks.rb:326 0.131
After features/support/hooks.rb:100 0.008
Tags: @product
2:37.432
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 11.678
And I log in to a new session 20.896
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.866
And I plug USB drive "to_upgrade" 2.436
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.463
Then the running Tails is installed on USB drive "to_upgrade" 23.639
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.249
After features/support/hooks.rb:326 5.644
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.036
Before features/support/hooks.rb:269 0.006
Given a computer 0.200
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.303
Then all tps features from the old Tails version are active 1.602
And Tails is running from USB drive "to_upgrade" 0.363
And the boot device has safe access rights 3.655
And the expected persistent files created with the old Tails version are present in the filesystem 1.420
And all persistent directories from the old Tails version have safe access rights 2.490
After features/support/hooks.rb:326 0.965
After features/support/hooks.rb:100 0.037
Tags: @product @automatic_upgrade
6:45.133
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 12.137
And no SquashFS delta is installed 0.157
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.509
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.340
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.529
When the network is plugged 0.081
And Tor is ready 20.745
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.298
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.301
Given I shutdown Tails and wait for the computer to power off 13.933
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.537
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.360
And the file system changes introduced in version 6.2~testoverlayfs are present 0.329
And only the 6.2~testoverlayfs SquashFS delta is installed 0.115
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.332
# 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.287
When the network is plugged 0.085
And Tor is ready 17.895
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.319
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.195
Given I shutdown Tails and wait for the computer to power off 4.331
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.160
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.005
And the file system changes introduced in version 6.3~testoverlayfs are present 0.482
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.278
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.299
When the network is plugged 0.097
And Tor is ready 21.454
Then the Upgrader considers the system as up-to-date 0.321
# 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.742
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.303
After features/support/hooks.rb:326 0.888
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
36.682
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 10.656
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.346
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 1.308
But a current signing key is available on our website 0.000
When the network is plugged 0.066
And Tor is ready 17.847
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.410
After features/support/hooks.rb:326 1.386
After features/support/hooks.rb:100 0.000