Project Number Date
test_Tails_ISO_20635-greeter-threading-fixes 33 18 Nov 2024, 19:48

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 20:8.821 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:17.139
Before features/support/hooks.rb:269 0.007
Given a computer 0.226
And I create a 7200 MiB disk named "old" 0.064
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 32.212
When I start Tails from USB drive "old" with network unplugged 1:39.197
Then the boot device has safe access rights 3.275
And Tails is running from USB drive "old" 0.387
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.109
And udev-watchdog is monitoring the correct device 0.314
And I unplug USB drive "old" 0.218
After features/support/hooks.rb:326 3.741
After features/support/hooks.rb:100 0.011
Tags: @product
2:10.846
Before features/support/hooks.rb:269 0.004
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login 1:27.193
Then Tails is running from USB drive "old" 0.353
And I create a persistent partition 32.143
And I take note of which tps features are available 1.708
Then a Tails persistence partition exists on USB drive "old" 0.874
And I shutdown Tails and wait for the computer to power off 8.376
After features/support/hooks.rb:326 0.152
After features/support/hooks.rb:100 0.008
Tags: @product
3:8.079
Before features/support/hooks.rb:269 0.005
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:28.570
Then Tails is running from USB drive "old" 0.354
And all tps features are active 2.547
When I write some files expected to persist 1.794
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.271
And all persistence configuration files have safe access rights 0.451
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 0.538
And I shutdown Tails and wait for the computer to power off 4.429
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.270
After features/support/hooks.rb:326 0.127
After features/support/hooks.rb:100 0.007
Tags: @product
2:42.146
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.932
And I log in to a new session 22.679
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.100
And I plug USB drive "to_upgrade" 2.476
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.267
Then the running Tails is installed on USB drive "to_upgrade" 25.177
And I unplug USB drive "to_upgrade" 0.232
And I unplug USB drive "__internal" 0.279
After features/support/hooks.rb:326 6.681
After features/support/hooks.rb:100 0.000
Tags: @product
2:33.271
Before features/support/hooks.rb:269 0.005
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:22.839
Then all tps features from the old Tails version are active 2.017
And Tails is running from USB drive "to_upgrade" 0.371
And the boot device has safe access rights 3.560
And the expected persistent files created with the old Tails version are present in the filesystem 1.679
And all persistent directories from the old Tails version have safe access rights 2.610
After features/support/hooks.rb:326 1.016
After features/support/hooks.rb:100 0.008
6:37.205
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.951
And no SquashFS delta is installed 0.113
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.383
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.328
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.496
When the network is plugged 0.069
And Tor is ready 21.556
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.814
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.615
Given I shutdown Tails and wait for the computer to power off 10.925
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.588
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.467
And the file system changes introduced in version 6.2~testoverlayfs are present 0.328
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.331
# 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.336
When the network is plugged 0.465
And Tor is ready 19.048
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.621
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.861
Given I shutdown Tails and wait for the computer to power off 4.517
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.969
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 2.893
And the file system changes introduced in version 6.3~testoverlayfs are present 0.509
And only the 6.3~testoverlayfs SquashFS delta is installed 0.091
# 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.563
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.441
When the network is plugged 0.063
And Tor is ready 19.129
Then the Upgrader considers the system as up-to-date 0.369
# 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.084
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.096
After features/support/hooks.rb:326 0.777
After features/support/hooks.rb:100 0.061
40.132
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.100
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.395
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.117
And the signing key used by the Upgrader is outdated 0.830
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 19.618
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.997
After features/support/hooks.rb:326 0.737
After features/support/hooks.rb:100 0.000