Project Number Date
test_Tails_ISO_devel 3417 05 Jun 2024, 20:20

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 21:50.326 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:52.261
Before features/support/hooks.rb:269 0.006
Given a computer 0.345
And I create a 7200 MiB disk named "old" 0.071
And I plug USB drive "old" 1.062
And I write an old version of the Tails USB image to disk "old" 58.503
When I start Tails from USB drive "old" with network unplugged 1:47.896
Then the boot device has safe access rights 3.204
And Tails is running from USB drive "old" 0.419
And there is no persistence partition on USB drive "old" 0.088
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.358
And I unplug USB drive "old" 0.204
After features/support/hooks.rb:315 3.868
After features/support/hooks.rb:100 0.011
Tags: @product
2:17.749
Before features/support/hooks.rb:269 0.007
Given a computer 0.379
And I start Tails from USB drive "old" with network unplugged and I login 1:25.000
Then Tails is running from USB drive "old" 0.381
And I create a persistent partition 40.387
And I take note of which tps features are available 1.895
Then a Tails persistence partition exists on USB drive "old" 0.854
And I shutdown Tails and wait for the computer to power off 8.849
After features/support/hooks.rb:315 0.184
After features/support/hooks.rb:100 0.009
Tags: @product
2:58.762
Before features/support/hooks.rb:269 0.005
Given a computer 2.011
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.400
Then Tails is running from USB drive "old" 0.376
And all tps features are active 2.344
When I write some files expected to persist 1.909
# 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.402
And all persistent directories from the old Tails version have safe access rights 2.980
And I take note of which tps features are available 0.544
And I shutdown Tails and wait for the computer to power off 4.485
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.068
After features/support/hooks.rb:315 0.100
After features/support/hooks.rb:100 0.011
Tags: @product
3:7.989
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 37.678
And I log in to a new session 22.694
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.140
And I plug USB drive "to_upgrade" 2.441
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.956
Then the running Tails is installed on USB drive "to_upgrade" 20.631
And I unplug USB drive "to_upgrade" 0.227
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:315 1.843
After features/support/hooks.rb:100 0.000
Tags: @product
2:31.523
Before features/support/hooks.rb:269 0.009
Given a computer 0.308
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:21.059
Then all tps features from the old Tails version are active 2.013
And Tails is running from USB drive "to_upgrade" 0.327
And the boot device has safe access rights 3.580
And the expected persistent files created with the old Tails version are present in the filesystem 1.561
And all persistent directories from the old Tails version have safe access rights 2.671
After features/support/hooks.rb:315 0.852
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
7:21.864
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 18.822
And no SquashFS delta is installed 0.322
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.401
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.095
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.303
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.539
When the network is plugged 0.054
And Tor is ready 28.044
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.434
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 18.423
Given I shutdown Tails and wait for the computer to power off 8.913
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.613
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 11.893
And the file system changes introduced in version 6.2~testoverlayfs are present 0.332
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.355
# 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.317
When the network is plugged 0.159
And Tor is ready 16.852
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.268
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.829
Given I shutdown Tails and wait for the computer to power off 7.100
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.697
Then Tails is running version 6.3~testoverlayfs 0.115
And all tps features are active 2.964
And the file system changes introduced in version 6.3~testoverlayfs are present 0.477
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.349
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.276
When the network is plugged 0.058
And Tor is ready 20.396
Then the Upgrader considers the system as up-to-date 0.308
# 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.868
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.125
After features/support/hooks.rb:315 0.967
After features/support/hooks.rb:100 0.039
Tags: @product @automatic_upgrade
40.176
Before features/support/hooks.rb:269 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.763
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.403
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.111
And the signing key used by the Upgrader is outdated 1.096
But a current signing key is available on our website 0.000
When the network is plugged 0.066
And Tor is ready 19.984
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.750
After features/support/hooks.rb:315 0.984
After features/support/hooks.rb:100 0.000