Project Number Date
test_Tails_ISO_stable 5079 08 Sep 2024, 08:38

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:33.911 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:17.840
Before features/support/hooks.rb:269 0.006
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 30.352
When I start Tails from USB drive "old" with network unplugged 1:41.682
Then the boot device has safe access rights 3.337
And Tails is running from USB drive "old" 0.378
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.322
And I unplug USB drive "old" 0.276
After features/support/hooks.rb:326 3.701
After features/support/hooks.rb:100 0.009
Tags: @product
2:17.507
Before features/support/hooks.rb:269 0.009
Given a computer 0.216
And I start Tails from USB drive "old" with network unplugged and I login 1:32.906
Then Tails is running from USB drive "old" 0.360
And I create a persistent partition 32.690
And I take note of which tps features are available 2.167
Then a Tails persistence partition exists on USB drive "old" 0.842
And I shutdown Tails and wait for the computer to power off 8.325
After features/support/hooks.rb:326 0.186
After features/support/hooks.rb:100 0.010
Tags: @product
3:1.460
Before features/support/hooks.rb:269 0.006
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.385
Then Tails is running from USB drive "old" 0.430
And all tps features are active 2.396
When I write some files expected to persist 2.440
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
And all persistence configuration files have safe access rights 0.401
And all persistent directories from the old Tails version have safe access rights 2.732
And I take note of which tps features are available 0.561
And I shutdown Tails and wait for the computer to power off 4.174
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.516
After features/support/hooks.rb:326 0.141
After features/support/hooks.rb:100 0.009
Tags: @product
2:49.916
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 27.716
And I log in to a new session 20.374
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.744
And I plug USB drive "to_upgrade" 2.380
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.385
Then the running Tails is installed on USB drive "to_upgrade" 20.710
And I unplug USB drive "to_upgrade" 0.379
And I unplug USB drive "__internal" 0.225
After features/support/hooks.rb:326 2.970
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.137
Before features/support/hooks.rb:269 0.008
Given a computer 0.223
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.036
Then all tps features from the old Tails version are active 1.785
And Tails is running from USB drive "to_upgrade" 0.404
And the boot device has safe access rights 3.992
And the expected persistent files created with the old Tails version are present in the filesystem 1.695
And all persistent directories from the old Tails version have safe access rights 2.998
After features/support/hooks.rb:326 0.765
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
7:0.372
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 11.883
And no SquashFS delta is installed 0.871
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.724
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.283
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.453
When the network is plugged 0.063
And Tor is ready 17.386
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.841
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.447
Given I shutdown Tails and wait for the computer to power off 10.930
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.310
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.287
And the file system changes introduced in version 6.2~testoverlayfs are present 0.357
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.343
# 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.305
When the network is plugged 0.089
And Tor is ready 18.493
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.978
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.967
Given I shutdown Tails and wait for the computer to power off 6.809
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:20.577
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 5.784
And the file system changes introduced in version 6.3~testoverlayfs are present 0.486
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.853
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.307
When the network is plugged 0.744
And Tor is ready 19.754
Then the Upgrader considers the system as up-to-date 0.337
# 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.298
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.159
After features/support/hooks.rb:326 0.807
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
45.676
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 17.418
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.063
And the signing key used by the Upgrader is outdated 1.504
But a current signing key is available on our website 0.000
When the network is plugged 0.086
And Tor is ready 21.006
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.262
After features/support/hooks.rb:326 0.694
After features/support/hooks.rb:100 0.000