Project Number Date
test_Tails_ISO_stable 4749 27 Mar 2024, 10:45

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 25:15.630 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
1:23.015
Before features/support/hooks.rb:245 0.021
Given a computer 1.034
And I create a 7200 MiB disk named "old" 0.132
And I plug USB drive "old" 1.108
And I write an old version of the Tails USB image to disk "old" 20.886
When I start Tails from USB drive "old" with network unplugged 56.182
Then the boot device has safe access rights 2.742
And Tails is running from USB drive "old" 0.300
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.289
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:291 3.517
After features/support/hooks.rb:75 0.006
Tags: @product
2:0.072
Before features/support/hooks.rb:245 0.002
Given a computer 0.121
And I start Tails from USB drive "old" with network unplugged and I login 1:19.137
Then Tails is running from USB drive "old" 0.328
And I create a persistent partition 32.413
And I take note of which tps features are available 1.221
Then a Tails persistence partition exists on USB drive "old" 0.707
And I shutdown Tails and wait for the computer to power off 6.142
After features/support/hooks.rb:291 0.159
After features/support/hooks.rb:75 0.005
Tags: @product
2:22.219
Before features/support/hooks.rb:245 0.002
Given a computer 0.136
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:54.818
Then Tails is running from USB drive "old" 0.414
And all tps features are active 1.815
When I write some files expected to persist 1.499
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.190
And all persistence configuration files have safe access rights 0.396
And all persistent directories from the old Tails version have safe access rights 2.555
And I take note of which tps features are available 0.337
And I shutdown Tails and wait for the computer to power off 4.289
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.764
After features/support/hooks.rb:291 0.109
After features/support/hooks.rb:75 0.005
Tags: @product
3:34.104
Before features/support/hooks.rb:245 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 1:28.824
And I log in to a new session 13.570
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.334
And I plug USB drive "to_upgrade" 2.405
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.190
Then the running Tails is installed on USB drive "to_upgrade" 13.378
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.197
After features/support/hooks.rb:291 3.535
After features/support/hooks.rb:75 0.006
Tags: @product
1:55.650
Before features/support/hooks.rb:245 0.002
Given a computer 0.251
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:46.243
Then all tps features from the old Tails version are active 1.458
And Tails is running from USB drive "to_upgrade" 0.349
And the boot device has safe access rights 3.376
And the expected persistent files created with the old Tails version are present in the filesystem 1.538
And all persistent directories from the old Tails version have safe access rights 2.432
After features/support/hooks.rb:291 0.796
After features/support/hooks.rb:75 0.006
Tags: @product @automatic_upgrade
13:27.468
Before features/support/hooks.rb:245 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7:34.980
And no SquashFS delta is installed 0.098
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.289
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.256
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.438
When the network is plugged 0.163
And Tor is ready 18.599
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.228
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.650
Given I shutdown Tails and wait for the computer to power off 4.203
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.866
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 1.757
And the file system changes introduced in version 6.2~testoverlayfs are present 0.295
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.292
# 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.264
When the network is plugged 0.044
And Tor is ready 17.848
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.035
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.498
Given I shutdown Tails and wait for the computer to power off 4.228
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.103
Then Tails is running version 6.3~testoverlayfs 0.023
And all tps features are active 2.143
And the file system changes introduced in version 6.3~testoverlayfs are present 0.490
And only the 6.3~testoverlayfs SquashFS delta is installed 0.091
# 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.353
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.302
When the network is plugged 0.043
And Tor is ready 13.778
Then the Upgrader considers the system as up-to-date 10.610
# 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.338
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.016
After features/support/hooks.rb:291 0.803
After features/support/hooks.rb:75 0.024
Tags: @product @automatic_upgrade
33.099
Before features/support/hooks.rb:245 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.777
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.327
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.529
But a current signing key is available on our website 0.000
When the network is plugged 0.058
And Tor is ready 16.374
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.968
After features/support/hooks.rb:291 1.113
After features/support/hooks.rb:75 0.000