Project Number Date
test_Tails_ISO_devel 3437 24 Jun 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 21:19.600 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:21.312
Before features/support/hooks.rb:269 0.009
Given a computer 0.424
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.068
And I write an old version of the Tails USB image to disk "old" 36.812
When I start Tails from USB drive "old" with network unplugged 1:38.475
Then the boot device has safe access rights 3.357
And Tails is running from USB drive "old" 0.385
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.322
And I unplug USB drive "old" 0.239
After features/support/hooks.rb:326 7.366
After features/support/hooks.rb:100 0.014
Tags: @product
2:33.374
Before features/support/hooks.rb:269 0.008
Given a computer 0.324
And I start Tails from USB drive "old" with network unplugged and I login 1:41.743
Then Tails is running from USB drive "old" 0.431
And I create a persistent partition 38.004
And I take note of which tps features are available 2.366
Then a Tails persistence partition exists on USB drive "old" 1.001
And I shutdown Tails and wait for the computer to power off 9.503
After features/support/hooks.rb:326 0.170
After features/support/hooks.rb:100 0.010
Tags: @product
3:17.794
Before features/support/hooks.rb:269 0.009
Given a computer 0.341
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:32.327
Then Tails is running from USB drive "old" 0.433
And all tps features are active 3.007
When I write some files expected to persist 1.941
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.293
And all persistence configuration files have safe access rights 0.428
And all persistent directories from the old Tails version have safe access rights 2.670
And I take note of which tps features are available 3.107
And I shutdown Tails and wait for the computer to power off 6.144
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 27.097
After features/support/hooks.rb:326 0.181
After features/support/hooks.rb:100 0.013
Tags: @product
2:52.268
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 22.564
And I log in to a new session 20.972
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.994
And I plug USB drive "to_upgrade" 2.525
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.018
Then the running Tails is installed on USB drive "to_upgrade" 21.408
And I unplug USB drive "to_upgrade" 0.267
And I unplug USB drive "__internal" 0.517
After features/support/hooks.rb:326 2.788
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.479
Before features/support/hooks.rb:269 0.007
Given a computer 2.757
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.807
Then all tps features from the old Tails version are active 4.615
And Tails is running from USB drive "to_upgrade" 0.336
And the boot device has safe access rights 3.757
And the expected persistent files created with the old Tails version are present in the filesystem 1.503
And all persistent directories from the old Tails version have safe access rights 2.701
After features/support/hooks.rb:326 1.260
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:13.556
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 15.682
And no SquashFS delta is installed 0.118
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.423
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.085
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.436
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.555
When the network is plugged 1.311
And Tor is ready 21.528
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.694
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.361
Given I shutdown Tails and wait for the computer to power off 13.195
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.693
Then Tails is running version 6.2~testoverlayfs 0.026
And all tps features are active 2.150
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.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.409
# 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.248
When the network is plugged 0.032
And Tor is ready 45.803
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.558
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.155
Given I shutdown Tails and wait for the computer to power off 4.263
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.119
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.171
And the file system changes introduced in version 6.3~testoverlayfs are present 0.843
And only the 6.3~testoverlayfs SquashFS delta is installed 0.087
# 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.358
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.339
When the network is plugged 0.044
And Tor is ready 19.244
Then the Upgrader considers the system as up-to-date 0.310
# 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.904
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.996
After features/support/hooks.rb:326 0.830
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
36.813
Before features/support/hooks.rb:269 0.029
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.148
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.059
And the signing key used by the Upgrader is outdated 0.980
But a current signing key is available on our website 0.000
When the network is plugged 0.063
And Tor is ready 18.448
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.807
After features/support/hooks.rb:326 0.693
After features/support/hooks.rb:100 0.000