Project Number Date
test_Tails_ISO_stable 5055 29 Aug 2024, 08:52

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:24.727 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:15.416
Before features/support/hooks.rb:269 0.007
Given a computer 0.225
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 33.545
When I start Tails from USB drive "old" with network unplugged 1:35.973
Then the boot device has safe access rights 3.537
And Tails is running from USB drive "old" 0.346
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.330
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:326 3.723
After features/support/hooks.rb:100 0.014
Tags: @product
2:14.341
Before features/support/hooks.rb:269 0.007
Given a computer 0.241
And I start Tails from USB drive "old" with network unplugged and I login 1:27.118
Then Tails is running from USB drive "old" 0.366
And I create a persistent partition 35.151
And I take note of which tps features are available 2.055
Then a Tails persistence partition exists on USB drive "old" 0.898
And I shutdown Tails and wait for the computer to power off 8.509
After features/support/hooks.rb:326 0.209
After features/support/hooks.rb:100 0.009
Tags: @product
3:7.102
Before features/support/hooks.rb:269 0.004
Given a computer 0.252
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:28.027
Then Tails is running from USB drive "old" 0.334
And all tps features are active 2.200
When I write some files expected to persist 2.024
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.264
And all persistence configuration files have safe access rights 0.445
And all persistent directories from the old Tails version have safe access rights 2.587
And I take note of which tps features are available 0.534
And I shutdown Tails and wait for the computer to power off 4.445
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.985
After features/support/hooks.rb:326 0.111
After features/support/hooks.rb:100 0.009
Tags: @product
2:43.982
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.395
And I log in to a new session 24.939
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.778
And I plug USB drive "to_upgrade" 3.760
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.315
Then the running Tails is installed on USB drive "to_upgrade" 23.381
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:326 2.901
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.705
Before features/support/hooks.rb:269 0.005
Given a computer 0.195
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.059
Then all tps features from the old Tails version are active 1.828
And Tails is running from USB drive "to_upgrade" 0.308
And the boot device has safe access rights 3.380
And the expected persistent files created with the old Tails version are present in the filesystem 1.546
And all persistent directories from the old Tails version have safe access rights 2.387
After features/support/hooks.rb:326 0.619
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
7:4.947
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 26.509
And no SquashFS delta is installed 0.317
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.643
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.261
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.450
When the network is plugged 0.277
And Tor is ready 22.920
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.709
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.063
Given I shutdown Tails and wait for the computer to power off 14.422
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.265
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.504
And the file system changes introduced in version 6.2~testoverlayfs are present 0.327
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.414
# 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.322
When the network is plugged 0.081
And Tor is ready 19.678
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.388
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.569
Given I shutdown Tails and wait for the computer to power off 4.484
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.880
Then Tails is running version 6.3~testoverlayfs 0.025
And all tps features are active 2.393
And the file system changes introduced in version 6.3~testoverlayfs are present 0.503
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.349
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.274
When the network is plugged 0.077
And Tor is ready 18.330
Then the Upgrader considers the system as up-to-date 0.347
# 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.704
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.209
After features/support/hooks.rb:326 0.859
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
38.231
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 11.045
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.587
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.104
And the signing key used by the Upgrader is outdated 0.807
But a current signing key is available on our website 0.000
When the network is plugged 0.082
And Tor is ready 20.178
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.424
After features/support/hooks.rb:326 0.665
After features/support/hooks.rb:100 0.000