Project Number Date
test_Tails_ISO_stable 5242 31 Oct 2024, 19:07

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:16.303 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:11.886
Before features/support/hooks.rb:269 0.005
Given a computer 0.187
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 31.895
When I start Tails from USB drive "old" with network unplugged 1:34.129
Then the boot device has safe access rights 3.492
And Tails is running from USB drive "old" 0.381
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.321
And I unplug USB drive "old" 0.207
After features/support/hooks.rb:326 7.254
After features/support/hooks.rb:100 0.010
Tags: @product
2:8.086
Before features/support/hooks.rb:269 0.008
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login 1:24.850
Then Tails is running from USB drive "old" 0.348
And I create a persistent partition 31.957
And I take note of which tps features are available 1.429
Then a Tails persistence partition exists on USB drive "old" 0.840
And I shutdown Tails and wait for the computer to power off 8.459
After features/support/hooks.rb:326 0.224
After features/support/hooks.rb:100 0.010
Tags: @product
2:51.717
Before features/support/hooks.rb:269 0.008
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.124
Then Tails is running from USB drive "old" 0.418
And all tps features are active 1.989
When I write some files expected to persist 2.116
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.248
And all persistence configuration files have safe access rights 0.483
And all persistent directories from the old Tails version have safe access rights 2.901
And I take note of which tps features are available 0.419
And I shutdown Tails and wait for the computer to power off 4.378
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.443
After features/support/hooks.rb:326 0.170
After features/support/hooks.rb:100 0.011
Tags: @product
2:43.509
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 11.417
And I log in to a new session 22.804
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.193
And I plug USB drive "to_upgrade" 2.499
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.988
Then the running Tails is installed on USB drive "to_upgrade" 25.214
And I unplug USB drive "to_upgrade" 0.193
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:326 2.222
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.329
Before features/support/hooks.rb:269 0.006
Given a computer 0.193
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.747
Then all tps features from the old Tails version are active 1.644
And Tails is running from USB drive "to_upgrade" 0.372
And the boot device has safe access rights 3.368
And the expected persistent files created with the old Tails version are present in the filesystem 1.397
And all persistent directories from the old Tails version have safe access rights 2.604
After features/support/hooks.rb:326 0.690
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:26.964
Before features/support/hooks.rb:269 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.514
And no SquashFS delta is installed 0.149
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.477
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.293
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.613
When the network is plugged 0.144
And Tor is ready 22.903
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.501
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.712
Given I shutdown Tails and wait for the computer to power off 8.671
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.369
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.149
And the file system changes introduced in version 6.2~testoverlayfs are present 0.470
And only the 6.2~testoverlayfs SquashFS delta is installed 0.118
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.502
# 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.326
When the network is plugged 0.062
And Tor is ready 19.750
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.473
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.393
Given I shutdown Tails and wait for the computer to power off 4.337
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.564
Then Tails is running version 6.3~testoverlayfs 0.070
And all tps features are active 2.221
And the file system changes introduced in version 6.3~testoverlayfs are present 0.491
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.342
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.294
When the network is plugged 0.067
And Tor is ready 20.660
Then the Upgrader considers the system as up-to-date 0.319
# 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.870
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.970
After features/support/hooks.rb:326 0.750
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
37.809
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.345
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.337
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.739
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 19.663
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.584
After features/support/hooks.rb:326 0.684
After features/support/hooks.rb:100 0.000