Project Number Date
test_Tails_ISO_devel 3452 09 Jul 2024, 13:16

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:47.793 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:56.019
Before features/support/hooks.rb:269 0.006
Given a computer 0.230
And I create a 7200 MiB disk named "old" 0.062
And I plug USB drive "old" 1.063
And I write an old version of the Tails USB image to disk "old" 32.350
When I start Tails from USB drive "old" with network unplugged 2:17.886
Then the boot device has safe access rights 3.215
And Tails is running from USB drive "old" 0.379
And there is no persistence partition on USB drive "old" 0.101
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.373
And I unplug USB drive "old" 0.251
After features/support/hooks.rb:326 3.586
After features/support/hooks.rb:100 0.012
Tags: @product
2:9.890
Before features/support/hooks.rb:269 0.008
Given a computer 0.239
And I start Tails from USB drive "old" with network unplugged and I login 1:25.879
Then Tails is running from USB drive "old" 0.400
And I create a persistent partition 32.391
And I take note of which tps features are available 1.546
Then a Tails persistence partition exists on USB drive "old" 0.820
And I shutdown Tails and wait for the computer to power off 8.612
After features/support/hooks.rb:326 0.165
After features/support/hooks.rb:100 0.010
Tags: @product
3:0.503
Before features/support/hooks.rb:269 0.008
Given a computer 0.249
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.334
Then Tails is running from USB drive "old" 0.360
And all tps features are active 3.098
When I write some files expected to persist 1.888
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.429
And all persistence configuration files have safe access rights 0.572
And all persistent directories from the old Tails version have safe access rights 2.890
And I take note of which tps features are available 1.004
And I shutdown Tails and wait for the computer to power off 5.130
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.543
After features/support/hooks.rb:326 0.118
After features/support/hooks.rb:100 0.010
Tags: @product
2:28.778
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 12.524
And I log in to a new session 19.939
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.420
And I plug USB drive "to_upgrade" 2.367
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.735
Then the running Tails is installed on USB drive "to_upgrade" 17.223
And I unplug USB drive "to_upgrade" 0.291
And I unplug USB drive "__internal" 0.276
After features/support/hooks.rb:326 6.187
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.355
Before features/support/hooks.rb:269 0.007
Given a computer 0.228
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.525
Then all tps features from the old Tails version are active 2.307
And Tails is running from USB drive "to_upgrade" 0.360
And the boot device has safe access rights 3.384
And the expected persistent files created with the old Tails version are present in the filesystem 1.300
And all persistent directories from the old Tails version have safe access rights 2.248
After features/support/hooks.rb:326 0.799
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:28.149
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 11.380
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.388
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.286
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.430
When the network is plugged 0.035
And Tor is ready 19.741
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.379
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.059
Given I shutdown Tails and wait for the computer to power off 9.096
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.307
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.207
And the file system changes introduced in version 6.2~testoverlayfs are present 0.297
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.330
# 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.231
When the network is plugged 0.041
And Tor is ready 17.377
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.430
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.410
Given I shutdown Tails and wait for the computer to power off 4.324
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.854
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.294
And the file system changes introduced in version 6.3~testoverlayfs are present 0.506
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.330
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.296
When the network is plugged 0.042
And Tor is ready 19.344
Then the Upgrader considers the system as up-to-date 0.320
# 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.115
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.994
After features/support/hooks.rb:326 0.839
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
35.097
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 10.112
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.349
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.837
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 17.275
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.391
After features/support/hooks.rb:326 0.941
After features/support/hooks.rb:100 0.000