Project Number Date
test_Tails_ISO_20666-whisperback-search 11 21 Nov 2024, 00:27

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.435 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:11.806
Before features/support/hooks.rb:269 0.006
Given a computer 0.194
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 31.300
When I start Tails from USB drive "old" with network unplugged 1:34.683
Then the boot device has safe access rights 3.399
And Tails is running from USB drive "old" 0.354
And there is no persistence partition on USB drive "old" 0.087
And process "udev-watchdog" is running 0.125
And udev-watchdog is monitoring the correct device 0.351
And I unplug USB drive "old" 0.207
After features/support/hooks.rb:326 3.827
After features/support/hooks.rb:100 0.009
Tags: @product
2:14.142
Before features/support/hooks.rb:269 0.004
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login 1:27.161
Then Tails is running from USB drive "old" 0.354
And I create a persistent partition 34.583
And I take note of which tps features are available 2.696
Then a Tails persistence partition exists on USB drive "old" 0.822
And I shutdown Tails and wait for the computer to power off 8.327
After features/support/hooks.rb:326 0.154
After features/support/hooks.rb:100 0.008
Tags: @product
3:0.254
Before features/support/hooks.rb:269 0.004
Given a computer 1.168
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.047
Then Tails is running from USB drive "old" 0.360
And all tps features are active 2.169
When I write some files expected to persist 2.047
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.261
And all persistence configuration files have safe access rights 0.408
And all persistent directories from the old Tails version have safe access rights 2.545
And I take note of which tps features are available 0.473
And I shutdown Tails and wait for the computer to power off 4.257
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.514
After features/support/hooks.rb:326 0.153
After features/support/hooks.rb:100 0.007
Tags: @product
2:32.329
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.395
And I log in to a new session 20.619
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.736
And I plug USB drive "to_upgrade" 2.453
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.375
Then the running Tails is installed on USB drive "to_upgrade" 19.192
And I unplug USB drive "to_upgrade" 0.248
And I unplug USB drive "__internal" 0.306
After features/support/hooks.rb:326 7.333
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.352
Before features/support/hooks.rb:269 0.010
Given a computer 0.227
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.435
Then all tps features from the old Tails version are active 1.751
And Tails is running from USB drive "to_upgrade" 0.315
And the boot device has safe access rights 3.600
And the expected persistent files created with the old Tails version are present in the filesystem 1.434
And all persistent directories from the old Tails version have safe access rights 2.586
After features/support/hooks.rb:326 0.680
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:35.774
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.483
And no SquashFS delta is installed 0.131
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.380
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.093
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.337
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.507
When the network is plugged 0.569
And Tor is ready 22.443
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.784
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.474
Given I shutdown Tails and wait for the computer to power off 11.340
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.203
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.115
And the file system changes introduced in version 6.2~testoverlayfs are present 0.375
And only the 6.2~testoverlayfs SquashFS delta is installed 0.118
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.491
# 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.355
When the network is plugged 0.075
And Tor is ready 18.602
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.761
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.949
Given I shutdown Tails and wait for the computer to power off 4.238
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.742
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.090
And the file system changes introduced in version 6.3~testoverlayfs are present 0.515
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.347
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.270
When the network is plugged 0.110
And Tor is ready 19.955
Then the Upgrader considers the system as up-to-date 0.357
# 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.303
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.137
After features/support/hooks.rb:326 0.714
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
44.775
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 9.849
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.437
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the signing key used by the Upgrader is outdated 1.354
But a current signing key is available on our website 0.000
When the network is plugged 0.089
And Tor is ready 32.284
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.687
After features/support/hooks.rb:326 0.855
After features/support/hooks.rb:100 0.000