Project Number Date
test_Tails_ISO_devel 3573 01 Nov 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 20:10.615 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:12.019
Before features/support/hooks.rb:269 0.006
Given a computer 0.201
And I create a 7200 MiB disk named "old" 0.089
And I plug USB drive "old" 1.085
And I write an old version of the Tails USB image to disk "old" 35.137
When I start Tails from USB drive "old" with network unplugged 1:30.662
Then the boot device has safe access rights 3.653
And Tails is running from USB drive "old" 0.395
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.374
And I unplug USB drive "old" 0.237
After features/support/hooks.rb:326 7.303
After features/support/hooks.rb:100 0.014
Tags: @product
2:9.124
Before features/support/hooks.rb:269 0.012
Given a computer 0.232
And I start Tails from USB drive "old" with network unplugged and I login 1:26.486
Then Tails is running from USB drive "old" 0.387
And I create a persistent partition 32.828
And I take note of which tps features are available 1.463
Then a Tails persistence partition exists on USB drive "old" 0.885
And I shutdown Tails and wait for the computer to power off 6.841
After features/support/hooks.rb:326 0.206
After features/support/hooks.rb:100 0.012
Tags: @product
3:0.444
Before features/support/hooks.rb:269 0.007
Given a computer 0.245
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.777
Then Tails is running from USB drive "old" 0.411
And all tps features are active 2.113
When I write some files expected to persist 2.187
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.240
And all persistence configuration files have safe access rights 0.461
And all persistent directories from the old Tails version have safe access rights 2.827
And I take note of which tps features are available 0.952
And I shutdown Tails and wait for the computer to power off 4.891
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 27.335
After features/support/hooks.rb:326 0.169
After features/support/hooks.rb:100 0.012
Tags: @product
2:45.152
Before features/support/hooks.rb:269 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 13.488
And I log in to a new session 22.777
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.981
And I plug USB drive "to_upgrade" 2.581
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.238
Then the running Tails is installed on USB drive "to_upgrade" 25.654
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.223
After features/support/hooks.rb:326 2.079
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.889
Before features/support/hooks.rb:269 0.004
Given a computer 0.273
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.307
Then all tps features from the old Tails version are active 1.828
And Tails is running from USB drive "to_upgrade" 0.409
And the boot device has safe access rights 3.600
And the expected persistent files created with the old Tails version are present in the filesystem 1.654
And all persistent directories from the old Tails version have safe access rights 2.815
After features/support/hooks.rb:326 0.663
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:59.656
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 12.861
And no SquashFS delta is installed 0.104
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.390
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.081
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.331
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.680
When the network is plugged 0.088
And Tor is ready 19.866
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.402
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.284
Given I shutdown Tails and wait for the computer to power off 13.256
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.693
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.457
And the file system changes introduced in version 6.2~testoverlayfs are present 0.330
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.353
# 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.333
When the network is plugged 0.081
And Tor is ready 48.253
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.769
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.292
Given I shutdown Tails and wait for the computer to power off 4.249
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.758
Then Tails is running version 6.3~testoverlayfs 0.043
And all tps features are active 2.341
And the file system changes introduced in version 6.3~testoverlayfs are present 0.570
And only the 6.3~testoverlayfs SquashFS delta is installed 0.122
# 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.345
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.315
When the network is plugged 0.080
And Tor is ready 22.529
Then the Upgrader considers the system as up-to-date 0.368
# 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.933
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.988
After features/support/hooks.rb:326 0.718
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
38.327
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.671
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.060
And the signing key used by the Upgrader is outdated 1.219
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 17.510
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.438
After features/support/hooks.rb:326 0.858
After features/support/hooks.rb:100 0.000