Project Number Date
test_Tails_ISO_20635-greeter-threading-fixes 32 17 Nov 2024, 19:56

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:53.796 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:20.731
Before features/support/hooks.rb:269 0.004
Given a computer 0.192
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 34.277
When I start Tails from USB drive "old" with network unplugged 1:40.327
Then the boot device has safe access rights 3.700
And Tails is running from USB drive "old" 0.392
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.109
And udev-watchdog is monitoring the correct device 0.353
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:326 3.579
After features/support/hooks.rb:100 0.009
Tags: @product
2:12.056
Before features/support/hooks.rb:269 0.007
Given a computer 0.215
And I start Tails from USB drive "old" with network unplugged and I login 1:28.589
Then Tails is running from USB drive "old" 0.320
And I create a persistent partition 31.961
And I take note of which tps features are available 1.607
Then a Tails persistence partition exists on USB drive "old" 0.910
And I shutdown Tails and wait for the computer to power off 8.451
After features/support/hooks.rb:326 0.215
After features/support/hooks.rb:100 0.007
Tags: @product
2:54.033
Before features/support/hooks.rb:269 0.004
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.830
Then Tails is running from USB drive "old" 0.911
And all tps features are active 1.972
When I write some files expected to persist 1.914
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.211
And all persistence configuration files have safe access rights 1.651
And all persistent directories from the old Tails version have safe access rights 2.505
And I take note of which tps features are available 0.487
And I shutdown Tails and wait for the computer to power off 4.376
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.979
After features/support/hooks.rb:326 0.124
After features/support/hooks.rb:100 0.014
Tags: @product
2:37.303
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 12.443
And I log in to a new session 22.071
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.941
And I plug USB drive "to_upgrade" 2.586
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.317
Then the running Tails is installed on USB drive "to_upgrade" 20.504
And I unplug USB drive "to_upgrade" 0.226
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:326 3.258
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.676
Before features/support/hooks.rb:269 0.006
Given a computer 0.222
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.108
Then all tps features from the old Tails version are active 1.907
And Tails is running from USB drive "to_upgrade" 0.421
And the boot device has safe access rights 3.786
And the expected persistent files created with the old Tails version are present in the filesystem 1.516
And all persistent directories from the old Tails version have safe access rights 2.714
After features/support/hooks.rb:326 0.875
After features/support/hooks.rb:100 0.010
6:51.964
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 12.714
And no SquashFS delta is installed 0.103
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.327
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.367
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.430
When the network is plugged 0.080
And Tor is ready 22.028
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.267
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.204
Given I shutdown Tails and wait for the computer to power off 11.032
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:23.330
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.523
And the file system changes introduced in version 6.2~testoverlayfs are present 0.353
And only the 6.2~testoverlayfs SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.364
# 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.333
When the network is plugged 0.093
And Tor is ready 21.050
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.033
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.618
Given I shutdown Tails and wait for the computer to power off 4.392
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.102
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.069
And the file system changes introduced in version 6.3~testoverlayfs are present 0.499
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.333
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.249
When the network is plugged 0.071
And Tor is ready 18.418
Then the Upgrader considers the system as up-to-date 0.300
# 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 14.961
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.044
After features/support/hooks.rb:326 0.766
After features/support/hooks.rb:100 0.015
36.030
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 10.180
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.320
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.082
And the signing key used by the Upgrader is outdated 0.904
But a current signing key is available on our website 0.000
When the network is plugged 0.084
And Tor is ready 17.497
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.960
After features/support/hooks.rb:326 0.720
After features/support/hooks.rb:100 0.000