Project Number Date
test_Tails_ISO_devel 3479 14 Aug 2024, 12:55

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:52.455 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:17.802
Before features/support/hooks.rb:269 0.006
Given a computer 0.219
And I create a 7200 MiB disk named "old" 0.061
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 30.262
When I start Tails from USB drive "old" with network unplugged 1:41.977
Then the boot device has safe access rights 3.160
And Tails is running from USB drive "old" 0.338
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.333
And I unplug USB drive "old" 0.233
After features/support/hooks.rb:326 6.914
After features/support/hooks.rb:100 0.010
Tags: @product
2:26.211
Before features/support/hooks.rb:269 0.005
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login 1:34.915
Then Tails is running from USB drive "old" 0.414
And I create a persistent partition 36.737
And I take note of which tps features are available 3.866
Then a Tails persistence partition exists on USB drive "old" 1.709
And I shutdown Tails and wait for the computer to power off 8.368
After features/support/hooks.rb:326 0.200
After features/support/hooks.rb:100 0.010
Tags: @product
2:58.033
Before features/support/hooks.rb:269 0.004
Given a computer 0.235
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.858
Then Tails is running from USB drive "old" 0.348
And all tps features are active 2.109
When I write some files expected to persist 1.864
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.273
And all persistence configuration files have safe access rights 0.438
And all persistent directories from the old Tails version have safe access rights 2.313
And I take note of which tps features are available 0.445
And I shutdown Tails and wait for the computer to power off 4.342
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.802
After features/support/hooks.rb:326 0.100
After features/support/hooks.rb:100 0.010
Tags: @product
2:27.379
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 12.477
And I log in to a new session 18.215
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.318
And I plug USB drive "to_upgrade" 2.407
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.977
Then the running Tails is installed on USB drive "to_upgrade" 18.565
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:326 3.762
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.525
Before features/support/hooks.rb:269 0.006
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.262
Then all tps features from the old Tails version are active 1.584
And Tails is running from USB drive "to_upgrade" 0.306
And the boot device has safe access rights 3.164
And the expected persistent files created with the old Tails version are present in the filesystem 1.377
And all persistent directories from the old Tails version have safe access rights 2.642
After features/support/hooks.rb:326 0.620
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
6:51.900
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.960
And no SquashFS delta is installed 0.166
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.387
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.318
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.493
When the network is plugged 0.111
And Tor is ready 19.908
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.187
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.150
Given I shutdown Tails and wait for the computer to power off 10.991
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.922
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.584
And the file system changes introduced in version 6.2~testoverlayfs are present 0.345
And only the 6.2~testoverlayfs SquashFS delta is installed 0.120
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.388
# 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.329
When the network is plugged 0.094
And Tor is ready 20.803
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.387
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.609
Given I shutdown Tails and wait for the computer to power off 4.568
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.113
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.885
And the file system changes introduced in version 6.3~testoverlayfs are present 0.481
And only the 6.3~testoverlayfs SquashFS delta is installed 0.089
# 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.378
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.345
When the network is plugged 0.085
And Tor is ready 21.231
Then the Upgrader considers the system as up-to-date 0.355
# 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.874
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.121
After features/support/hooks.rb:326 0.778
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
36.602
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.236
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.480
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.106
And the signing key used by the Upgrader is outdated 1.171
But a current signing key is available on our website 0.000
When the network is plugged 0.095
And Tor is ready 17.819
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.692
After features/support/hooks.rb:326 1.379
After features/support/hooks.rb:100 0.000