Project Number Date
test_Tails_ISO_devel 3551 17 Oct 2024, 12:54

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:13.313 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:6.624
Before features/support/hooks.rb:269 0.007
Given a computer 0.224
And I create a 7200 MiB disk named "old" 0.060
And I plug USB drive "old" 1.062
And I write an old version of the Tails USB image to disk "old" 29.616
When I start Tails from USB drive "old" with network unplugged 1:31.621
Then the boot device has safe access rights 3.013
And Tails is running from USB drive "old" 0.343
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.324
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:326 7.043
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.793
Before features/support/hooks.rb:269 0.006
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login 1:22.209
Then Tails is running from USB drive "old" 0.329
And I create a persistent partition 33.552
And I take note of which tps features are available 1.529
Then a Tails persistence partition exists on USB drive "old" 0.803
And I shutdown Tails and wait for the computer to power off 8.174
After features/support/hooks.rb:326 0.172
After features/support/hooks.rb:100 0.009
Tags: @product
2:57.068
Before features/support/hooks.rb:269 0.006
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.045
Then Tails is running from USB drive "old" 0.929
And all tps features are active 2.375
When I write some files expected to persist 2.612
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.275
And all persistence configuration files have safe access rights 0.478
And all persistent directories from the old Tails version have safe access rights 2.733
And I take note of which tps features are available 0.475
And I shutdown Tails and wait for the computer to power off 4.369
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.555
After features/support/hooks.rb:326 0.118
After features/support/hooks.rb:100 0.010
Tags: @product
2:35.023
Before features/support/hooks.rb:269 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.386
And I log in to a new session 22.242
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.546
And I plug USB drive "to_upgrade" 2.535
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.459
Then the running Tails is installed on USB drive "to_upgrade" 22.411
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.234
After features/support/hooks.rb:326 2.604
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.036
Before features/support/hooks.rb:269 0.007
Given a computer 0.194
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.358
Then all tps features from the old Tails version are active 1.739
And Tails is running from USB drive "to_upgrade" 0.350
And the boot device has safe access rights 3.638
And the expected persistent files created with the old Tails version are present in the filesystem 1.359
And all persistent directories from the old Tails version have safe access rights 2.396
After features/support/hooks.rb:326 0.792
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:39.196
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 20.576
And no SquashFS delta is installed 0.131
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.778
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.100
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.285
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.460
When the network is plugged 0.084
And Tor is ready 19.910
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.127
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.921
Given I shutdown Tails and wait for the computer to power off 11.364
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.028
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.213
And the file system changes introduced in version 6.2~testoverlayfs are present 0.305
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.312
# 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.376
When the network is plugged 0.082
And Tor is ready 20.758
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.399
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.719
Given I shutdown Tails and wait for the computer to power off 4.301
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.188
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.152
And the file system changes introduced in version 6.3~testoverlayfs are present 0.549
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.412
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.281
When the network is plugged 0.069
And Tor is ready 16.698
Then the Upgrader considers the system as up-to-date 0.314
# 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.065
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.038
After features/support/hooks.rb:326 0.920
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
37.570
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.033
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.361
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.080
And the signing key used by the Upgrader is outdated 0.932
But a current signing key is available on our website 0.000
When the network is plugged 0.093
And Tor is ready 21.032
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.036
After features/support/hooks.rb:326 0.733
After features/support/hooks.rb:100 0.000