Project Number Date
test_Tails_ISO_devel 3533 06 Oct 2024, 12:38

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 18:38.729 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:56.995
Before features/support/hooks.rb:269 0.006
Given a computer 0.241
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 30.448
When I start Tails from USB drive "old" with network unplugged 1:21.186
Then the boot device has safe access rights 3.037
And Tails is running from USB drive "old" 0.323
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.300
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:326 3.476
After features/support/hooks.rb:100 0.010
Tags: @product
2:12.326
Before features/support/hooks.rb:269 0.006
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login 1:30.581
Then Tails is running from USB drive "old" 0.315
And I create a persistent partition 30.699
And I take note of which tps features are available 1.517
Then a Tails persistence partition exists on USB drive "old" 0.767
And I shutdown Tails and wait for the computer to power off 8.245
After features/support/hooks.rb:326 0.206
After features/support/hooks.rb:100 0.011
Tags: @product
2:48.297
Before features/support/hooks.rb:269 0.006
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:9.022
Then Tails is running from USB drive "old" 1.003
And all tps features are active 1.986
When I write some files expected to persist 1.747
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.221
And all persistence configuration files have safe access rights 0.450
And all persistent directories from the old Tails version have safe access rights 4.733
And I take note of which tps features are available 0.639
And I shutdown Tails and wait for the computer to power off 4.236
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.046
After features/support/hooks.rb:326 0.116
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.695
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.062
And I log in to a new session 21.891
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.557
And I plug USB drive "to_upgrade" 2.415
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.961
Then the running Tails is installed on USB drive "to_upgrade" 22.398
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:326 6.729
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.634
Before features/support/hooks.rb:269 0.006
Given a computer 0.224
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.024
Then all tps features from the old Tails version are active 2.248
And Tails is running from USB drive "to_upgrade" 0.362
And the boot device has safe access rights 3.298
And the expected persistent files created with the old Tails version are present in the filesystem 1.605
And all persistent directories from the old Tails version have safe access rights 2.870
After features/support/hooks.rb:326 0.722
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:14.545
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.638
And no SquashFS delta is installed 0.872
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.263
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.316
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.554
When the network is plugged 0.166
And Tor is ready 19.712
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.026
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.340
Given I shutdown Tails and wait for the computer to power off 8.776
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.096
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.113
And the file system changes introduced in version 6.2~testoverlayfs are present 0.322
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.308
# 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.263
When the network is plugged 0.079
And Tor is ready 19.017
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.992
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.701
Given I shutdown Tails and wait for the computer to power off 4.369
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.075
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 1.918
And the file system changes introduced in version 6.3~testoverlayfs are present 0.541
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.405
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.327
When the network is plugged 0.086
And Tor is ready 18.705
Then the Upgrader considers the system as up-to-date 0.308
# 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 13.828
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.132
After features/support/hooks.rb:326 0.868
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
36.234
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.671
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.495
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.911
But a current signing key is available on our website 0.000
When the network is plugged 0.111
And Tor is ready 18.384
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.601
After features/support/hooks.rb:326 0.690
After features/support/hooks.rb:100 0.000