Project Number Date
test_Tails_ISO_stable 4806 22 Apr 2024, 15:21

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:34.328 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
1:57.351
Before features/support/hooks.rb:259 0.007
Given a computer 0.174
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 30.034
When I start Tails from USB drive "old" with network unplugged 1:22.136
Then the boot device has safe access rights 2.850
And Tails is running from USB drive "old" 0.300
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.284
And I unplug USB drive "old" 0.321
After features/support/hooks.rb:305 6.987
After features/support/hooks.rb:89 0.010
Tags: @product
2:10.329
Before features/support/hooks.rb:259 0.007
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login 1:25.754
Then Tails is running from USB drive "old" 0.298
And I create a persistent partition 33.381
And I take note of which tps features are available 1.493
Then a Tails persistence partition exists on USB drive "old" 0.876
And I shutdown Tails and wait for the computer to power off 8.333
After features/support/hooks.rb:305 0.211
After features/support/hooks.rb:89 0.012
Tags: @product
2:38.271
Before features/support/hooks.rb:259 0.007
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:1.506
Then Tails is running from USB drive "old" 0.343
And all tps features are active 1.796
When I write some files expected to persist 1.677
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.265
And all persistence configuration files have safe access rights 0.379
And all persistent directories from the old Tails version have safe access rights 2.844
And I take note of which tps features are available 0.435
And I shutdown Tails and wait for the computer to power off 4.165
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.656
After features/support/hooks.rb:305 0.127
After features/support/hooks.rb:89 0.013
Tags: @product
2:31.471
Before features/support/hooks.rb:259 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.379
And I log in to a new session 17.668
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.642
And I plug USB drive "to_upgrade" 2.389
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.847
Then the running Tails is installed on USB drive "to_upgrade" 20.174
And I unplug USB drive "to_upgrade" 0.192
And I unplug USB drive "__internal" 0.176
After features/support/hooks.rb:305 2.048
After features/support/hooks.rb:89 0.000
Tags: @product
2:12.488
Before features/support/hooks.rb:259 0.005
Given a computer 0.182
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.593
Then all tps features from the old Tails version are active 1.558
And Tails is running from USB drive "to_upgrade" 0.307
And the boot device has safe access rights 2.980
And the expected persistent files created with the old Tails version are present in the filesystem 1.583
And all persistent directories from the old Tails version have safe access rights 2.282
After features/support/hooks.rb:305 1.002
After features/support/hooks.rb:89 0.010
Tags: @product @automatic_upgrade
6:27.538
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.107
And no SquashFS delta is installed 0.195
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.365
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.299
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.480
When the network is plugged 0.034
And Tor is ready 17.855
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.679
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.823
Given I shutdown Tails and wait for the computer to power off 8.512
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.573
Then Tails is running version 6.2~testoverlayfs 0.033
And all tps features are active 2.094
And the file system changes introduced in version 6.2~testoverlayfs are present 0.328
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.307
# 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.242
When the network is plugged 0.041
And Tor is ready 18.712
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.245
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.236
Given I shutdown Tails and wait for the computer to power off 4.446
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.023
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 1.848
And the file system changes introduced in version 6.3~testoverlayfs are present 0.475
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.515
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.281
When the network is plugged 0.036
And Tor is ready 20.218
Then the Upgrader considers the system as up-to-date 0.304
# 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.152
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.869
After features/support/hooks.rb:305 0.832
After features/support/hooks.rb:89 0.028
Tags: @product @automatic_upgrade
36.875
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 10.338
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.406
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.537
But a current signing key is available on our website 0.000
When the network is plugged 0.030
And Tor is ready 18.426
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.084
After features/support/hooks.rb:305 1.212
After features/support/hooks.rb:89 0.000