Project Number Date
test_Tails_ISO_devel 3463 15 Jul 2024, 12:49

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 21:27.742 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
3:29.821
Before features/support/hooks.rb:269 0.009
Given a computer 0.305
And I create a 7200 MiB disk named "old" 0.078
And I plug USB drive "old" 1.084
And I write an old version of the Tails USB image to disk "old" 1:21.136
When I start Tails from USB drive "old" with network unplugged 2:2.870
Then the boot device has safe access rights 3.199
And Tails is running from USB drive "old" 0.386
And there is no persistence partition on USB drive "old" 0.096
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.351
And I unplug USB drive "old" 0.208
After features/support/hooks.rb:326 6.911
After features/support/hooks.rb:100 0.014
Tags: @product
2:37.133
Before features/support/hooks.rb:269 0.008
Given a computer 0.526
And I start Tails from USB drive "old" with network unplugged and I login 1:21.570
Then Tails is running from USB drive "old" 0.290
And I create a persistent partition 45.880
And I take note of which tps features are available 17.064
Then a Tails persistence partition exists on USB drive "old" 1.112
And I shutdown Tails and wait for the computer to power off 10.687
After features/support/hooks.rb:326 0.182
After features/support/hooks.rb:100 0.012
Tags: @product
3:5.448
Before features/support/hooks.rb:269 0.008
Given a computer 1.765
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.062
Then Tails is running from USB drive "old" 0.407
And all tps features are active 2.359
When I write some files expected to persist 1.938
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.243
And all persistence configuration files have safe access rights 0.411
And all persistent directories from the old Tails version have safe access rights 2.696
And I take note of which tps features are available 0.604
And I shutdown Tails and wait for the computer to power off 4.486
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.471
After features/support/hooks.rb:326 0.158
After features/support/hooks.rb:100 0.013
Tags: @product
2:59.944
Before features/support/hooks.rb:269 0.013
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 26.191
And I log in to a new session 19.824
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.579
And I plug USB drive "to_upgrade" 2.422
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:46.679
Then the running Tails is installed on USB drive "to_upgrade" 22.753
And I unplug USB drive "to_upgrade" 0.245
And I unplug USB drive "__internal" 0.248
After features/support/hooks.rb:326 2.081
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.378
Before features/support/hooks.rb:269 0.006
Given a computer 0.222
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.833
Then all tps features from the old Tails version are active 1.590
And Tails is running from USB drive "to_upgrade" 0.290
And the boot device has safe access rights 3.346
And the expected persistent files created with the old Tails version are present in the filesystem 1.597
And all persistent directories from the old Tails version have safe access rights 2.496
After features/support/hooks.rb:326 0.640
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:26.992
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 10.162
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.273
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.320
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.483
When the network is plugged 0.047
And Tor is ready 22.148
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.564
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.143
Given I shutdown Tails and wait for the computer to power off 8.682
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.093
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.405
And the file system changes introduced in version 6.2~testoverlayfs are present 0.335
And only the 6.2~testoverlayfs SquashFS delta is installed 0.086
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.359
# 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.417
When the network is plugged 0.054
And Tor is ready 16.940
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.662
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.885
Given I shutdown Tails and wait for the computer to power off 4.346
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.864
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.182
And the file system changes introduced in version 6.3~testoverlayfs are present 0.546
And only the 6.3~testoverlayfs SquashFS delta is installed 0.084
# 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.360
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.341
When the network is plugged 0.072
And Tor is ready 17.886
Then the Upgrader considers the system as up-to-date 0.370
# 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.703
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.010
After features/support/hooks.rb:326 0.743
After features/support/hooks.rb:100 0.027
Tags: @product @automatic_upgrade
38.023
Before features/support/hooks.rb:269 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.403
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.449
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 1.278
But a current signing key is available on our website 0.000
When the network is plugged 0.252
And Tor is ready 20.383
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.208
After features/support/hooks.rb:326 1.237
After features/support/hooks.rb:100 0.000