Project Number Date
test_Tails_ISO_stable 4843 15 May 2024, 18:44

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:43.651 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.677
Before features/support/hooks.rb:259 0.006
Given a computer 0.177
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 31.691
When I start Tails from USB drive "old" with network unplugged 1:33.565
Then the boot device has safe access rights 3.047
And Tails is running from USB drive "old" 0.342
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.337
And I unplug USB drive "old" 0.226
After features/support/hooks.rb:305 8.111
After features/support/hooks.rb:89 0.015
Tags: @product
2:19.954
Before features/support/hooks.rb:259 0.009
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login 1:21.786
Then Tails is running from USB drive "old" 0.390
And I create a persistent partition 46.486
And I take note of which tps features are available 1.746
Then a Tails persistence partition exists on USB drive "old" 0.930
And I shutdown Tails and wait for the computer to power off 8.413
After features/support/hooks.rb:305 0.165
After features/support/hooks.rb:89 0.009
Tags: @product
2:58.634
Before features/support/hooks.rb:259 0.007
Given a computer 0.169
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.875
Then Tails is running from USB drive "old" 0.461
And all tps features are active 2.331
When I write some files expected to persist 1.808
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.238
And all persistence configuration files have safe access rights 0.396
And all persistent directories from the old Tails version have safe access rights 3.076
And I take note of which tps features are available 0.455
And I shutdown Tails and wait for the computer to power off 6.435
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.384
After features/support/hooks.rb:305 0.099
After features/support/hooks.rb:89 0.009
Tags: @product
2:30.430
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 13.550
And I log in to a new session 18.720
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.390
And I plug USB drive "to_upgrade" 2.530
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.108
Then the running Tails is installed on USB drive "to_upgrade" 19.708
And I unplug USB drive "to_upgrade" 0.229
And I unplug USB drive "__internal" 0.191
After features/support/hooks.rb:305 1.909
After features/support/hooks.rb:89 0.000
Tags: @product
2:15.489
Before features/support/hooks.rb:259 0.010
Given a computer 0.197
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.876
Then all tps features from the old Tails version are active 1.464
And Tails is running from USB drive "to_upgrade" 0.356
And the boot device has safe access rights 3.260
And the expected persistent files created with the old Tails version are present in the filesystem 1.878
And all persistent directories from the old Tails version have safe access rights 2.454
After features/support/hooks.rb:305 0.659
After features/support/hooks.rb:89 0.010
Tags: @product @automatic_upgrade
6:49.499
Before features/support/hooks.rb:259 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.817
And no SquashFS delta is installed 0.128
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.373
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.292
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.430
When the network is plugged 0.104
And Tor is ready 19.780
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.168
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.483
Given I shutdown Tails and wait for the computer to power off 13.177
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.523
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.035
And the file system changes introduced in version 6.2~testoverlayfs are present 0.278
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.331
# 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.262
When the network is plugged 0.125
And Tor is ready 17.739
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.678
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.743
Given I shutdown Tails and wait for the computer to power off 4.371
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.259
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.156
And the file system changes introduced in version 6.3~testoverlayfs are present 0.474
And only the 6.3~testoverlayfs SquashFS delta is installed 0.055
# 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.331
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.329
When the network is plugged 0.048
And Tor is ready 19.849
Then the Upgrader considers the system as up-to-date 0.341
# 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 14.511
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.144
After features/support/hooks.rb:305 0.913
After features/support/hooks.rb:89 0.035
Tags: @product @automatic_upgrade
38.963
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.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.289
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.512
But a current signing key is available on our website 0.000
When the network is plugged 0.057
And Tor is ready 20.043
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.927
After features/support/hooks.rb:305 0.838
After features/support/hooks.rb:89 0.000