Project Number Date
test_Tails_ISO_stable 4708 11 Mar 2024, 16:41

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:46.567 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:31.810
Before features/support/hooks.rb:245 0.004
Given a computer 0.181
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 19.355
When I start Tails from USB drive "old" with network unplugged 1:6.871
Then the boot device has safe access rights 3.184
And Tails is running from USB drive "old" 0.367
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.365
And I unplug USB drive "old" 0.223
After features/support/hooks.rb:291 3.569
After features/support/hooks.rb:75 0.030
Tags: @product
2:12.700
Before features/support/hooks.rb:245 0.010
Given a computer 0.222
And I start Tails from USB drive "old" with network unplugged and I login 1:18.348
Then Tails is running from USB drive "old" 0.278
And I create a persistent partition 43.078
And I take note of which tps features are available 2.093
Then a Tails persistence partition exists on USB drive "old" 0.657
And I shutdown Tails and wait for the computer to power off 8.022
After features/support/hooks.rb:291 0.162
After features/support/hooks.rb:75 0.008
Tags: @product
2:45.581
Before features/support/hooks.rb:245 0.004
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.615
Then Tails is running from USB drive "old" 0.342
And all tps features are active 1.921
When I write some files expected to persist 1.702
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.218
And all persistence configuration files have safe access rights 0.373
And all persistent directories from the old Tails version have safe access rights 2.462
And I take note of which tps features are available 0.454
And I shutdown Tails and wait for the computer to power off 4.023
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.261
After features/support/hooks.rb:291 0.216
After features/support/hooks.rb:75 0.009
Tags: @product
2:47.106
Before features/support/hooks.rb:245 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 24.626
And I log in to a new session 16.804
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.476
And I plug USB drive "to_upgrade" 2.455
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.110
Then the running Tails is installed on USB drive "to_upgrade" 14.246
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.183
After features/support/hooks.rb:291 3.547
After features/support/hooks.rb:75 0.000
Tags: @product
2:22.500
Before features/support/hooks.rb:245 0.005
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.451
Then all tps features from the old Tails version are active 1.515
And Tails is running from USB drive "to_upgrade" 0.319
And the boot device has safe access rights 3.150
And the expected persistent files created with the old Tails version are present in the filesystem 1.466
And all persistent directories from the old Tails version have safe access rights 2.398
After features/support/hooks.rb:291 0.687
After features/support/hooks.rb:75 0.012
Tags: @product @automatic_upgrade
6:34.237
Before features/support/hooks.rb:245 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.694
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.315
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.266
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.458
When the network is plugged 0.131
And Tor is ready 16.774
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.542
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.470
Given I shutdown Tails and wait for the computer to power off 7.084
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.977
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.043
And the file system changes introduced in version 6.2~testoverlayfs are present 0.298
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.307
# 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.287
When the network is plugged 0.064
And Tor is ready 18.810
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.296
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.363
Given I shutdown Tails and wait for the computer to power off 4.026
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.864
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.038
And the file system changes introduced in version 6.3~testoverlayfs are present 0.474
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.283
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.294
When the network is plugged 0.033
And Tor is ready 16.287
Then the Upgrader considers the system as up-to-date 0.260
# 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 13.296
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.875
After features/support/hooks.rb:291 0.782
After features/support/hooks.rb:75 0.017
Tags: @product @automatic_upgrade
32.631
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.312
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.290
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.503
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 16.337
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.095
After features/support/hooks.rb:291 0.675
After features/support/hooks.rb:75 0.000