Project Number Date
test_Tails_ISO_stable 4991 01 Aug 2024, 16:04

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 21:25.117 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:47.428
Before features/support/hooks.rb:269 0.006
Given a computer 0.479
And I create a 7200 MiB disk named "old" 0.083
And I plug USB drive "old" 1.077
And I write an old version of the Tails USB image to disk "old" 1:0.133
When I start Tails from USB drive "old" with network unplugged 1:41.412
Then the boot device has safe access rights 3.235
And Tails is running from USB drive "old" 0.343
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.329
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:326 3.909
After features/support/hooks.rb:100 0.010
Tags: @product
2:14.318
Before features/support/hooks.rb:269 0.006
Given a computer 1.163
And I start Tails from USB drive "old" with network unplugged and I login 1:29.848
Then Tails is running from USB drive "old" 0.370
And I create a persistent partition 31.657
And I take note of which tps features are available 2.030
Then a Tails persistence partition exists on USB drive "old" 0.738
And I shutdown Tails and wait for the computer to power off 8.509
After features/support/hooks.rb:326 0.204
After features/support/hooks.rb:100 0.012
Tags: @product
3:9.801
Before features/support/hooks.rb:269 0.008
Given a computer 0.239
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:31.545
Then Tails is running from USB drive "old" 0.435
And all tps features are active 2.414
When I write some files expected to persist 2.032
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.300
And all persistence configuration files have safe access rights 0.376
And all persistent directories from the old Tails version have safe access rights 2.700
And I take note of which tps features are available 0.491
And I shutdown Tails and wait for the computer to power off 4.443
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.821
After features/support/hooks.rb:326 0.135
After features/support/hooks.rb:100 0.008
Tags: @product
2:39.319
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 12.534
And I log in to a new session 21.808
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.332
And I plug USB drive "to_upgrade" 2.353
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.139
Then the running Tails is installed on USB drive "to_upgrade" 25.720
And I unplug USB drive "to_upgrade" 0.225
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:326 2.000
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.080
Before features/support/hooks.rb:269 0.005
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.182
Then all tps features from the old Tails version are active 1.645
And Tails is running from USB drive "to_upgrade" 0.321
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.722
And all persistent directories from the old Tails version have safe access rights 2.647
After features/support/hooks.rb:326 0.838
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
7:13.513
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 15.422
And no SquashFS delta is installed 0.393
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.355
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.091
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.376
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.536
When the network is plugged 0.050
And Tor is ready 49.112
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.623
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.356
Given I shutdown Tails and wait for the computer to power off 11.258
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.546
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.243
And the file system changes introduced in version 6.2~testoverlayfs are present 0.285
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.328
# 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.281
When the network is plugged 0.051
And Tor is ready 18.618
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.421
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.759
Given I shutdown Tails and wait for the computer to power off 4.580
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.910
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.072
And the file system changes introduced in version 6.3~testoverlayfs are present 0.545
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.346
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.447
When the network is plugged 0.039
And Tor is ready 20.725
Then the Upgrader considers the system as up-to-date 0.311
# 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.180
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.066
After features/support/hooks.rb:326 0.927
After features/support/hooks.rb:100 0.028
Tags: @product @automatic_upgrade
53.654
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 23.747
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.431
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.102
And the signing key used by the Upgrader is outdated 1.748
But a current signing key is available on our website 0.000
When the network is plugged 0.053
And Tor is ready 20.369
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.201
After features/support/hooks.rb:326 0.760
After features/support/hooks.rb:100 0.000