Project Number Date
test_Tails_ISO_devel 3391 16 May 2024, 18:19

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:44.723 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:21.370
Before features/support/hooks.rb:259 0.008
Given a computer 0.247
And I create a 7200 MiB disk named "old" 0.077
And I plug USB drive "old" 1.070
And I write an old version of the Tails USB image to disk "old" 37.282
When I start Tails from USB drive "old" with network unplugged 1:38.655
Then the boot device has safe access rights 2.985
And Tails is running from USB drive "old" 0.370
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.083
And udev-watchdog is monitoring the correct device 0.332
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:305 3.522
After features/support/hooks.rb:89 0.070
Tags: @product
2:9.405
Before features/support/hooks.rb:259 0.007
Given a computer 0.230
And I start Tails from USB drive "old" with network unplugged and I login 1:24.506
Then Tails is running from USB drive "old" 0.368
And I create a persistent partition 32.788
And I take note of which tps features are available 1.944
Then a Tails persistence partition exists on USB drive "old" 1.022
And I shutdown Tails and wait for the computer to power off 8.545
After features/support/hooks.rb:305 0.225
After features/support/hooks.rb:89 0.014
Tags: @product
3:1.249
Before features/support/hooks.rb:259 0.008
Given a computer 0.221
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.285
Then Tails is running from USB drive "old" 0.575
And all tps features are active 2.955
When I write some files expected to persist 1.852
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.246
And all persistence configuration files have safe access rights 0.402
And all persistent directories from the old Tails version have safe access rights 2.788
And I take note of which tps features are available 0.529
And I shutdown Tails and wait for the computer to power off 4.427
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.963
After features/support/hooks.rb:305 0.155
After features/support/hooks.rb:89 0.013
Tags: @product
2:30.244
Before features/support/hooks.rb:259 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 14.625
And I log in to a new session 20.427
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.667
And I plug USB drive "to_upgrade" 2.449
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.710
Then the running Tails is installed on USB drive "to_upgrade" 16.974
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.183
After features/support/hooks.rb:305 4.853
After features/support/hooks.rb:89 0.000
Tags: @product
2:19.236
Before features/support/hooks.rb:259 0.007
Given a computer 0.328
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.185
Then all tps features from the old Tails version are active 1.720
And Tails is running from USB drive "to_upgrade" 0.350
And the boot device has safe access rights 3.259
And the expected persistent files created with the old Tails version are present in the filesystem 2.844
And all persistent directories from the old Tails version have safe access rights 2.547
After features/support/hooks.rb:305 0.878
After features/support/hooks.rb:89 0.012
Tags: @product @automatic_upgrade
6:46.843
Before features/support/hooks.rb:259 0.018
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.456
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.319
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.449
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.458
When the network is plugged 0.076
And Tor is ready 20.421
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.919
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.240
Given I shutdown Tails and wait for the computer to power off 9.088
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.254
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.431
And the file system changes introduced in version 6.2~testoverlayfs are present 0.360
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.433
# 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.278
When the network is plugged 0.033
And Tor is ready 20.531
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.700
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.824
Given I shutdown Tails and wait for the computer to power off 4.506
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.146
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.327
And the file system changes introduced in version 6.3~testoverlayfs are present 0.620
And only the 6.3~testoverlayfs SquashFS delta is installed 0.093
# 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.390
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.364
When the network is plugged 0.055
And Tor is ready 21.105
Then the Upgrader considers the system as up-to-date 0.358
# 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.330
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.006
After features/support/hooks.rb:305 0.780
After features/support/hooks.rb:89 0.020
Tags: @product @automatic_upgrade
36.373
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.828
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.328
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the signing key used by the Upgrader is outdated 1.116
But a current signing key is available on our website 0.000
When the network is plugged 0.039
And Tor is ready 17.867
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.114
After features/support/hooks.rb:305 0.700
After features/support/hooks.rb:89 0.000