Project Number Date
test_Tails_ISO_devel 3420 07 Jun 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:24.577 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:2.560
Before features/support/hooks.rb:269 0.007
Given a computer 0.209
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 29.674
When I start Tails from USB drive "old" with network unplugged 1:27.829
Then the boot device has safe access rights 2.804
And Tails is running from USB drive "old" 0.296
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.086
And udev-watchdog is monitoring the correct device 0.322
And I unplug USB drive "old" 0.169
After features/support/hooks.rb:315 3.519
After features/support/hooks.rb:100 0.010
Tags: @product
2:15.380
Before features/support/hooks.rb:269 0.008
Given a computer 0.316
And I start Tails from USB drive "old" with network unplugged and I login 1:29.528
Then Tails is running from USB drive "old" 0.313
And I create a persistent partition 34.697
And I take note of which tps features are available 1.277
Then a Tails persistence partition exists on USB drive "old" 0.850
And I shutdown Tails and wait for the computer to power off 8.397
After features/support/hooks.rb:315 0.171
After features/support/hooks.rb:100 0.010
Tags: @product
2:45.139
Before features/support/hooks.rb:269 0.007
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:9.132
Then Tails is running from USB drive "old" 0.364
And all tps features are active 2.039
When I write some files expected to persist 1.650
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.211
And all persistence configuration files have safe access rights 0.342
And all persistent directories from the old Tails version have safe access rights 2.648
And I take note of which tps features are available 0.366
And I shutdown Tails and wait for the computer to power off 4.314
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.855
After features/support/hooks.rb:315 0.118
After features/support/hooks.rb:100 0.010
Tags: @product
2:25.810
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.779
And I log in to a new session 19.031
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.560
And I plug USB drive "to_upgrade" 2.404
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.139
Then the running Tails is installed on USB drive "to_upgrade" 16.488
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:315 3.603
After features/support/hooks.rb:100 0.000
Tags: @product
2:3.968
Before features/support/hooks.rb:269 0.007
Given a computer 0.196
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:55.323
Then all tps features from the old Tails version are active 1.457
And Tails is running from USB drive "to_upgrade" 0.307
And the boot device has safe access rights 2.935
And the expected persistent files created with the old Tails version are present in the filesystem 1.498
And all persistent directories from the old Tails version have safe access rights 2.250
After features/support/hooks.rb:315 0.700
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:17.635
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.061
And no SquashFS delta is installed 0.144
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.313
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.259
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.441
When the network is plugged 0.048
And Tor is ready 18.072
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.835
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.131
Given I shutdown Tails and wait for the computer to power off 8.687
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.687
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.079
And the file system changes introduced in version 6.2~testoverlayfs are present 0.324
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.322
# 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.331
When the network is plugged 0.042
And Tor is ready 19.988
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.370
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.970
Given I shutdown Tails and wait for the computer to power off 4.275
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.634
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.014
And the file system changes introduced in version 6.3~testoverlayfs are present 0.450
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.335
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.287
When the network is plugged 0.042
And Tor is ready 15.881
Then the Upgrader considers the system as up-to-date 0.341
# 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 16.059
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.953
After features/support/hooks.rb:315 0.732
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
34.080
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 9.973
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.407
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 1.597
But a current signing key is available on our website 0.000
When the network is plugged 0.046
And Tor is ready 16.884
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.112
After features/support/hooks.rb:315 0.640
After features/support/hooks.rb:100 0.000