Project Number Date
test_Tails_ISO_stable 5440 03 Feb 2025, 21:20

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:9.296 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:22.364
Before features/support/hooks.rb:269 0.004
Given a computer 0.198
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 31.923
When I start Tails from USB drive "old" with network unplugged 1:44.453
Then the boot device has safe access rights 3.566
And Tails is running from USB drive "old" 0.353
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.312
And I unplug USB drive "old" 0.296
After features/support/hooks.rb:326 3.558
After features/support/hooks.rb:100 0.012
Tags: @product
2:10.591
Before features/support/hooks.rb:269 0.008
Given a computer 0.349
And I start Tails from USB drive "old" with network unplugged and I login 1:26.992
Then Tails is running from USB drive "old" 0.313
And I create a persistent partition 32.427
And I take note of which tps features are available 1.456
Then a Tails persistence partition exists on USB drive "old" 0.825
And I shutdown Tails and wait for the computer to power off 8.226
After features/support/hooks.rb:326 0.202
After features/support/hooks.rb:100 0.009
Tags: @product
3:2.015
Before features/support/hooks.rb:269 0.005
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.791
Then Tails is running from USB drive "old" 1.029
And all tps features are active 2.095
When I write some files expected to persist 1.895
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.238
And all persistence configuration files have safe access rights 0.435
And all persistent directories from the old Tails version have safe access rights 3.178
And I take note of which tps features are available 0.441
And I shutdown Tails and wait for the computer to power off 4.525
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.203
After features/support/hooks.rb:326 0.127
After features/support/hooks.rb:100 0.008
Tags: @product
2:24.142
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.512
And I log in to a new session 16.611
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.951
And I plug USB drive "to_upgrade" 2.432
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.647
Then the running Tails is installed on USB drive "to_upgrade" 18.615
And I unplug USB drive "to_upgrade" 0.181
And I unplug USB drive "__internal" 0.190
After features/support/hooks.rb:326 6.889
After features/support/hooks.rb:100 0.000
Tags: @product
2:29.991
Before features/support/hooks.rb:269 0.004
Given a computer 0.165
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:19.380
Then all tps features from the old Tails version are active 2.350
And Tails is running from USB drive "to_upgrade" 0.414
And the boot device has safe access rights 3.367
And the expected persistent files created with the old Tails version are present in the filesystem 1.547
And all persistent directories from the old Tails version have safe access rights 2.765
After features/support/hooks.rb:326 0.992
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
7:4.363
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 28.796
And no SquashFS delta is installed 0.100
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.432
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.395
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.523
When the network is plugged 0.067
And Tor is ready 21.566
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.652
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.746
Given I shutdown Tails and wait for the computer to power off 11.168
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.839
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.180
And the file system changes introduced in version 6.2~testoverlayfs are present 0.398
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.314
# 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.350
When the network is plugged 0.068
And Tor is ready 19.370
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.270
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.936
Given I shutdown Tails and wait for the computer to power off 4.186
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.234
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.175
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.081
# 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.323
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.312
When the network is plugged 0.066
And Tor is ready 16.180
Then the Upgrader considers the system as up-to-date 10.853
# 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 15.225
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.899
After features/support/hooks.rb:326 0.753
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
35.826
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 9.286
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.312
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.108
But a current signing key is available on our website 0.000
When the network is plugged 0.105
And Tor is ready 20.996
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.952
After features/support/hooks.rb:326 1.049
After features/support/hooks.rb:100 0.000