Project Number Date
test_Tails_ISO_devel 3527 02 Oct 2024, 12:17

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:51.009 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:12.497
Before features/support/hooks.rb:269 0.004
Given a computer 0.200
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 30.755
When I start Tails from USB drive "old" with network unplugged 1:35.522
Then the boot device has safe access rights 3.870
And Tails is running from USB drive "old" 0.299
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.112
And udev-watchdog is monitoring the correct device 0.381
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:326 3.493
After features/support/hooks.rb:100 0.033
Tags: @product
2:2.240
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:19.222
Then Tails is running from USB drive "old" 0.341
And I create a persistent partition 32.155
And I take note of which tps features are available 1.462
Then a Tails persistence partition exists on USB drive "old" 0.760
And I shutdown Tails and wait for the computer to power off 8.097
After features/support/hooks.rb:326 0.122
After features/support/hooks.rb:100 0.009
Tags: @product
2:56.351
Before features/support/hooks.rb:269 0.004
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.128
Then Tails is running from USB drive "old" 0.371
And all tps features are active 2.221
When I write some files expected to persist 1.553
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
And all persistence configuration files have safe access rights 0.398
And all persistent directories from the old Tails version have safe access rights 2.318
And I take note of which tps features are available 0.466
And I shutdown Tails and wait for the computer to power off 4.257
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.239
After features/support/hooks.rb:326 0.105
After features/support/hooks.rb:100 0.008
Tags: @product
2:29.767
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.514
And I log in to a new session 19.494
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.666
And I plug USB drive "to_upgrade" 2.359
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.643
Then the running Tails is installed on USB drive "to_upgrade" 17.672
And I unplug USB drive "to_upgrade" 0.218
And I unplug USB drive "__internal" 0.197
After features/support/hooks.rb:326 6.754
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.596
Before features/support/hooks.rb:269 0.006
Given a computer 0.195
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.337
Then all tps features from the old Tails version are active 1.651
And Tails is running from USB drive "to_upgrade" 0.315
And the boot device has safe access rights 3.120
And the expected persistent files created with the old Tails version are present in the filesystem 1.570
And all persistent directories from the old Tails version have safe access rights 2.404
After features/support/hooks.rb:326 0.862
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:21.493
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.859
And no SquashFS delta is installed 0.350
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.436
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.299
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.443
When the network is plugged 0.075
And Tor is ready 17.024
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.034
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.386
Given I shutdown Tails and wait for the computer to power off 8.867
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.823
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.377
And the file system changes introduced in version 6.2~testoverlayfs are present 0.301
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.302
# 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.323
When the network is plugged 0.070
And Tor is ready 18.815
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.064
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.557
Given I shutdown Tails and wait for the computer to power off 4.143
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.094
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.315
And the file system changes introduced in version 6.3~testoverlayfs are present 0.463
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.307
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.289
When the network is plugged 0.075
And Tor is ready 17.685
Then the Upgrader considers the system as up-to-date 0.324
# 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.038
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.110
After features/support/hooks.rb:326 0.836
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
35.063
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 9.962
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.300
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.731
But a current signing key is available on our website 0.000
When the network is plugged 0.097
And Tor is ready 18.837
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.066
After features/support/hooks.rb:326 0.636
After features/support/hooks.rb:100 0.000