Project Number Date
test_Tails_ISO_stable 5202 21 Oct 2024, 08:57

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:44.830 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:11.616
Before features/support/hooks.rb:269 0.007
Given a computer 0.207
And I create a 7200 MiB disk named "old" 0.064
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 32.818
When I start Tails from USB drive "old" with network unplugged 1:33.253
Then the boot device has safe access rights 3.224
And Tails is running from USB drive "old" 0.319
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.325
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:326 3.792
After features/support/hooks.rb:100 0.013
Tags: @product
2:14.396
Before features/support/hooks.rb:269 0.007
Given a computer 0.269
And I start Tails from USB drive "old" with network unplugged and I login 1:29.015
Then Tails is running from USB drive "old" 0.370
And I create a persistent partition 33.430
And I take note of which tps features are available 1.963
Then a Tails persistence partition exists on USB drive "old" 0.852
And I shutdown Tails and wait for the computer to power off 8.494
After features/support/hooks.rb:326 0.176
After features/support/hooks.rb:100 0.008
Tags: @product
3:0.218
Before features/support/hooks.rb:269 0.006
Given a computer 0.248
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.333
Then Tails is running from USB drive "old" 0.899
And all tps features are active 2.067
When I write some files expected to persist 1.862
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 1.174
And all persistence configuration files have safe access rights 1.237
And all persistent directories from the old Tails version have safe access rights 2.902
And I take note of which tps features are available 0.728
And I shutdown Tails and wait for the computer to power off 4.374
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.388
After features/support/hooks.rb:326 0.116
After features/support/hooks.rb:100 0.010
Tags: @product
2:38.881
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 10.807
And I log in to a new session 21.475
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.814
And I plug USB drive "to_upgrade" 2.502
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.909
Then the running Tails is installed on USB drive "to_upgrade" 25.916
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.241
After features/support/hooks.rb:326 4.851
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.210
Before features/support/hooks.rb:269 0.005
Given a computer 0.212
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.599
Then all tps features from the old Tails version are active 2.054
And Tails is running from USB drive "to_upgrade" 0.394
And the boot device has safe access rights 3.746
And the expected persistent files created with the old Tails version are present in the filesystem 1.465
And all persistent directories from the old Tails version have safe access rights 2.737
After features/support/hooks.rb:326 0.869
After features/support/hooks.rb:100 0.050
Tags: @product @automatic_upgrade
7:18.955
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 30.894
And no SquashFS delta is installed 0.132
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.369
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.507
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.595
When the network is plugged 0.116
And Tor is ready 22.306
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.082
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.273
Given I shutdown Tails and wait for the computer to power off 11.242
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.942
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 3.212
And the file system changes introduced in version 6.2~testoverlayfs are present 0.377
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.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.460
When the network is plugged 0.101
And Tor is ready 20.426
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.900
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.479
Given I shutdown Tails and wait for the computer to power off 4.538
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.988
Then Tails is running version 6.3~testoverlayfs 0.032
And all tps features are active 5.970
And the file system changes introduced in version 6.3~testoverlayfs are present 0.671
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.317
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.391
When the network is plugged 0.447
And Tor is ready 18.594
Then the Upgrader considers the system as up-to-date 0.403
# 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 16.396
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.184
After features/support/hooks.rb:326 0.983
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
1:3.550
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 13.215
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.398
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.139
And the signing key used by the Upgrader is outdated 1.142
But a current signing key is available on our website 0.000
When the network is plugged 0.220
And Tor is ready 47.724
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.709
After features/support/hooks.rb:326 0.720
After features/support/hooks.rb:100 0.000