Project Number Date
test_Tails_ISO_stable 4910 23 Jun 2024, 12:19

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:33.417 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:29.977
Before features/support/hooks.rb:269 0.007
Given a computer 0.265
And I create a 7200 MiB disk named "old" 0.062
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 28.819
When I start Tails from USB drive "old" with network unplugged 1:55.773
Then the boot device has safe access rights 2.969
And Tails is running from USB drive "old" 0.378
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.304
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:326 6.955
After features/support/hooks.rb:100 0.010
Tags: @product
2:3.483
Before features/support/hooks.rb:269 0.006
Given a computer 0.236
And I start Tails from USB drive "old" with network unplugged and I login 1:21.781
Then Tails is running from USB drive "old" 0.323
And I create a persistent partition 30.542
And I take note of which tps features are available 1.490
Then a Tails persistence partition exists on USB drive "old" 0.734
And I shutdown Tails and wait for the computer to power off 8.374
After features/support/hooks.rb:326 0.170
After features/support/hooks.rb:100 0.011
Tags: @product
2:50.578
Before features/support/hooks.rb:269 0.006
Given a computer 0.243
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.502
Then Tails is running from USB drive "old" 0.314
And all tps features are active 2.353
When I write some files expected to persist 1.788
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.215
And all persistence configuration files have safe access rights 0.381
And all persistent directories from the old Tails version have safe access rights 2.404
And I take note of which tps features are available 0.464
And I shutdown Tails and wait for the computer to power off 4.461
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.449
After features/support/hooks.rb:326 0.146
After features/support/hooks.rb:100 0.010
Tags: @product
2:31.679
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 13.441
And I log in to a new session 19.626
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.359
And I plug USB drive "to_upgrade" 2.477
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.795
Then the running Tails is installed on USB drive "to_upgrade" 20.527
And I unplug USB drive "to_upgrade" 0.233
And I unplug USB drive "__internal" 0.216
After features/support/hooks.rb:326 1.983
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.551
Before features/support/hooks.rb:269 0.010
Given a computer 0.272
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.467
Then all tps features from the old Tails version are active 2.001
And Tails is running from USB drive "to_upgrade" 0.380
And the boot device has safe access rights 3.455
And the expected persistent files created with the old Tails version are present in the filesystem 1.566
And all persistent directories from the old Tails version have safe access rights 2.406
After features/support/hooks.rb:326 0.655
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:25.826
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.878
And no SquashFS delta is installed 0.110
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.309
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.281
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.540
When the network is plugged 0.039
And Tor is ready 18.076
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.779
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.483
Given I shutdown Tails and wait for the computer to power off 8.603
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.504
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.131
And the file system changes introduced in version 6.2~testoverlayfs are present 0.305
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.319
# 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.312
When the network is plugged 0.043
And Tor is ready 19.957
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.788
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.851
Given I shutdown Tails and wait for the computer to power off 4.349
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.998
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.156
And the file system changes introduced in version 6.3~testoverlayfs are present 0.485
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.373
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.388
When the network is plugged 0.055
And Tor is ready 19.356
Then the Upgrader considers the system as up-to-date 0.322
# 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.715
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.079
After features/support/hooks.rb:326 0.729
After features/support/hooks.rb:100 0.087
Tags: @product @automatic_upgrade
58.321
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.636
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.501
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.752
But a current signing key is available on our website 0.000
When the network is plugged 0.106
And Tor is ready 46.677
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.591
After features/support/hooks.rb:326 0.742
After features/support/hooks.rb:100 0.000