Project Number Date
test_Tails_ISO_devel 3319 13 Mar 2024, 12:43

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:31.326 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:53.764
Before features/support/hooks.rb:245 0.007
Given a computer 0.222
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 22.871
When I start Tails from USB drive "old" with network unplugged 1:25.403
Then the boot device has safe access rights 3.149
And Tails is running from USB drive "old" 0.359
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.289
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:291 6.781
After features/support/hooks.rb:75 0.013
Tags: @product
2:12.318
Before features/support/hooks.rb:245 0.009
Given a computer 0.285
And I start Tails from USB drive "old" with network unplugged and I login 1:18.427
Then Tails is running from USB drive "old" 0.379
And I create a persistent partition 42.313
And I take note of which tps features are available 2.076
Then a Tails persistence partition exists on USB drive "old" 0.746
And I shutdown Tails and wait for the computer to power off 8.088
After features/support/hooks.rb:291 0.191
After features/support/hooks.rb:75 0.010
Tags: @product
2:40.745
Before features/support/hooks.rb:245 0.005
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.094
Then Tails is running from USB drive "old" 0.392
And all tps features are active 1.940
When I write some files expected to persist 1.638
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.278
And all persistence configuration files have safe access rights 0.397
And all persistent directories from the old Tails version have safe access rights 2.601
And I take note of which tps features are available 0.416
And I shutdown Tails and wait for the computer to power off 4.087
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.701
After features/support/hooks.rb:291 0.231
After features/support/hooks.rb:75 0.017
Tags: @product
2:39.987
Before features/support/hooks.rb:245 0.012
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.226
And I log in to a new session 17.814
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.641
And I plug USB drive "to_upgrade" 2.472
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.761
Then the running Tails is installed on USB drive "to_upgrade" 21.643
And I unplug USB drive "to_upgrade" 0.228
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:291 1.912
After features/support/hooks.rb:75 0.000
Tags: @product
2:30.495
Before features/support/hooks.rb:245 0.007
Given a computer 0.210
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:21.027
Then all tps features from the old Tails version are active 1.515
And Tails is running from USB drive "to_upgrade" 0.355
And the boot device has safe access rights 3.202
And the expected persistent files created with the old Tails version are present in the filesystem 1.412
And all persistent directories from the old Tails version have safe access rights 2.771
After features/support/hooks.rb:291 0.650
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
6:58.927
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 24.192
And no SquashFS delta is installed 0.119
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.296
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.286
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.454
When the network is plugged 0.051
And Tor is ready 19.756
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.911
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.564
Given I shutdown Tails and wait for the computer to power off 7.033
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.642
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 2.033
And the file system changes introduced in version 6.2~testoverlayfs are present 0.281
And only the 6.2~testoverlayfs SquashFS delta is installed 0.101
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.316
# 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.355
When the network is plugged 0.042
And Tor is ready 18.929
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.617
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.454
Given I shutdown Tails and wait for the computer to power off 5.041
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.683
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 1.942
And the file system changes introduced in version 6.3~testoverlayfs are present 0.450
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.306
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.258
When the network is plugged 0.058
And Tor is ready 17.830
Then the Upgrader considers the system as up-to-date 0.238
# 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.604
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.885
After features/support/hooks.rb:291 0.874
After features/support/hooks.rb:75 0.023
Tags: @product @automatic_upgrade
35.087
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.059
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.340
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the signing key used by the Upgrader is outdated 0.671
But a current signing key is available on our website 0.000
When the network is plugged 0.042
And Tor is ready 17.780
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.119
After features/support/hooks.rb:291 0.874
After features/support/hooks.rb:75 0.000