Project Number Date
test_Tails_ISO_stable 5143 04 Oct 2024, 12:16

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:46.020 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:10.018
Before features/support/hooks.rb:269 0.004
Given a computer 0.165
And I create a 7200 MiB disk named "old" 0.035
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 31.161
When I start Tails from USB drive "old" with network unplugged 1:33.458
Then the boot device has safe access rights 3.138
And Tails is running from USB drive "old" 0.314
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.329
And I unplug USB drive "old" 0.204
After features/support/hooks.rb:326 7.235
After features/support/hooks.rb:100 0.007
Tags: @product
2:6.127
Before features/support/hooks.rb:269 0.004
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login 1:23.646
Then Tails is running from USB drive "old" 0.353
And I create a persistent partition 31.004
And I take note of which tps features are available 1.740
Then a Tails persistence partition exists on USB drive "old" 0.792
And I shutdown Tails and wait for the computer to power off 8.414
After features/support/hooks.rb:326 0.152
After features/support/hooks.rb:100 0.008
Tags: @product
2:47.512
Before features/support/hooks.rb:269 0.005
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:9.782
Then Tails is running from USB drive "old" 0.858
And all tps features are active 1.974
When I write some files expected to persist 1.688
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.364
And all persistence configuration files have safe access rights 0.581
And all persistent directories from the old Tails version have safe access rights 3.001
And I take note of which tps features are available 0.388
And I shutdown Tails and wait for the computer to power off 4.412
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.261
After features/support/hooks.rb:326 0.152
After features/support/hooks.rb:100 0.009
Tags: @product
2:31.933
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 11.992
And I log in to a new session 19.159
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.176
And I plug USB drive "to_upgrade" 2.379
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.391
Then the running Tails is installed on USB drive "to_upgrade" 21.451
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.188
After features/support/hooks.rb:326 2.606
After features/support/hooks.rb:100 0.000
Tags: @product
2:13.106
Before features/support/hooks.rb:269 0.004
Given a computer 0.171
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.862
Then all tps features from the old Tails version are active 1.582
And Tails is running from USB drive "to_upgrade" 0.345
And the boot device has safe access rights 3.360
And the expected persistent files created with the old Tails version are present in the filesystem 1.439
And all persistent directories from the old Tails version have safe access rights 2.343
After features/support/hooks.rb:326 0.632
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:23.885
Before features/support/hooks.rb:269 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.429
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.366
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.302
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.428
When the network is plugged 0.059
And Tor is ready 22.281
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.739
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.328
Given I shutdown Tails and wait for the computer to power off 10.640
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.249
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.180
And the file system changes introduced in version 6.2~testoverlayfs are present 0.307
And only the 6.2~testoverlayfs SquashFS delta is installed 0.092
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.300
# 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.263
When the network is plugged 0.072
And Tor is ready 20.056
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.247
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.398
Given I shutdown Tails and wait for the computer to power off 4.678
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.055
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.276
And the file system changes introduced in version 6.3~testoverlayfs are present 0.519
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.299
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.376
When the network is plugged 0.067
And Tor is ready 18.448
Then the Upgrader considers the system as up-to-date 0.320
# 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 13.894
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.955
After features/support/hooks.rb:326 0.874
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
33.435
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 10.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.419
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.081
And the signing key used by the Upgrader is outdated 0.819
But a current signing key is available on our website 0.000
When the network is plugged 0.125
And Tor is ready 15.292
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.632
After features/support/hooks.rb:326 1.356
After features/support/hooks.rb:100 0.000