Project Number Date
test_Tails_ISO_devel 3617 20 Dec 2024, 12:36

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:55.025 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:9.749
Before features/support/hooks.rb:269 0.005
Given a computer 0.195
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 29.381
When I start Tails from USB drive "old" with network unplugged 1:35.007
Then the boot device has safe access rights 3.098
And Tails is running from USB drive "old" 0.302
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.111
And udev-watchdog is monitoring the correct device 0.301
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:326 7.010
After features/support/hooks.rb:100 0.008
Tags: @product
2:6.310
Before features/support/hooks.rb:269 0.004
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 1:20.956
Then Tails is running from USB drive "old" 0.390
And I create a persistent partition 34.014
And I take note of which tps features are available 1.750
Then a Tails persistence partition exists on USB drive "old" 0.786
And I shutdown Tails and wait for the computer to power off 8.218
After features/support/hooks.rb:326 0.142
After features/support/hooks.rb:100 0.009
Tags: @product
2:52.593
Before features/support/hooks.rb:269 0.004
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.121
Then Tails is running from USB drive "old" 0.322
And all tps features are active 1.971
When I write some files expected to persist 1.905
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.215
And all persistence configuration files have safe access rights 0.420
And all persistent directories from the old Tails version have safe access rights 2.340
And I take note of which tps features are available 0.420
And I shutdown Tails and wait for the computer to power off 4.410
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.251
After features/support/hooks.rb:326 0.131
After features/support/hooks.rb:100 0.009
Tags: @product
2:37.637
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 11.381
And I log in to a new session 22.480
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.587
And I plug USB drive "to_upgrade" 2.349
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.890
Then the running Tails is installed on USB drive "to_upgrade" 20.533
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:326 6.716
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.296
Before features/support/hooks.rb:269 0.005
Given a computer 0.179
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.894
Then all tps features from the old Tails version are active 1.620
And Tails is running from USB drive "to_upgrade" 0.311
And the boot device has safe access rights 3.608
And the expected persistent files created with the old Tails version are present in the filesystem 1.324
And all persistent directories from the old Tails version have safe access rights 2.357
After features/support/hooks.rb:326 0.634
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:15.180
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 11.298
And no SquashFS delta is installed 0.277
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.491
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.258
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.445
When the network is plugged 0.063
And Tor is ready 22.211
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.482
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.261
Given I shutdown Tails and wait for the computer to power off 8.403
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.630
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.337
And the file system changes introduced in version 6.2~testoverlayfs are present 0.305
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.279
# 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.295
When the network is plugged 0.073
And Tor is ready 16.368
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.767
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.898
Given I shutdown Tails and wait for the computer to power off 4.289
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.206
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.015
And the file system changes introduced in version 6.3~testoverlayfs are present 0.478
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.277
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.386
When the network is plugged 0.073
And Tor is ready 18.434
Then the Upgrader considers the system as up-to-date 0.326
# 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.312
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.017
After features/support/hooks.rb:326 0.819
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
37.257
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.157
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.887
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.692
But a current signing key is available on our website 0.000
When the network is plugged 0.080
And Tor is ready 18.819
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.557
After features/support/hooks.rb:326 0.710
After features/support/hooks.rb:100 0.000