Project Number Date
test_Tails_ISO_20666-whisperback-search 12 21 Nov 2024, 14:23

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:59.311 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:26.438
Before features/support/hooks.rb:269 0.008
Given a computer 0.233
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.069
And I write an old version of the Tails USB image to disk "old" 32.713
When I start Tails from USB drive "old" with network unplugged 1:46.951
Then the boot device has safe access rights 4.106
And Tails is running from USB drive "old" 0.479
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.124
And udev-watchdog is monitoring the correct device 0.395
And I unplug USB drive "old" 0.241
After features/support/hooks.rb:326 3.795
After features/support/hooks.rb:100 0.015
Tags: @product
2:19.937
Before features/support/hooks.rb:269 0.009
Given a computer 0.264
And I start Tails from USB drive "old" with network unplugged and I login 1:33.377
Then Tails is running from USB drive "old" 0.387
And I create a persistent partition 33.056
And I take note of which tps features are available 1.916
Then a Tails persistence partition exists on USB drive "old" 1.089
And I shutdown Tails and wait for the computer to power off 9.845
After features/support/hooks.rb:326 0.362
After features/support/hooks.rb:100 0.011
Tags: @product
3:7.906
Before features/support/hooks.rb:269 0.007
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.534
Then Tails is running from USB drive "old" 1.031
And all tps features are active 2.064
When I write some files expected to persist 3.087
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.275
And all persistence configuration files have safe access rights 0.453
And all persistent directories from the old Tails version have safe access rights 2.657
And I take note of which tps features are available 0.445
And I shutdown Tails and wait for the computer to power off 4.744
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.401
After features/support/hooks.rb:326 0.131
After features/support/hooks.rb:100 0.014
Tags: @product
2:53.501
Before features/support/hooks.rb:269 0.011
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.830
And I log in to a new session 23.846
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.852
And I plug USB drive "to_upgrade" 2.430
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.206
Then the running Tails is installed on USB drive "to_upgrade" 26.756
And I unplug USB drive "to_upgrade" 0.293
And I unplug USB drive "__internal" 0.286
After features/support/hooks.rb:326 3.641
After features/support/hooks.rb:100 0.000
Tags: @product
2:38.204
Before features/support/hooks.rb:269 0.012
Given a computer 0.355
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:25.509
Then all tps features from the old Tails version are active 3.696
And Tails is running from USB drive "to_upgrade" 0.359
And the boot device has safe access rights 3.754
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.848
After features/support/hooks.rb:326 1.140
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:54.146
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 17.388
And no SquashFS delta is installed 0.202
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.324
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.399
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.493
When the network is plugged 0.659
And Tor is ready 22.295
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.758
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.342
Given I shutdown Tails and wait for the computer to power off 8.938
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.305
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 2.661
And the file system changes introduced in version 6.2~testoverlayfs are present 0.400
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.353
# 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.455
When the network is plugged 0.116
And Tor is ready 17.365
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.456
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.964
Given I shutdown Tails and wait for the computer to power off 4.568
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.437
Then Tails is running version 6.3~testoverlayfs 0.025
And all tps features are active 2.109
And the file system changes introduced in version 6.3~testoverlayfs are present 0.529
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.346
When the network is plugged 0.069
And Tor is ready 19.194
Then the Upgrader considers the system as up-to-date 0.304
# 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.035
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.075
After features/support/hooks.rb:326 1.001
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
39.176
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.183
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.074
And the signing key used by the Upgrader is outdated 0.931
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 19.484
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.082
After features/support/hooks.rb:326 1.484
After features/support/hooks.rb:100 0.000