Project Number Date
test_Tails_ISO_20668-unblock-20-time.sh 9 26 Nov 2024, 21:04

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:37.124 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:5.409
Before features/support/hooks.rb:269 0.007
Given a computer 0.211
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 33.355
When I start Tails from USB drive "old" with network unplugged 1:26.601
Then the boot device has safe access rights 3.055
And Tails is running from USB drive "old" 0.358
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.348
And I unplug USB drive "old" 0.205
After features/support/hooks.rb:326 3.544
After features/support/hooks.rb:100 0.034
Tags: @product
2:6.512
Before features/support/hooks.rb:269 0.006
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login 1:21.323
Then Tails is running from USB drive "old" 0.321
And I create a persistent partition 33.911
And I take note of which tps features are available 1.569
Then a Tails persistence partition exists on USB drive "old" 0.843
And I shutdown Tails and wait for the computer to power off 8.361
After features/support/hooks.rb:326 0.190
After features/support/hooks.rb:100 0.011
Tags: @product
3:1.670
Before features/support/hooks.rb:269 0.006
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.307
Then Tails is running from USB drive "old" 0.381
And all tps features are active 2.335
When I write some files expected to persist 1.900
# 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.418
And all persistent directories from the old Tails version have safe access rights 2.828
And I take note of which tps features are available 0.430
And I shutdown Tails and wait for the computer to power off 4.416
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.209
After features/support/hooks.rb:326 0.128
After features/support/hooks.rb:100 0.010
Tags: @product
2:38.266
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.971
And I log in to a new session 20.335
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.362
And I plug USB drive "to_upgrade" 2.422
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.815
Then the running Tails is installed on USB drive "to_upgrade" 25.921
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.227
After features/support/hooks.rb:326 3.592
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.535
Before features/support/hooks.rb:269 0.004
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.745
Then all tps features from the old Tails version are active 1.694
And Tails is running from USB drive "to_upgrade" 0.388
And the boot device has safe access rights 3.766
And the expected persistent files created with the old Tails version are present in the filesystem 2.119
And all persistent directories from the old Tails version have safe access rights 2.632
After features/support/hooks.rb:326 0.868
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:42.614
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 14.093
And no SquashFS delta is installed 0.435
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.353
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.356
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.541
When the network is plugged 0.065
And Tor is ready 24.693
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.669
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.292
Given I shutdown Tails and wait for the computer to power off 10.826
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.674
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.019
And the file system changes introduced in version 6.2~testoverlayfs are present 0.387
And only the 6.2~testoverlayfs SquashFS delta is installed 0.114
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.395
# 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.332
When the network is plugged 0.081
And Tor is ready 18.834
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.271
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.129
Given I shutdown Tails and wait for the computer to power off 4.426
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.028
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.202
And the file system changes introduced in version 6.3~testoverlayfs are present 0.487
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.338
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.295
When the network is plugged 0.056
And Tor is ready 18.816
Then the Upgrader considers the system as up-to-date 0.332
# 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.958
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.946
After features/support/hooks.rb:326 0.765
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
40.114
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.686
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.629
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.832
But a current signing key is available on our website 0.000
When the network is plugged 0.096
And Tor is ready 21.173
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.628
After features/support/hooks.rb:326 0.756
After features/support/hooks.rb:100 0.000