Project Number Date
test_Tails_ISO_stable 4817 30 Apr 2024, 15:40

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:27.227 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.030
Before features/support/hooks.rb:259 0.005
Given a computer 0.208
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 32.783
When I start Tails from USB drive "old" with network unplugged 1:31.686
Then the boot device has safe access rights 3.142
And Tails is running from USB drive "old" 0.362
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.360
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:305 3.569
After features/support/hooks.rb:89 0.008
Tags: @product
2:18.713
Before features/support/hooks.rb:259 0.006
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login 1:29.137
Then Tails is running from USB drive "old" 0.458
And I create a persistent partition 35.609
And I take note of which tps features are available 1.898
Then a Tails persistence partition exists on USB drive "old" 0.777
And I shutdown Tails and wait for the computer to power off 10.637
After features/support/hooks.rb:305 0.275
After features/support/hooks.rb:89 0.011
Tags: @product
2:53.650
Before features/support/hooks.rb:259 0.005
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.538
Then Tails is running from USB drive "old" 0.319
And all tps features are active 2.051
When I write some files expected to persist 1.719
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.217
And all persistence configuration files have safe access rights 0.459
And all persistent directories from the old Tails version have safe access rights 2.546
And I take note of which tps features are available 0.446
And I shutdown Tails and wait for the computer to power off 4.423
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.750
After features/support/hooks.rb:305 0.161
After features/support/hooks.rb:89 0.011
Tags: @product
2:31.860
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.017
And I log in to a new session 20.486
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.508
And I plug USB drive "to_upgrade" 2.623
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.776
Then the running Tails is installed on USB drive "to_upgrade" 16.943
And I unplug USB drive "to_upgrade" 0.258
And I unplug USB drive "__internal" 0.245
After features/support/hooks.rb:305 2.601
After features/support/hooks.rb:89 0.000
Tags: @product
2:18.041
Before features/support/hooks.rb:259 0.008
Given a computer 0.211
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.380
Then all tps features from the old Tails version are active 1.669
And Tails is running from USB drive "to_upgrade" 0.348
And the boot device has safe access rights 3.486
And the expected persistent files created with the old Tails version are present in the filesystem 1.544
And all persistent directories from the old Tails version have safe access rights 2.399
After features/support/hooks.rb:305 0.669
After features/support/hooks.rb:89 0.008
Tags: @product @automatic_upgrade
6:37.136
Before features/support/hooks.rb:259 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.647
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.362
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.297
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.524
When the network is plugged 0.056
And Tor is ready 21.553
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.572
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.125
Given I shutdown Tails and wait for the computer to power off 9.634
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.747
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 3.547
And the file system changes introduced in version 6.2~testoverlayfs are present 0.343
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.400
# 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.294
When the network is plugged 0.039
And Tor is ready 22.000
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.463
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.097
Given I shutdown Tails and wait for the computer to power off 4.549
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.446
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.162
And the file system changes introduced in version 6.3~testoverlayfs are present 0.523
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.306
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.272
When the network is plugged 0.048
And Tor is ready 20.127
Then the Upgrader considers the system as up-to-date 0.317
# 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 15.416
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.929
After features/support/hooks.rb:305 0.823
After features/support/hooks.rb:89 0.022
Tags: @product @automatic_upgrade
37.795
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 9.843
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.351
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 0.783
But a current signing key is available on our website 0.000
When the network is plugged 0.039
And Tor is ready 21.150
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.556
After features/support/hooks.rb:305 0.717
After features/support/hooks.rb:89 0.000