Project Number Date
test_Tails_ISO_stable 4703 08 Mar 2024, 14:51

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 19:17.226 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:30.169
Before features/support/hooks.rb:245 0.005
Given a computer 0.153
And I create a 7200 MiB disk named "old" 0.030
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 18.469
When I start Tails from USB drive "old" with network unplugged 1:6.723
Then the boot device has safe access rights 2.876
And Tails is running from USB drive "old" 0.282
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.262
And I unplug USB drive "old" 0.178
After features/support/hooks.rb:291 6.760
After features/support/hooks.rb:75 0.009
Tags: @product
2:5.662
Before features/support/hooks.rb:245 0.005
Given a computer 0.140
And I start Tails from USB drive "old" with network unplugged and I login 1:14.381
Then Tails is running from USB drive "old" 0.283
And I create a persistent partition 41.100
And I take note of which tps features are available 1.878
Then a Tails persistence partition exists on USB drive "old" 0.818
And I shutdown Tails and wait for the computer to power off 7.059
After features/support/hooks.rb:291 0.159
After features/support/hooks.rb:75 0.010
Tags: @product
2:36.787
Before features/support/hooks.rb:245 0.006
Given a computer 0.152
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.789
Then Tails is running from USB drive "old" 0.334
And all tps features are active 1.610
When I write some files expected to persist 1.629
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.188
And all persistence configuration files have safe access rights 0.351
And all persistent directories from the old Tails version have safe access rights 2.388
And I take note of which tps features are available 0.291
And I shutdown Tails and wait for the computer to power off 4.159
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.891
After features/support/hooks.rb:291 0.156
After features/support/hooks.rb:75 0.010
Tags: @product
2:30.829
Before features/support/hooks.rb:245 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.795
And I log in to a new session 15.230
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.482
And I plug USB drive "to_upgrade" 2.479
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.582
Then the running Tails is installed on USB drive "to_upgrade" 13.816
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.244
After features/support/hooks.rb:291 3.641
After features/support/hooks.rb:75 0.000
Tags: @product
2:25.948
Before features/support/hooks.rb:245 0.006
Given a computer 0.381
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.467
Then all tps features from the old Tails version are active 1.717
And Tails is running from USB drive "to_upgrade" 0.360
And the boot device has safe access rights 3.335
And the expected persistent files created with the old Tails version are present in the filesystem 1.454
And all persistent directories from the old Tails version have safe access rights 2.231
After features/support/hooks.rb:291 0.954
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
7:34.446
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 39.710
And no SquashFS delta is installed 0.104
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.346
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.298
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.429
When the network is plugged 0.046
And Tor is ready 19.203
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.596
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.275
Given I shutdown Tails and wait for the computer to power off 8.067
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:24.446
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 1.943
And the file system changes introduced in version 6.2~testoverlayfs are present 0.317
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.291
# 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.296
When the network is plugged 0.027
And Tor is ready 45.718
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.583
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.205
Given I shutdown Tails and wait for the computer to power off 4.076
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.933
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.902
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.059
# 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.277
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.256
When the network is plugged 0.055
And Tor is ready 16.220
Then the Upgrader considers the system as up-to-date 0.238
# 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.027
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.854
After features/support/hooks.rb:291 0.752
After features/support/hooks.rb:75 0.014
Tags: @product @automatic_upgrade
33.383
Before features/support/hooks.rb:245 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.098
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.284
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 1.256
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 15.144
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.497
After features/support/hooks.rb:291 0.643
After features/support/hooks.rb:75 0.000