Project Number Date
test_Tails_ISO_devel 3441 29 Jun 2024, 12:43

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:58.003 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:11.587
Before features/support/hooks.rb:269 0.007
Given a computer 0.244
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.089
And I write an old version of the Tails USB image to disk "old" 29.991
When I start Tails from USB drive "old" with network unplugged 1:35.908
Then the boot device has safe access rights 3.051
And Tails is running from USB drive "old" 0.440
And there is no persistence partition on USB drive "old" 0.086
And process "udev-watchdog" is running 0.121
And udev-watchdog is monitoring the correct device 0.369
And I unplug USB drive "old" 0.234
After features/support/hooks.rb:326 3.675
After features/support/hooks.rb:100 0.011
Tags: @product
2:3.952
Before features/support/hooks.rb:269 0.008
Given a computer 0.246
And I start Tails from USB drive "old" with network unplugged and I login 1:21.722
Then Tails is running from USB drive "old" 0.335
And I create a persistent partition 30.601
And I take note of which tps features are available 1.835
Then a Tails persistence partition exists on USB drive "old" 0.881
And I shutdown Tails and wait for the computer to power off 8.328
After features/support/hooks.rb:326 0.160
After features/support/hooks.rb:100 0.011
Tags: @product
2:53.955
Before features/support/hooks.rb:269 0.008
Given a computer 0.245
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.080
Then Tails is running from USB drive "old" 0.398
And all tps features are active 2.152
When I write some files expected to persist 1.860
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.256
And all persistence configuration files have safe access rights 0.423
And all persistent directories from the old Tails version have safe access rights 2.388
And I take note of which tps features are available 0.536
And I shutdown Tails and wait for the computer to power off 4.377
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.236
After features/support/hooks.rb:326 0.107
After features/support/hooks.rb:100 0.011
Tags: @product
2:25.232
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 10.963
And I log in to a new session 19.016
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.508
And I plug USB drive "to_upgrade" 2.427
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.344
Then the running Tails is installed on USB drive "to_upgrade" 16.496
And I unplug USB drive "to_upgrade" 0.253
And I unplug USB drive "__internal" 0.221
After features/support/hooks.rb:326 6.789
After features/support/hooks.rb:100 0.000
Tags: @product
2:7.740
Before features/support/hooks.rb:269 0.008
Given a computer 0.254
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:57.650
Then all tps features from the old Tails version are active 1.615
And Tails is running from USB drive "to_upgrade" 0.332
And the boot device has safe access rights 3.917
And the expected persistent files created with the old Tails version are present in the filesystem 1.386
And all persistent directories from the old Tails version have safe access rights 2.583
After features/support/hooks.rb:326 0.734
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
6:39.318
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 10.780
And no SquashFS delta is installed 0.125
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.381
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.290
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.446
When the network is plugged 0.133
And Tor is ready 18.616
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.554
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.778
Given I shutdown Tails and wait for the computer to power off 6.788
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.153
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.099
And the file system changes introduced in version 6.2~testoverlayfs are present 0.417
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# 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.270
When the network is plugged 0.047
And Tor is ready 15.179
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.738
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.565
Given I shutdown Tails and wait for the computer to power off 4.458
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.481
Then Tails is running version 6.3~testoverlayfs 0.024
And all tps features are active 2.240
And the file system changes introduced in version 6.3~testoverlayfs are present 0.457
And only the 6.3~testoverlayfs SquashFS delta is installed 0.089
# 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.316
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.280
When the network is plugged 0.038
And Tor is ready 17.587
Then the Upgrader considers the system as up-to-date 0.352
# 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 16.058
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.091
After features/support/hooks.rb:326 0.953
After features/support/hooks.rb:100 0.035
Tags: @product @automatic_upgrade
36.217
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 12.747
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.351
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.098
And the signing key used by the Upgrader is outdated 0.773
But a current signing key is available on our website 0.000
When the network is plugged 0.389
And Tor is ready 16.625
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.232
After features/support/hooks.rb:326 1.271
After features/support/hooks.rb:100 0.000