Project Number Date
test_Tails_ISO_stable 4920 08 Jul 2024, 15:59

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:25.758 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.372
Before features/support/hooks.rb:269 0.007
Given a computer 0.258
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.062
And I write an old version of the Tails USB image to disk "old" 29.536
When I start Tails from USB drive "old" with network unplugged 1:36.390
Then the boot device has safe access rights 3.062
And Tails is running from USB drive "old" 0.341
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.336
And I unplug USB drive "old" 0.176
After features/support/hooks.rb:326 3.542
After features/support/hooks.rb:100 0.010
Tags: @product
2:6.516
Before features/support/hooks.rb:269 0.007
Given a computer 0.252
And I start Tails from USB drive "old" with network unplugged and I login 1:25.041
Then Tails is running from USB drive "old" 0.289
And I create a persistent partition 29.621
And I take note of which tps features are available 1.602
Then a Tails persistence partition exists on USB drive "old" 0.909
And I shutdown Tails and wait for the computer to power off 8.800
After features/support/hooks.rb:326 0.247
After features/support/hooks.rb:100 0.014
Tags: @product
3:0.076
Before features/support/hooks.rb:269 0.006
Given a computer 0.259
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.751
Then Tails is running from USB drive "old" 0.384
And all tps features are active 2.195
When I write some files expected to persist 1.698
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.253
And all persistence configuration files have safe access rights 0.461
And all persistent directories from the old Tails version have safe access rights 2.471
And I take note of which tps features are available 0.457
And I shutdown Tails and wait for the computer to power off 4.254
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.888
After features/support/hooks.rb:326 0.131
After features/support/hooks.rb:100 0.024
Tags: @product
2:27.298
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.787
And I log in to a new session 19.756
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.439
And I plug USB drive "to_upgrade" 2.374
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.103
Then the running Tails is installed on USB drive "to_upgrade" 18.422
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:326 6.677
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.012
Before features/support/hooks.rb:269 0.009
Given a computer 0.227
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.124
Then all tps features from the old Tails version are active 1.728
And Tails is running from USB drive "to_upgrade" 0.303
And the boot device has safe access rights 3.597
And the expected persistent files created with the old Tails version are present in the filesystem 1.425
And all persistent directories from the old Tails version have safe access rights 2.605
After features/support/hooks.rb:326 0.649
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:44.001
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 11.742
And no SquashFS delta is installed 0.201
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.431
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.370
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.554
When the network is plugged 0.049
And Tor is ready 19.933
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.898
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 15.890
Given I shutdown Tails and wait for the computer to power off 9.276
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.006
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.241
And the file system changes introduced in version 6.2~testoverlayfs are present 0.271
And only the 6.2~testoverlayfs SquashFS delta is installed 0.129
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.420
# 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.310
When the network is plugged 0.038
And Tor is ready 17.589
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.253
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.782
Given I shutdown Tails and wait for the computer to power off 4.592
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.612
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.345
And the file system changes introduced in version 6.3~testoverlayfs are present 0.572
And only the 6.3~testoverlayfs SquashFS delta is installed 0.087
# 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.363
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.355
When the network is plugged 0.048
And Tor is ready 16.851
Then the Upgrader considers the system as up-to-date 10.823
# 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.864
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.996
After features/support/hooks.rb:326 0.616
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
34.479
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.848
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.318
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.086
And the signing key used by the Upgrader is outdated 0.859
But a current signing key is available on our website 0.000
When the network is plugged 0.050
And Tor is ready 15.878
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.438
After features/support/hooks.rb:326 1.894
After features/support/hooks.rb:100 0.000