Project Number Date
test_Tails_ISO_stable 5232 30 Oct 2024, 04:22

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:18.811 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:55.890
Before features/support/hooks.rb:269 0.005
Given a computer 0.182
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 28.795
When I start Tails from USB drive "old" with network unplugged 1:22.038
Then the boot device has safe access rights 2.837
And Tails is running from USB drive "old" 0.312
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.277
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:326 3.502
After features/support/hooks.rb:100 0.028
Tags: @product
2:4.893
Before features/support/hooks.rb:269 0.005
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login 1:18.438
Then Tails is running from USB drive "old" 0.325
And I create a persistent partition 35.096
And I take note of which tps features are available 1.512
Then a Tails persistence partition exists on USB drive "old" 0.756
And I shutdown Tails and wait for the computer to power off 8.577
After features/support/hooks.rb:326 0.146
After features/support/hooks.rb:100 0.009
Tags: @product
2:55.430
Before features/support/hooks.rb:269 0.006
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.549
Then Tails is running from USB drive "old" 0.426
And all tps features are active 1.960
When I write some files expected to persist 1.752
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.231
And all persistence configuration files have safe access rights 0.394
And all persistent directories from the old Tails version have safe access rights 2.423
And I take note of which tps features are available 0.418
And I shutdown Tails and wait for the computer to power off 4.271
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.798
After features/support/hooks.rb:326 0.092
After features/support/hooks.rb:100 0.009
Tags: @product
2:26.228
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.180
And I log in to a new session 17.814
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.546
And I plug USB drive "to_upgrade" 2.337
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.896
Then the running Tails is installed on USB drive "to_upgrade" 20.051
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.195
After features/support/hooks.rb:326 6.827
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.008
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:1.960
Then all tps features from the old Tails version are active 1.602
And Tails is running from USB drive "to_upgrade" 0.300
And the boot device has safe access rights 3.218
And the expected persistent files created with the old Tails version are present in the filesystem 1.355
And all persistent directories from the old Tails version have safe access rights 2.376
After features/support/hooks.rb:326 0.954
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:10.792
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 12.407
And no SquashFS delta is installed 0.285
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.361
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.288
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.439
When the network is plugged 0.075
And Tor is ready 17.585
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.289
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.268
Given I shutdown Tails and wait for the computer to power off 10.461
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.663
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.174
And the file system changes introduced in version 6.2~testoverlayfs are present 0.296
And only the 6.2~testoverlayfs SquashFS delta is installed 0.105
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.303
# 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.259
When the network is plugged 0.076
And Tor is ready 18.092
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.496
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.228
Given I shutdown Tails and wait for the computer to power off 4.132
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.834
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.012
And the file system changes introduced in version 6.3~testoverlayfs are present 0.440
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.399
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.291
When the network is plugged 0.092
And Tor is ready 19.097
Then the Upgrader considers the system as up-to-date 0.315
# 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 13.870
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.964
After features/support/hooks.rb:326 0.759
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
34.568
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 10.061
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.374
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.744
But a current signing key is available on our website 0.000
When the network is plugged 0.085
And Tor is ready 16.735
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.509
After features/support/hooks.rb:326 0.723
After features/support/hooks.rb:100 0.000