Project Number Date
test_Tails_ISO_stable 5339 16 Dec 2024, 22:50

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:50.846 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:28.425
Before features/support/hooks.rb:269 0.008
Given a computer 0.213
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 32.746
When I start Tails from USB drive "old" with network unplugged 1:49.509
Then the boot device has safe access rights 3.716
And Tails is running from USB drive "old" 0.401
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.350
And I unplug USB drive "old" 0.204
After features/support/hooks.rb:326 6.896
After features/support/hooks.rb:100 0.010
Tags: @product
2:23.150
Before features/support/hooks.rb:269 0.007
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login 1:37.374
Then Tails is running from USB drive "old" 0.973
And I create a persistent partition 33.084
And I take note of which tps features are available 1.970
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.693
After features/support/hooks.rb:326 0.200
After features/support/hooks.rb:100 0.010
Tags: @product
2:55.792
Before features/support/hooks.rb:269 0.006
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.153
Then Tails is running from USB drive "old" 0.626
And all tps features are active 2.092
When I write some files expected to persist 1.725
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 1.848
And all persistence configuration files have safe access rights 0.582
And all persistent directories from the old Tails version have safe access rights 3.008
And I take note of which tps features are available 0.509
And I shutdown Tails and wait for the computer to power off 4.568
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.466
After features/support/hooks.rb:326 0.154
After features/support/hooks.rb:100 0.010
Tags: @product
2:52.652
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 24.945
And I log in to a new session 21.536
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.049
And I plug USB drive "to_upgrade" 2.492
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.600
Then the running Tails is installed on USB drive "to_upgrade" 24.486
And I unplug USB drive "to_upgrade" 0.270
And I unplug USB drive "__internal" 0.270
After features/support/hooks.rb:326 2.089
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.926
Before features/support/hooks.rb:269 0.009
Given a computer 0.278
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.154
Then all tps features from the old Tails version are active 1.655
And Tails is running from USB drive "to_upgrade" 0.317
And the boot device has safe access rights 3.429
And the expected persistent files created with the old Tails version are present in the filesystem 2.510
And all persistent directories from the old Tails version have safe access rights 2.580
After features/support/hooks.rb:326 0.715
After features/support/hooks.rb:100 0.032
Tags: @product @automatic_upgrade
7:5.698
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 29.959
And no SquashFS delta is installed 0.113
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.342
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.330
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.438
When the network is plugged 0.101
And Tor is ready 20.381
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.554
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.991
Given I shutdown Tails and wait for the computer to power off 8.835
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.812
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.481
And the file system changes introduced in version 6.2~testoverlayfs are present 0.308
And only the 6.2~testoverlayfs SquashFS delta is installed 0.089
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.278
# 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.488
When the network is plugged 0.061
And Tor is ready 17.755
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.975
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.396
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 2:10.713
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 2.324
And the file system changes introduced in version 6.3~testoverlayfs are present 0.558
And only the 6.3~testoverlayfs SquashFS delta is installed 0.087
# 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.300
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.277
When the network is plugged 0.074
And Tor is ready 19.811
Then the Upgrader considers the system as up-to-date 0.307
# 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.575
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.543
After features/support/hooks.rb:326 0.825
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
37.200
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 10.473
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.295
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.091
And the signing key used by the Upgrader is outdated 1.447
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 19.656
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.167
After features/support/hooks.rb:326 0.724
After features/support/hooks.rb:100 0.000