Project Number Date
test_Tails_ISO_devel 3358 20 Apr 2024, 16:44

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:14.234 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:6.288
Before features/support/hooks.rb:259 0.007
Given a computer 0.218
And I create a 7200 MiB disk named "old" 0.192
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 29.585
When I start Tails from USB drive "old" with network unplugged 1:31.056
Then the boot device has safe access rights 3.137
And Tails is running from USB drive "old" 0.362
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.085
And udev-watchdog is monitoring the correct device 0.339
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:305 7.520
After features/support/hooks.rb:89 0.009
Tags: @product
2:9.241
Before features/support/hooks.rb:259 0.006
Given a computer 0.270
And I start Tails from USB drive "old" with network unplugged and I login 1:21.655
Then Tails is running from USB drive "old" 0.295
And I create a persistent partition 35.771
And I take note of which tps features are available 1.561
Then a Tails persistence partition exists on USB drive "old" 0.815
And I shutdown Tails and wait for the computer to power off 8.870
After features/support/hooks.rb:305 0.321
After features/support/hooks.rb:89 0.011
Tags: @product
2:44.784
Before features/support/hooks.rb:259 0.006
Given a computer 0.614
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:6.996
Then Tails is running from USB drive "old" 0.344
And all tps features are active 1.977
When I write some files expected to persist 1.617
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.243
And all persistence configuration files have safe access rights 0.359
And all persistent directories from the old Tails version have safe access rights 3.011
And I take note of which tps features are available 0.431
And I shutdown Tails and wait for the computer to power off 4.519
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.666
After features/support/hooks.rb:305 0.145
After features/support/hooks.rb:89 0.011
Tags: @product
2:41.906
Before features/support/hooks.rb:259 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 14.849
And I log in to a new session 25.275
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.717
And I plug USB drive "to_upgrade" 2.615
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.887
Then the running Tails is installed on USB drive "to_upgrade" 22.180
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.177
After features/support/hooks.rb:305 2.482
After features/support/hooks.rb:89 0.000
Tags: @product
2:18.864
Before features/support/hooks.rb:259 0.005
Given a computer 0.187
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.066
Then all tps features from the old Tails version are active 1.683
And Tails is running from USB drive "to_upgrade" 0.340
And the boot device has safe access rights 3.663
And the expected persistent files created with the old Tails version are present in the filesystem 1.464
And all persistent directories from the old Tails version have safe access rights 2.457
After features/support/hooks.rb:305 0.670
After features/support/hooks.rb:89 0.013
Tags: @product @automatic_upgrade
6:34.232
Before features/support/hooks.rb:259 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.923
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.523
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.081
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.323
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.492
When the network is plugged 0.323
And Tor is ready 17.248
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.868
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 15.333
Given I shutdown Tails and wait for the computer to power off 11.447
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.079
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.529
And the file system changes introduced in version 6.2~testoverlayfs are present 0.376
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.337
# 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.047
And Tor is ready 19.460
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.220
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.119
Given I shutdown Tails and wait for the computer to power off 4.500
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.898
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.119
And the file system changes introduced in version 6.3~testoverlayfs are present 0.481
And only the 6.3~testoverlayfs SquashFS delta is installed 0.085
# 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.493
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.279
When the network is plugged 0.033
And Tor is ready 16.936
Then the Upgrader considers the system as up-to-date 10.810
# 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.490
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.840
After features/support/hooks.rb:305 0.834
After features/support/hooks.rb:89 0.018
Tags: @product @automatic_upgrade
38.917
Before features/support/hooks.rb:259 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.632
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.453
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.081
And the signing key used by the Upgrader is outdated 0.673
But a current signing key is available on our website 0.000
When the network is plugged 0.207
And Tor is ready 19.101
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.766
After features/support/hooks.rb:305 1.029
After features/support/hooks.rb:89 0.000