Project Number Date
test_Tails_ISO_devel 3346 02 Apr 2024, 12:14

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:15.272 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:50.009
Before features/support/hooks.rb:245 0.006
Given a computer 0.197
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 20.172
When I start Tails from USB drive "old" with network unplugged 1:24.500
Then the boot device has safe access rights 2.953
And Tails is running from USB drive "old" 0.381
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.340
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:291 6.933
After features/support/hooks.rb:75 0.014
Tags: @product
2:1.703
Before features/support/hooks.rb:245 0.007
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login 1:18.580
Then Tails is running from USB drive "old" 0.305
And I create a persistent partition 33.951
And I take note of which tps features are available 1.628
Then a Tails persistence partition exists on USB drive "old" 0.797
And I shutdown Tails and wait for the computer to power off 6.262
After features/support/hooks.rb:291 0.128
After features/support/hooks.rb:75 0.009
Tags: @product
2:39.703
Before features/support/hooks.rb:245 0.006
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.541
Then Tails is running from USB drive "old" 0.363
And all tps features are active 1.950
When I write some files expected to persist 1.684
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.203
And all persistence configuration files have safe access rights 0.378
And all persistent directories from the old Tails version have safe access rights 2.445
And I take note of which tps features are available 0.454
And I shutdown Tails and wait for the computer to power off 4.406
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.094
After features/support/hooks.rb:291 0.110
After features/support/hooks.rb:75 0.011
Tags: @product
2:26.016
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.827
And I log in to a new session 16.204
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.551
And I plug USB drive "to_upgrade" 2.424
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.376
Then the running Tails is installed on USB drive "to_upgrade" 13.260
And I unplug USB drive "to_upgrade" 0.191
And I unplug USB drive "__internal" 0.180
After features/support/hooks.rb:291 3.570
After features/support/hooks.rb:75 0.000
Tags: @product
2:5.410
Before features/support/hooks.rb:245 0.006
Given a computer 0.287
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:55.872
Then all tps features from the old Tails version are active 1.586
And Tails is running from USB drive "to_upgrade" 0.331
And the boot device has safe access rights 3.096
And the expected persistent files created with the old Tails version are present in the filesystem 1.772
And all persistent directories from the old Tails version have safe access rights 2.462
After features/support/hooks.rb:291 0.664
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
6:37.765
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 26.598
And no SquashFS delta is installed 0.126
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.292
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.291
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.441
When the network is plugged 0.046
And Tor is ready 19.626
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.821
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.187
Given I shutdown Tails and wait for the computer to power off 6.782
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.820
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.200
And the file system changes introduced in version 6.2~testoverlayfs are present 0.277
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.301
# 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.299
When the network is plugged 0.038
And Tor is ready 15.720
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.912
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.046
Given I shutdown Tails and wait for the computer to power off 4.259
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.419
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.071
And the file system changes introduced in version 6.3~testoverlayfs are present 0.483
And only the 6.3~testoverlayfs SquashFS delta is installed 0.093
# 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.344
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.299
When the network is plugged 0.040
And Tor is ready 45.417
Then the Upgrader considers the system as up-to-date 0.225
# 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.016
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.084
After features/support/hooks.rb:291 0.816
After features/support/hooks.rb:75 0.018
Tags: @product @automatic_upgrade
34.663
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.289
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.335
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.520
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 18.407
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.013
After features/support/hooks.rb:291 0.686
After features/support/hooks.rb:75 0.000