Project Number Date
test_Tails_ISO_20666-whisperback-search 10 20 Nov 2024, 13:35

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 18:39.673 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:3.886
Before features/support/hooks.rb:269 0.005
Given a computer 0.164
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 30.551
When I start Tails from USB drive "old" with network unplugged 1:28.247
Then the boot device has safe access rights 2.861
And Tails is running from USB drive "old" 0.318
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.288
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:326 7.063
After features/support/hooks.rb:100 0.009
Tags: @product
2:4.158
Before features/support/hooks.rb:269 0.006
Given a computer 0.169
And I start Tails from USB drive "old" with network unplugged and I login 1:21.846
Then Tails is running from USB drive "old" 0.313
And I create a persistent partition 31.027
And I take note of which tps features are available 1.526
Then a Tails persistence partition exists on USB drive "old" 0.855
And I shutdown Tails and wait for the computer to power off 8.416
After features/support/hooks.rb:326 0.182
After features/support/hooks.rb:100 0.009
Tags: @product
2:54.137
Before features/support/hooks.rb:269 0.005
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.985
Then Tails is running from USB drive "old" 0.366
And all tps features are active 1.879
When I write some files expected to persist 1.870
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.216
And all persistence configuration files have safe access rights 0.371
And all persistent directories from the old Tails version have safe access rights 2.282
And I take note of which tps features are available 0.399
And I shutdown Tails and wait for the computer to power off 6.353
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.234
After features/support/hooks.rb:326 0.129
After features/support/hooks.rb:100 0.009
Tags: @product
2:29.006
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 10.780
And I log in to a new session 18.760
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.000
And I plug USB drive "to_upgrade" 2.404
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.970
Then the running Tails is installed on USB drive "to_upgrade" 19.702
And I unplug USB drive "to_upgrade" 0.186
And I unplug USB drive "__internal" 0.200
After features/support/hooks.rb:326 2.424
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.666
Before features/support/hooks.rb:269 0.006
Given a computer 0.168
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.740
Then all tps features from the old Tails version are active 1.508
And Tails is running from USB drive "to_upgrade" 0.300
And the boot device has safe access rights 3.092
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.348
After features/support/hooks.rb:326 0.621
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:11.714
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.267
And no SquashFS delta is installed 0.152
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.337
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.329
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.426
When the network is plugged 0.059
And Tor is ready 21.945
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.342
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.003
Given I shutdown Tails and wait for the computer to power off 8.497
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.702
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.110
And the file system changes introduced in version 6.2~testoverlayfs are present 0.269
And only the 6.2~testoverlayfs SquashFS delta is installed 0.092
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.317
# 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.274
When the network is plugged 0.060
And Tor is ready 18.059
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.427
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.387
Given I shutdown Tails and wait for the computer to power off 4.675
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.979
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.165
And the file system changes introduced in version 6.3~testoverlayfs are present 0.510
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.424
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.360
When the network is plugged 0.060
And Tor is ready 15.439
Then the Upgrader considers the system as up-to-date 0.319
# 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.576
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.993
After features/support/hooks.rb:326 0.704
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
38.104
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.677
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.363
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.920
But a current signing key is available on our website 0.000
When the network is plugged 0.061
And Tor is ready 19.348
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.672
After features/support/hooks.rb:326 1.128
After features/support/hooks.rb:100 0.000