Project Number Date
test_Tails_ISO_stable 5148 07 Oct 2024, 12:37

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 20:31.340 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:23.291
Before features/support/hooks.rb:269 0.005
Given a computer 0.191
And I create a 7200 MiB disk named "old" 0.063
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 34.527
When I start Tails from USB drive "old" with network unplugged 1:43.298
Then the boot device has safe access rights 3.104
And Tails is running from USB drive "old" 0.350
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.328
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:326 7.285
After features/support/hooks.rb:100 0.008
Tags: @product
2:14.971
Before features/support/hooks.rb:269 0.005
Given a computer 0.795
And I start Tails from USB drive "old" with network unplugged and I login 1:26.392
Then Tails is running from USB drive "old" 0.335
And I create a persistent partition 36.502
And I take note of which tps features are available 1.479
Then a Tails persistence partition exists on USB drive "old" 0.818
And I shutdown Tails and wait for the computer to power off 8.648
After features/support/hooks.rb:326 0.174
After features/support/hooks.rb:100 0.009
Tags: @product
3:10.693
Before features/support/hooks.rb:269 0.005
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:28.493
Then Tails is running from USB drive "old" 0.469
And all tps features are active 2.210
When I write some files expected to persist 3.357
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.213
And all persistence configuration files have safe access rights 0.343
And all persistent directories from the old Tails version have safe access rights 2.343
And I take note of which tps features are available 0.567
And I shutdown Tails and wait for the computer to power off 6.712
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.776
After features/support/hooks.rb:326 0.147
After features/support/hooks.rb:100 0.027
Tags: @product
2:47.338
Before features/support/hooks.rb:269 0.013
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.622
And I log in to a new session 22.589
And I clone USB drive "old" to a new USB drive "to_upgrade" 3.831
And I plug USB drive "to_upgrade" 3.182
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.372
Then the running Tails is installed on USB drive "to_upgrade" 19.229
And I unplug USB drive "to_upgrade" 0.220
And I unplug USB drive "__internal" 0.291
After features/support/hooks.rb:326 7.102
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.821
Before features/support/hooks.rb:269 0.008
Given a computer 0.293
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.541
Then all tps features from the old Tails version are active 1.816
And Tails is running from USB drive "to_upgrade" 0.366
And the boot device has safe access rights 3.680
And the expected persistent files created with the old Tails version are present in the filesystem 1.635
And all persistent directories from the old Tails version have safe access rights 2.487
After features/support/hooks.rb:326 0.834
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:53.524
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.124
And no SquashFS delta is installed 0.096
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.511
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.100
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.313
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.464
When the network is plugged 0.078
And Tor is ready 22.959
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.269
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.868
Given I shutdown Tails and wait for the computer to power off 8.967
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.545
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.622
And the file system changes introduced in version 6.2~testoverlayfs are present 0.509
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.362
# 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.338
When the network is plugged 0.065
And Tor is ready 22.016
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.526
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.508
Given I shutdown Tails and wait for the computer to power off 6.690
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.555
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.312
And the file system changes introduced in version 6.3~testoverlayfs are present 0.553
And only the 6.3~testoverlayfs SquashFS delta is installed 0.098
# 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.340
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.314
When the network is plugged 0.069
And Tor is ready 17.857
Then the Upgrader considers the system as up-to-date 0.380
# 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 15.832
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.155
After features/support/hooks.rb:326 0.871
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
40.699
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.504
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.447
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the signing key used by the Upgrader is outdated 0.848
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 20.564
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.181
After features/support/hooks.rb:326 0.810
After features/support/hooks.rb:100 0.000