Project Number Date
test_Tails_ISO_devel 3495 28 Aug 2024, 12:37

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:8.814 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:0.096
Before features/support/hooks.rb:269 0.007
Given a computer 0.215
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 30.530
When I start Tails from USB drive "old" with network unplugged 1:24.264
Then the boot device has safe access rights 2.938
And Tails is running from USB drive "old" 0.326
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.347
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:326 0.775
After features/support/hooks.rb:100 0.009
Tags: @product
2:0.889
Before features/support/hooks.rb:269 0.006
Given a computer 0.230
And I start Tails from USB drive "old" with network unplugged and I login 1:19.412
Then Tails is running from USB drive "old" 0.300
And I create a persistent partition 30.600
And I take note of which tps features are available 1.346
Then a Tails persistence partition exists on USB drive "old" 0.797
And I shutdown Tails and wait for the computer to power off 8.200
After features/support/hooks.rb:326 0.183
After features/support/hooks.rb:100 0.010
Tags: @product
2:49.217
Before features/support/hooks.rb:269 0.006
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.039
Then Tails is running from USB drive "old" 0.314
And all tps features are active 2.158
When I write some files expected to persist 1.636
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.217
And all persistence configuration files have safe access rights 0.515
And all persistent directories from the old Tails version have safe access rights 2.273
And I take note of which tps features are available 0.463
And I shutdown Tails and wait for the computer to power off 4.281
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.112
After features/support/hooks.rb:326 0.101
After features/support/hooks.rb:100 0.010
Tags: @product
2:23.023
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.728
And I log in to a new session 17.460
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.509
And I plug USB drive "to_upgrade" 2.390
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.007
Then the running Tails is installed on USB drive "to_upgrade" 17.514
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.200
After features/support/hooks.rb:326 2.425
After features/support/hooks.rb:100 0.000
Tags: @product
2:7.895
Before features/support/hooks.rb:269 0.008
Given a computer 0.204
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.110
Then all tps features from the old Tails version are active 1.517
And Tails is running from USB drive "to_upgrade" 0.285
And the boot device has safe access rights 3.050
And the expected persistent files created with the old Tails version are present in the filesystem 1.402
And all persistent directories from the old Tails version have safe access rights 2.323
After features/support/hooks.rb:326 0.643
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:12.104
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.583
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.358
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.091
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.276
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.438
When the network is plugged 0.069
And Tor is ready 19.955
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.309
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.567
Given I shutdown Tails and wait for the computer to power off 8.554
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.212
Then Tails is running version 6.2~testoverlayfs 0.039
And all tps features are active 2.132
And the file system changes introduced in version 6.2~testoverlayfs are present 0.279
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.315
# 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.252
When the network is plugged 0.074
And Tor is ready 18.235
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.065
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.594
Given I shutdown Tails and wait for the computer to power off 4.299
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.134
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.264
And the file system changes introduced in version 6.3~testoverlayfs are present 0.480
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.366
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.256
When the network is plugged 0.068
And Tor is ready 15.660
Then the Upgrader considers the system as up-to-date 0.312
# 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.696
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.918
After features/support/hooks.rb:326 0.740
After features/support/hooks.rb:100 0.032
Tags: @product @automatic_upgrade
35.587
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.162
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.335
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.964
But a current signing key is available on our website 0.000
When the network is plugged 0.062
And Tor is ready 17.582
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.427
After features/support/hooks.rb:326 0.759
After features/support/hooks.rb:100 0.000