Project Number Date
test_Tails_ISO_devel 3418 05 Jun 2024, 21:06

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:42.476 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:4.352
Before features/support/hooks.rb:269 0.007
Given a computer 0.234
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.062
And I write an old version of the Tails USB image to disk "old" 29.133
When I start Tails from USB drive "old" with network unplugged 1:29.764
Then the boot device has safe access rights 3.082
And Tails is running from USB drive "old" 0.350
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.110
And udev-watchdog is monitoring the correct device 0.307
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:315 3.523
After features/support/hooks.rb:100 0.014
Tags: @product
2:14.976
Before features/support/hooks.rb:269 0.010
Given a computer 0.230
And I start Tails from USB drive "old" with network unplugged and I login 1:26.638
Then Tails is running from USB drive "old" 0.362
And I create a persistent partition 37.024
And I take note of which tps features are available 1.501
Then a Tails persistence partition exists on USB drive "old" 0.803
And I shutdown Tails and wait for the computer to power off 8.414
After features/support/hooks.rb:315 0.193
After features/support/hooks.rb:100 0.011
Tags: @product
2:49.976
Before features/support/hooks.rb:269 0.007
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.580
Then Tails is running from USB drive "old" 0.413
And all tps features are active 2.208
When I write some files expected to persist 1.776
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.277
And all persistence configuration files have safe access rights 0.452
And all persistent directories from the old Tails version have safe access rights 2.861
And I take note of which tps features are available 0.470
And I shutdown Tails and wait for the computer to power off 4.260
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.442
After features/support/hooks.rb:315 0.160
After features/support/hooks.rb:100 0.010
Tags: @product
2:29.439
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.427
And I log in to a new session 19.935
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.332
And I plug USB drive "to_upgrade" 2.507
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.164
Then the running Tails is installed on USB drive "to_upgrade" 15.670
And I unplug USB drive "to_upgrade" 0.193
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:315 3.572
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.685
Before features/support/hooks.rb:269 0.010
Given a computer 0.224
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.806
Then all tps features from the old Tails version are active 1.931
And Tails is running from USB drive "to_upgrade" 0.442
And the boot device has safe access rights 3.807
And the expected persistent files created with the old Tails version are present in the filesystem 1.600
And all persistent directories from the old Tails version have safe access rights 2.872
After features/support/hooks.rb:315 0.911
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:58.875
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.334
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.317
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.284
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.506
When the network is plugged 0.090
And Tor is ready 20.266
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.049
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.156
Given I shutdown Tails and wait for the computer to power off 9.084
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.537
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.256
And the file system changes introduced in version 6.2~testoverlayfs are present 0.375
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.358
# 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.277
When the network is plugged 0.036
And Tor is ready 46.779
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.655
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.082
Given I shutdown Tails and wait for the computer to power off 4.511
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.369
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.279
And the file system changes introduced in version 6.3~testoverlayfs are present 0.529
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.351
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.278
When the network is plugged 0.040
And Tor is ready 20.790
Then the Upgrader considers the system as up-to-date 0.340
# 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.626
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.975
After features/support/hooks.rb:315 0.741
After features/support/hooks.rb:100 0.037
Tags: @product @automatic_upgrade
38.170
Before features/support/hooks.rb:269 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.561
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.520
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.959
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 20.455
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.568
After features/support/hooks.rb:315 0.653
After features/support/hooks.rb:100 0.000