Project Number Date
test_Tails_ISO_20668-unblock-20-time.sh 4 21 Nov 2024, 20:53

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:14.107 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:13.565
Before features/support/hooks.rb:269 0.003
Given a computer 0.193
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.065
And I write an old version of the Tails USB image to disk "old" 30.275
When I start Tails from USB drive "old" with network unplugged 1:37.151
Then the boot device has safe access rights 3.639
And Tails is running from USB drive "old" 0.406
And there is no persistence partition on USB drive "old" 0.096
And process "udev-watchdog" is running 0.112
And udev-watchdog is monitoring the correct device 0.356
And I unplug USB drive "old" 0.223
After features/support/hooks.rb:326 3.540
After features/support/hooks.rb:100 0.009
Tags: @product
2:18.074
Before features/support/hooks.rb:269 0.005
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login 1:33.306
Then Tails is running from USB drive "old" 0.320
And I create a persistent partition 32.734
And I take note of which tps features are available 1.664
Then a Tails persistence partition exists on USB drive "old" 0.903
And I shutdown Tails and wait for the computer to power off 8.949
After features/support/hooks.rb:326 0.190
After features/support/hooks.rb:100 0.008
Tags: @product
2:58.121
Before features/support/hooks.rb:269 0.005
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.949
Then Tails is running from USB drive "old" 1.323
And all tps features are active 2.137
When I write some files expected to persist 2.680
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.582
And all persistence configuration files have safe access rights 0.521
And all persistent directories from the old Tails version have safe access rights 3.678
And I take note of which tps features are available 0.454
And I shutdown Tails and wait for the computer to power off 4.439
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.145
After features/support/hooks.rb:326 0.146
After features/support/hooks.rb:100 0.044
Tags: @product
2:38.939
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.342
And I log in to a new session 25.391
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.755
And I plug USB drive "to_upgrade" 2.480
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.591
Then the running Tails is installed on USB drive "to_upgrade" 21.941
And I unplug USB drive "to_upgrade" 0.231
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:326 7.526
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.005
Before features/support/hooks.rb:269 0.005
Given a computer 0.199
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.896
Then all tps features from the old Tails version are active 1.961
And Tails is running from USB drive "to_upgrade" 0.394
And the boot device has safe access rights 3.301
And the expected persistent files created with the old Tails version are present in the filesystem 1.508
And all persistent directories from the old Tails version have safe access rights 2.745
After features/support/hooks.rb:326 0.711
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
7:2.878
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 12.982
And no SquashFS delta is installed 0.125
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.339
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.331
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.645
When the network is plugged 0.088
And Tor is ready 21.175
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.258
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.747
Given I shutdown Tails and wait for the computer to power off 10.896
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.362
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 3.180
And the file system changes introduced in version 6.2~testoverlayfs are present 0.458
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.352
# 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.333
When the network is plugged 0.089
And Tor is ready 49.142
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.569
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.844
Given I shutdown Tails and wait for the computer to power off 6.653
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.596
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.409
And the file system changes introduced in version 6.3~testoverlayfs are present 0.527
And only the 6.3~testoverlayfs SquashFS delta is installed 0.086
# 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.560
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.425
When the network is plugged 0.081
And Tor is ready 18.833
Then the Upgrader considers the system as up-to-date 0.334
# 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.105
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.155
After features/support/hooks.rb:326 0.757
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
39.522
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 11.758
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.355
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.815
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 19.203
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.250
After features/support/hooks.rb:326 0.815
After features/support/hooks.rb:100 0.000