Project Number Date
test_Tails_ISO_devel 3525 30 Sep 2024, 12:47

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:47.778 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
1:56.301
Before features/support/hooks.rb:269 0.006
Given a computer 0.191
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 30.196
When I start Tails from USB drive "old" with network unplugged 1:20.811
Then the boot device has safe access rights 3.022
And Tails is running from USB drive "old" 0.333
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.295
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:326 6.968
After features/support/hooks.rb:100 0.007
Tags: @product
2:2.982
Before features/support/hooks.rb:269 0.003
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login 1:22.600
Then Tails is running from USB drive "old" 0.358
And I create a persistent partition 29.193
And I take note of which tps features are available 1.668
Then a Tails persistence partition exists on USB drive "old" 0.743
And I shutdown Tails and wait for the computer to power off 8.234
After features/support/hooks.rb:326 0.123
After features/support/hooks.rb:100 0.009
Tags: @product
2:55.624
Before features/support/hooks.rb:269 0.005
Given a computer 0.240
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.176
Then Tails is running from USB drive "old" 0.339
And all tps features are active 2.018
When I write some files expected to persist 1.762
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.239
And all persistence configuration files have safe access rights 0.388
And all persistent directories from the old Tails version have safe access rights 2.278
And I take note of which tps features are available 0.460
And I shutdown Tails and wait for the computer to power off 4.308
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.411
After features/support/hooks.rb:326 0.132
After features/support/hooks.rb:100 0.009
Tags: @product
2:34.881
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 11.533
And I log in to a new session 22.907
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.552
And I plug USB drive "to_upgrade" 2.478
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.820
Then the running Tails is installed on USB drive "to_upgrade" 23.178
And I unplug USB drive "to_upgrade" 0.214
And I unplug USB drive "__internal" 0.194
After features/support/hooks.rb:326 2.322
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.022
Before features/support/hooks.rb:269 0.008
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.999
Then all tps features from the old Tails version are active 1.582
And Tails is running from USB drive "to_upgrade" 0.301
And the boot device has safe access rights 3.012
And the expected persistent files created with the old Tails version are present in the filesystem 1.707
And all persistent directories from the old Tails version have safe access rights 2.225
After features/support/hooks.rb:326 0.808
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:17.253
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.390
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.301
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.278
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.440
When the network is plugged 0.074
And Tor is ready 18.446
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.253
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.174
Given I shutdown Tails and wait for the computer to power off 8.418
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.610
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.100
And the file system changes introduced in version 6.2~testoverlayfs are present 0.320
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.272
# 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.272
When the network is plugged 0.094
And Tor is ready 15.314
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.531
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.766
Given I shutdown Tails and wait for the computer to power off 4.290
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.101
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.221
And the file system changes introduced in version 6.3~testoverlayfs are present 0.459
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.323
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.304
When the network is plugged 0.077
And Tor is ready 18.846
Then the Upgrader considers the system as up-to-date 0.317
# 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 12.971
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.956
After features/support/hooks.rb:326 0.758
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
49.710
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 23.150
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.305
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the signing key used by the Upgrader is outdated 0.822
But a current signing key is available on our website 0.000
When the network is plugged 0.065
And Tor is ready 18.805
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.481
After features/support/hooks.rb:326 0.800
After features/support/hooks.rb:100 0.000