Project Number Date
test_Tails_ISO_15451-support-manual-fsck-on-error 20 07 Aug 2024, 18:08

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 23:26.199 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:53.978
Before features/support/hooks.rb:269 0.006
Given a computer 0.910
And I create a 7200 MiB disk named "old" 0.287
And I plug USB drive "old" 1.090
And I write an old version of the Tails USB image to disk "old" 1:15.104
When I start Tails from USB drive "old" with network unplugged 1:31.980
Then the boot device has safe access rights 3.438
And Tails is running from USB drive "old" 0.351
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.137
And udev-watchdog is monitoring the correct device 0.357
And I unplug USB drive "old" 0.248
After features/support/hooks.rb:326 7.349
After features/support/hooks.rb:100 0.009
Tags: @product
2:41.521
Before features/support/hooks.rb:269 0.006
Given a computer 0.271
And I start Tails from USB drive "old" with network unplugged and I login 1:29.123
Then Tails is running from USB drive "old" 0.442
And I create a persistent partition 47.341
And I take note of which tps features are available 10.838
Then a Tails persistence partition exists on USB drive "old" 1.595
And I shutdown Tails and wait for the computer to power off 11.909
After features/support/hooks.rb:326 0.200
After features/support/hooks.rb:100 0.014
Tags: @product
3:20.920
Before features/support/hooks.rb:269 0.008
Given a computer 1.606
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:36.230
Then Tails is running from USB drive "old" 1.154
And all tps features are active 3.332
When I write some files expected to persist 2.590
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.257
And all persistence configuration files have safe access rights 0.415
And all persistent directories from the old Tails version have safe access rights 2.886
And I take note of which tps features are available 0.617
And I shutdown Tails and wait for the computer to power off 6.850
# 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.147
After features/support/hooks.rb:100 0.009
Tags: @product
2:45.007
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 16.768
And I log in to a new session 20.676
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.738
And I plug USB drive "to_upgrade" 2.475
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.613
Then the running Tails is installed on USB drive "to_upgrade" 22.286
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.243
After features/support/hooks.rb:326 3.607
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.148
Before features/support/hooks.rb:269 0.008
Given a computer 0.286
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.486
Then all tps features from the old Tails version are active 1.854
And Tails is running from USB drive "to_upgrade" 0.385
And the boot device has safe access rights 3.631
And the expected persistent files created with the old Tails version are present in the filesystem 1.664
And all persistent directories from the old Tails version have safe access rights 2.839
After features/support/hooks.rb:326 0.748
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
8:46.396
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 22.337
And no SquashFS delta is installed 0.205
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.422
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
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.517
When the network is plugged 0.090
And Tor is ready 22.951
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.447
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.322
Given I shutdown Tails and wait for the computer to power off 1:28.941
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:26.606
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.451
And the file system changes introduced in version 6.2~testoverlayfs are present 0.354
And only the 6.2~testoverlayfs SquashFS delta is installed 0.088
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.356
# 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.322
When the network is plugged 0.088
And Tor is ready 20.027
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.752
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.407
Given I shutdown Tails and wait for the computer to power off 6.466
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:21.213
Then Tails is running version 6.3~testoverlayfs 0.023
And all tps features are active 3.306
And the file system changes introduced in version 6.3~testoverlayfs are present 0.555
And only the 6.3~testoverlayfs SquashFS delta is installed 0.093
# 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.399
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.340
When the network is plugged 0.224
And Tor is ready 19.069
Then the Upgrader considers the system as up-to-date 0.360
# 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.057
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.159
After features/support/hooks.rb:326 0.906
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
35.227
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.118
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.387
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.854
But a current signing key is available on our website 0.000
When the network is plugged 0.095
And Tor is ready 16.223
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.479
After features/support/hooks.rb:326 0.897
After features/support/hooks.rb:100 0.000