Project Number Date
test_Tails_ISO_stable 5386 11 Jan 2025, 08:27

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 18:20.118 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
1:58.929
Before features/support/hooks.rb:269 0.005
Given a computer 0.179
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 27.290
When I start Tails from USB drive "old" with network unplugged 1:26.526
Then the boot device has safe access rights 2.891
And Tails is running from USB drive "old" 0.304
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.306
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:326 3.551
After features/support/hooks.rb:100 0.008
Tags: @product
2:4.536
Before features/support/hooks.rb:269 0.005
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login 1:23.299
Then Tails is running from USB drive "old" 0.301
And I create a persistent partition 30.402
And I take note of which tps features are available 1.405
Then a Tails persistence partition exists on USB drive "old" 0.748
And I shutdown Tails and wait for the computer to power off 8.190
After features/support/hooks.rb:326 0.167
After features/support/hooks.rb:100 0.008
Tags: @product
2:44.919
Before features/support/hooks.rb:269 0.006
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:8.125
Then Tails is running from USB drive "old" 0.762
And all tps features are active 1.821
When I write some files expected to persist 2.060
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.270
And all persistence configuration files have safe access rights 0.404
And all persistent directories from the old Tails version have safe access rights 2.774
And I take note of which tps features are available 0.432
And I shutdown Tails and wait for the computer to power off 4.244
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.827
After features/support/hooks.rb:326 0.140
After features/support/hooks.rb:100 0.009
Tags: @product
2:26.417
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.699
And I log in to a new session 17.673
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.559
And I plug USB drive "to_upgrade" 2.349
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.113
Then the running Tails is installed on USB drive "to_upgrade" 20.564
And I unplug USB drive "to_upgrade" 0.239
And I unplug USB drive "__internal" 0.216
After features/support/hooks.rb:326 2.395
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.572
Before features/support/hooks.rb:269 0.006
Given a computer 0.195
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.685
Then all tps features from the old Tails version are active 1.655
And Tails is running from USB drive "to_upgrade" 0.294
And the boot device has safe access rights 2.946
And the expected persistent files created with the old Tails version are present in the filesystem 1.479
And all persistent directories from the old Tails version have safe access rights 2.314
After features/support/hooks.rb:326 0.656
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
6:14.562
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 12.952
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.279
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.342
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.520
When the network is plugged 0.070
And Tor is ready 21.722
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.406
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.306
Given I shutdown Tails and wait for the computer to power off 8.441
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.292
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.962
And the file system changes introduced in version 6.2~testoverlayfs are present 0.272
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.275
# 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.278
When the network is plugged 0.078
And Tor is ready 18.883
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.927
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.623
Given I shutdown Tails and wait for the computer to power off 4.263
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.021
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.003
And the file system changes introduced in version 6.3~testoverlayfs are present 0.614
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.402
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.370
When the network is plugged 0.077
And Tor is ready 17.650
Then the Upgrader considers the system as up-to-date 0.394
# 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.810
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.002
After features/support/hooks.rb:326 0.785
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
33.180
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.710
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.248
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.063
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 18.043
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.993
After features/support/hooks.rb:326 0.680
After features/support/hooks.rb:100 0.000