Project Number Date
test_Tails_ISO_devel 3406 30 May 2024, 19:34

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:31.937 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:0.019
Before features/support/hooks.rb:259 0.008
Given a computer 0.171
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.083
And I write an old version of the Tails USB image to disk "old" 29.923
When I start Tails from USB drive "old" with network unplugged 1:24.803
Then the boot device has safe access rights 2.947
And Tails is running from USB drive "old" 0.330
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.317
And I unplug USB drive "old" 0.245
After features/support/hooks.rb:305 3.519
After features/support/hooks.rb:89 0.061
Tags: @product
2:5.590
Before features/support/hooks.rb:259 0.006
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login 1:19.840
Then Tails is running from USB drive "old" 0.313
And I create a persistent partition 34.446
And I take note of which tps features are available 1.509
Then a Tails persistence partition exists on USB drive "old" 0.843
And I shutdown Tails and wait for the computer to power off 8.461
After features/support/hooks.rb:305 0.210
After features/support/hooks.rb:89 0.012
Tags: @product
2:52.083
Before features/support/hooks.rb:259 0.007
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.941
Then Tails is running from USB drive "old" 0.311
And all tps features are active 1.969
When I write some files expected to persist 1.850
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.413
And all persistence configuration files have safe access rights 0.465
And all persistent directories from the old Tails version have safe access rights 2.494
And I take note of which tps features are available 0.386
And I shutdown Tails and wait for the computer to power off 4.518
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.547
After features/support/hooks.rb:305 0.145
After features/support/hooks.rb:89 0.012
Tags: @product
2:24.817
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.611
And I log in to a new session 19.128
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.779
And I plug USB drive "to_upgrade" 2.429
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.127
Then the running Tails is installed on USB drive "to_upgrade" 15.274
And I unplug USB drive "to_upgrade" 0.220
And I unplug USB drive "__internal" 0.246
After features/support/hooks.rb:305 2.782
After features/support/hooks.rb:89 0.000
Tags: @product
2:10.629
Before features/support/hooks.rb:259 0.007
Given a computer 0.525
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.706
Then all tps features from the old Tails version are active 1.516
And Tails is running from USB drive "to_upgrade" 0.363
And the boot device has safe access rights 3.290
And the expected persistent files created with the old Tails version are present in the filesystem 1.625
And all persistent directories from the old Tails version have safe access rights 2.602
After features/support/hooks.rb:305 0.610
After features/support/hooks.rb:89 0.009
Tags: @product @automatic_upgrade
6:20.735
Before features/support/hooks.rb:259 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.544
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.355
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.274
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.455
When the network is plugged 0.055
And Tor is ready 20.350
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.611
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.555
Given I shutdown Tails and wait for the computer to power off 8.737
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.712
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.181
And the file system changes introduced in version 6.2~testoverlayfs are present 0.306
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.335
# 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.266
When the network is plugged 0.048
And Tor is ready 15.796
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.706
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.540
Given I shutdown Tails and wait for the computer to power off 4.349
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.429
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.117
And the file system changes introduced in version 6.3~testoverlayfs are present 0.598
And only the 6.3~testoverlayfs SquashFS delta is installed 0.083
# 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.354
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.280
When the network is plugged 0.039
And Tor is ready 18.829
Then the Upgrader considers the system as up-to-date 0.299
# 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.466
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.826
After features/support/hooks.rb:305 0.798
After features/support/hooks.rb:89 0.019
Tags: @product @automatic_upgrade
38.061
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 9.738
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.314
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.085
And the signing key used by the Upgrader is outdated 1.916
But a current signing key is available on our website 0.000
When the network is plugged 0.030
And Tor is ready 18.731
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.243
After features/support/hooks.rb:305 0.699
After features/support/hooks.rb:89 0.000