Project Number Date
test_Tails_ISO_devel 3642 09 Jan 2025, 23:00

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:10.333 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:28.799
Before features/support/hooks.rb:269 0.002
Given a computer 0.192
And I create a 7200 MiB disk named "old" 0.067
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 40.223
When I start Tails from USB drive "old" with network unplugged 1:42.808
Then the boot device has safe access rights 3.074
And Tails is running from USB drive "old" 0.444
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.116
And udev-watchdog is monitoring the correct device 0.404
And I unplug USB drive "old" 0.347
After features/support/hooks.rb:326 3.908
After features/support/hooks.rb:100 0.007
Tags: @product
2:23.354
Before features/support/hooks.rb:269 0.002
Given a computer 0.219
And I start Tails from USB drive "old" with network unplugged and I login 1:34.018
Then Tails is running from USB drive "old" 0.434
And I create a persistent partition 37.319
And I take note of which tps features are available 2.016
Then a Tails persistence partition exists on USB drive "old" 0.895
And I shutdown Tails and wait for the computer to power off 8.449
After features/support/hooks.rb:326 0.176
After features/support/hooks.rb:100 0.010
Tags: @product
2:59.208
Before features/support/hooks.rb:269 0.007
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.422
Then Tails is running from USB drive "old" 0.707
And all tps features are active 2.476
When I write some files expected to persist 3.360
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.231
And all persistence configuration files have safe access rights 0.415
And all persistent directories from the old Tails version have safe access rights 2.676
And I take note of which tps features are available 0.499
And I shutdown Tails and wait for the computer to power off 4.235
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.969
After features/support/hooks.rb:326 0.111
After features/support/hooks.rb:100 0.007
Tags: @product
2:36.301
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 11.542
And I log in to a new session 21.891
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.812
And I plug USB drive "to_upgrade" 2.461
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.296
Then the running Tails is installed on USB drive "to_upgrade" 20.842
And I unplug USB drive "to_upgrade" 0.228
And I unplug USB drive "__internal" 0.224
After features/support/hooks.rb:326 2.944
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.075
Before features/support/hooks.rb:269 0.004
Given a computer 0.210
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.075
Then all tps features from the old Tails version are active 1.758
And Tails is running from USB drive "to_upgrade" 0.327
And the boot device has safe access rights 3.500
And the expected persistent files created with the old Tails version are present in the filesystem 1.737
And all persistent directories from the old Tails version have safe access rights 2.465
After features/support/hooks.rb:326 0.635
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
6:50.042
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.673
And no SquashFS delta is installed 0.117
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.421
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.356
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.663
When the network is plugged 0.081
And Tor is ready 25.837
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.415
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.215
Given I shutdown Tails and wait for the computer to power off 8.530
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.071
Then Tails is running version 6.2~testoverlayfs 0.043
And all tps features are active 2.611
And the file system changes introduced in version 6.2~testoverlayfs are present 0.340
And only the 6.2~testoverlayfs SquashFS delta is installed 0.088
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.350
# 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.306
When the network is plugged 0.086
And Tor is ready 19.696
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.614
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.575
Given I shutdown Tails and wait for the computer to power off 6.973
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.972
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.510
And the file system changes introduced in version 6.3~testoverlayfs are present 0.536
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.298
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.300
When the network is plugged 0.069
And Tor is ready 19.547
Then the Upgrader considers the system as up-to-date 0.342
# 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.051
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.177
After features/support/hooks.rb:326 0.762
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
37.551
Before features/support/hooks.rb:269 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.461
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.743
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.071
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 18.914
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.235
After features/support/hooks.rb:326 0.740
After features/support/hooks.rb:100 0.000