Project Number Date
test_Tails_ISO_devel 3342 29 Mar 2024, 12:13

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 17:41.096 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
1:39.063
Before features/support/hooks.rb:245 0.008
Given a computer 0.217
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 20.949
When I start Tails from USB drive "old" with network unplugged 1:12.499
Then the boot device has safe access rights 3.221
And Tails is running from USB drive "old" 0.366
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.320
And I unplug USB drive "old" 0.214
After features/support/hooks.rb:291 3.783
After features/support/hooks.rb:75 0.014
Tags: @product
2:11.787
Before features/support/hooks.rb:245 0.008
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login 1:25.499
Then Tails is running from USB drive "old" 0.331
And I create a persistent partition 34.412
And I take note of which tps features are available 1.709
Then a Tails persistence partition exists on USB drive "old" 0.744
And I shutdown Tails and wait for the computer to power off 8.865
After features/support/hooks.rb:291 0.240
After features/support/hooks.rb:75 0.012
Tags: @product
2:35.723
Before features/support/hooks.rb:245 0.006
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:5.682
Then Tails is running from USB drive "old" 0.391
And all tps features are active 1.956
When I write some files expected to persist 2.009
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.237
And all persistence configuration files have safe access rights 0.422
And all persistent directories from the old Tails version have safe access rights 2.842
And I take note of which tps features are available 0.463
And I shutdown Tails and wait for the computer to power off 4.518
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.997
After features/support/hooks.rb:291 0.150
After features/support/hooks.rb:75 0.011
Tags: @product
2:31.386
Before features/support/hooks.rb:245 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 16.698
And I log in to a new session 18.785
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.604
And I plug USB drive "to_upgrade" 2.453
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.070
Then the running Tails is installed on USB drive "to_upgrade" 18.384
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.175
After features/support/hooks.rb:291 2.358
After features/support/hooks.rb:75 0.000
Tags: @product
2:5.571
Before features/support/hooks.rb:245 0.008
Given a computer 0.202
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:56.298
Then all tps features from the old Tails version are active 1.685
And Tails is running from USB drive "to_upgrade" 0.342
And the boot device has safe access rights 2.940
And the expected persistent files created with the old Tails version are present in the filesystem 1.762
And all persistent directories from the old Tails version have safe access rights 2.340
After features/support/hooks.rb:291 0.531
After features/support/hooks.rb:75 0.012
Tags: @product @automatic_upgrade
6:2.416
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.521
And no SquashFS delta is installed 0.211
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.322
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.335
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.780
When the network is plugged 0.389
And Tor is ready 20.733
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.129
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.537
Given I shutdown Tails and wait for the computer to power off 6.826
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.382
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.166
And the file system changes introduced in version 6.2~testoverlayfs are present 0.299
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.348
# 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.232
When the network is plugged 0.048
And Tor is ready 15.829
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.488
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.509
Given I shutdown Tails and wait for the computer to power off 4.334
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.043
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.788
And the file system changes introduced in version 6.3~testoverlayfs are present 0.482
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.288
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.287
When the network is plugged 0.100
And Tor is ready 17.663
Then the Upgrader considers the system as up-to-date 0.250
# 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 13.986
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.876
After features/support/hooks.rb:291 0.747
After features/support/hooks.rb:75 0.022
Tags: @product @automatic_upgrade
35.147
Before features/support/hooks.rb:245 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.470
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.395
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.420
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 17.839
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.923
After features/support/hooks.rb:291 0.688
After features/support/hooks.rb:75 0.000