Project Number Date
test_Tails_ISO_devel 3532 05 Oct 2024, 12:26

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:40.400 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.579
Before features/support/hooks.rb:269 0.006
Given a computer 0.198
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 31.063
When I start Tails from USB drive "old" with network unplugged 1:20.421
Then the boot device has safe access rights 2.831
And Tails is running from USB drive "old" 0.332
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.275
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:326 7.058
After features/support/hooks.rb:100 0.009
Tags: @product
1:58.592
Before features/support/hooks.rb:269 0.006
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 1:18.935
Then Tails is running from USB drive "old" 0.291
And I create a persistent partition 30.954
And I take note of which tps features are available 1.283
Then a Tails persistence partition exists on USB drive "old" 0.763
And I shutdown Tails and wait for the computer to power off 6.172
After features/support/hooks.rb:326 0.189
After features/support/hooks.rb:100 0.020
Tags: @product
2:57.988
Before features/support/hooks.rb:269 0.006
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.513
Then Tails is running from USB drive "old" 0.403
And all tps features are active 2.054
When I write some files expected to persist 1.689
# 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.545
And all persistent directories from the old Tails version have safe access rights 2.482
And I take note of which tps features are available 0.475
And I shutdown Tails and wait for the computer to power off 4.287
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.132
After features/support/hooks.rb:326 0.141
After features/support/hooks.rb:100 0.009
Tags: @product
2:26.549
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.826
And I log in to a new session 17.744
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.439
And I plug USB drive "to_upgrade" 2.458
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.541
Then the running Tails is installed on USB drive "to_upgrade" 17.130
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.200
After features/support/hooks.rb:326 2.524
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.309
Before features/support/hooks.rb:269 0.006
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.454
Then all tps features from the old Tails version are active 1.639
And Tails is running from USB drive "to_upgrade" 0.337
And the boot device has safe access rights 2.948
And the expected persistent files created with the old Tails version are present in the filesystem 1.473
And all persistent directories from the old Tails version have safe access rights 2.267
After features/support/hooks.rb:326 0.607
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:34.338
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 11.785
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.239
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.271
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.412
When the network is plugged 0.067
And Tor is ready 49.123
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.571
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.362
Given I shutdown Tails and wait for the computer to power off 8.359
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.816
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.064
And the file system changes introduced in version 6.2~testoverlayfs are present 0.289
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.321
# 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.266
When the network is plugged 0.073
And Tor is ready 19.120
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.977
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.059
Given I shutdown Tails and wait for the computer to power off 4.290
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.404
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.976
And the file system changes introduced in version 6.3~testoverlayfs are present 0.453
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.316
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.257
When the network is plugged 0.076
And Tor is ready 19.581
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 14.066
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.080
After features/support/hooks.rb:326 0.775
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
37.041
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.558
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.462
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.707
But a current signing key is available on our website 0.000
When the network is plugged 0.085
And Tor is ready 18.814
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.353
After features/support/hooks.rb:326 0.605
After features/support/hooks.rb:100 0.000