Project Number Date
test_Tails_ISO_stable 4830 06 May 2024, 15:32

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 19:13.233 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:3.595
Before features/support/hooks.rb:259 0.006
Given a computer 0.179
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 29.423
When I start Tails from USB drive "old" with network unplugged 1:28.647
Then the boot device has safe access rights 3.247
And Tails is running from USB drive "old" 0.324
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.086
And udev-watchdog is monitoring the correct device 0.310
And I unplug USB drive "old" 0.211
After features/support/hooks.rb:305 7.271
After features/support/hooks.rb:89 0.011
Tags: @product
2:12.912
Before features/support/hooks.rb:259 0.007
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login 1:25.437
Then Tails is running from USB drive "old" 0.331
And I create a persistent partition 35.133
And I take note of which tps features are available 2.276
Then a Tails persistence partition exists on USB drive "old" 0.898
And I shutdown Tails and wait for the computer to power off 8.636
After features/support/hooks.rb:305 0.201
After features/support/hooks.rb:89 0.010
Tags: @product
2:51.443
Before features/support/hooks.rb:259 0.006
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.959
Then Tails is running from USB drive "old" 0.405
And all tps features are active 2.163
When I write some files expected to persist 1.795
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.206
And all persistence configuration files have safe access rights 0.467
And all persistent directories from the old Tails version have safe access rights 2.713
And I take note of which tps features are available 0.897
And I shutdown Tails and wait for the computer to power off 4.436
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.191
After features/support/hooks.rb:305 0.150
After features/support/hooks.rb:89 0.008
Tags: @product
2:26.620
Before features/support/hooks.rb:259 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.330
And I log in to a new session 17.666
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.607
And I plug USB drive "to_upgrade" 2.399
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.912
Then the running Tails is installed on USB drive "to_upgrade" 20.279
And I unplug USB drive "to_upgrade" 0.242
And I unplug USB drive "__internal" 0.180
After features/support/hooks.rb:305 2.570
After features/support/hooks.rb:89 0.000
Tags: @product
2:16.380
Before features/support/hooks.rb:259 0.008
Given a computer 0.187
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.803
Then all tps features from the old Tails version are active 1.822
And Tails is running from USB drive "to_upgrade" 0.313
And the boot device has safe access rights 3.079
And the expected persistent files created with the old Tails version are present in the filesystem 1.464
And all persistent directories from the old Tails version have safe access rights 2.709
After features/support/hooks.rb:305 0.837
After features/support/hooks.rb:89 0.010
Tags: @product @automatic_upgrade
6:48.431
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.519
And no SquashFS delta is installed 0.306
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.407
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.320
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.522
When the network is plugged 0.039
And Tor is ready 22.779
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.602
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.385
Given I shutdown Tails and wait for the computer to power off 9.631
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.923
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.288
And the file system changes introduced in version 6.2~testoverlayfs are present 0.342
And only the 6.2~testoverlayfs SquashFS delta is installed 0.090
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.525
# 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.287
When the network is plugged 0.047
And Tor is ready 17.614
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.349
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.208
Given I shutdown Tails and wait for the computer to power off 4.347
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.077
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.098
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.070
# 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.389
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.313
When the network is plugged 0.047
And Tor is ready 50.878
Then the Upgrader considers the system as up-to-date 0.350
# 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.081
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.976
After features/support/hooks.rb:305 0.711
After features/support/hooks.rb:89 0.015
Tags: @product @automatic_upgrade
33.850
Before features/support/hooks.rb:259 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.983
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.446
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.451
But a current signing key is available on our website 0.000
When the network is plugged 0.053
And Tor is ready 16.253
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.595
After features/support/hooks.rb:305 1.357
After features/support/hooks.rb:89 0.000