Project Number Date
test_Tails_ISO_20666-whisperback-search 14 21 Nov 2024, 17:02

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:41.088 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:6.971
Before features/support/hooks.rb:269 0.005
Given a computer 0.161
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 31.931
When I start Tails from USB drive "old" with network unplugged 1:29.436
Then the boot device has safe access rights 3.332
And Tails is running from USB drive "old" 0.349
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.313
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:326 3.599
After features/support/hooks.rb:100 0.009
Tags: @product
2:9.836
Before features/support/hooks.rb:269 0.005
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login 1:25.814
Then Tails is running from USB drive "old" 0.358
And I create a persistent partition 31.938
And I take note of which tps features are available 2.003
Then a Tails persistence partition exists on USB drive "old" 0.932
And I shutdown Tails and wait for the computer to power off 8.613
After features/support/hooks.rb:326 0.206
After features/support/hooks.rb:100 0.009
Tags: @product
3:7.574
Before features/support/hooks.rb:269 0.006
Given a computer 0.215
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.347
Then Tails is running from USB drive "old" 1.900
And all tps features are active 2.218
When I write some files expected to persist 5.731
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.260
And all persistence configuration files have safe access rights 0.459
And all persistent directories from the old Tails version have safe access rights 3.363
And I take note of which tps features are available 0.439
And I shutdown Tails and wait for the computer to power off 4.403
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.232
After features/support/hooks.rb:326 0.127
After features/support/hooks.rb:100 0.008
Tags: @product
2:36.091
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.696
And I log in to a new session 20.603
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.201
And I plug USB drive "to_upgrade" 2.621
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.321
Then the running Tails is installed on USB drive "to_upgrade" 21.199
And I unplug USB drive "to_upgrade" 0.199
And I unplug USB drive "__internal" 0.248
After features/support/hooks.rb:326 1.128
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.381
Before features/support/hooks.rb:269 0.006
Given a computer 0.196
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.446
Then all tps features from the old Tails version are active 1.745
And Tails is running from USB drive "to_upgrade" 0.359
And the boot device has safe access rights 3.508
And the expected persistent files created with the old Tails version are present in the filesystem 1.524
And all persistent directories from the old Tails version have safe access rights 2.599
After features/support/hooks.rb:326 0.983
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:34.962
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.689
And no SquashFS delta is installed 0.123
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.369
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.353
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.455
When the network is plugged 0.075
And Tor is ready 23.811
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.409
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.783
Given I shutdown Tails and wait for the computer to power off 8.845
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.170
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 2.330
And the file system changes introduced in version 6.2~testoverlayfs are present 0.416
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.397
# 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.331
When the network is plugged 0.064
And Tor is ready 19.058
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.192
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.344
Given I shutdown Tails and wait for the computer to power off 4.500
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.552
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 2.044
And the file system changes introduced in version 6.3~testoverlayfs are present 0.504
And only the 6.3~testoverlayfs SquashFS delta is installed 0.104
# 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.404
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.458
When the network is plugged 0.408
And Tor is ready 17.222
Then the Upgrader considers the system as up-to-date 10.854
# 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 16.425
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.040
After features/support/hooks.rb:326 0.897
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
43.272
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 10.750
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.315
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.096
And the signing key used by the Upgrader is outdated 1.070
But a current signing key is available on our website 0.000
When the network is plugged 0.273
And Tor is ready 23.956
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.808
After features/support/hooks.rb:326 0.726
After features/support/hooks.rb:100 0.000