Project Number Date
test_Tails_ISO_devel 3282 14 Feb 2024, 20:45

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 88 0 0 0 0 88 7 0 7 22:51.983 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:10.676
Before features/support/hooks.rb:245 0.004
Given a computer 0.198
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.064
And I write an old version of the Tails USB image to disk "old" 50.009
When I start Tails from USB drive "old" with network unplugged 1:15.378
Then the boot device has safe access rights 3.068
And Tails is running from USB drive "old" 0.303
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.078
And udev-watchdog is monitoring the correct device 0.283
And I unplug USB drive "old" 0.174
After features/support/hooks.rb:291 0.915
After features/support/hooks.rb:75 0.010
Tags: @product
2:13.624
Before features/support/hooks.rb:245 0.006
Given a computer 0.273
And I start Tails from USB drive "old" with network unplugged and I login 1:20.155
Then Tails is running from USB drive "old" 0.355
And I create a persistent partition 42.046
And I take note of which tps features are available 1.840
Then a Tails persistence partition exists on USB drive "old" 0.860
And I shutdown Tails and wait for the computer to power off 8.092
After features/support/hooks.rb:291 0.168
After features/support/hooks.rb:75 0.009
Tags: @product
3:36.950
Before features/support/hooks.rb:245 0.007
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:4.458
Then Tails is running from USB drive "old" 0.405
And all tps features are active 2.531
When I write some files expected to persist 1.924
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.384
And all persistence configuration files have safe access rights 0.627
And all persistent directories from the old Tails version have safe access rights 2.864
And I take note of which tps features are available 0.825
And I shutdown Tails and wait for the computer to power off 5.251
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.469
After features/support/hooks.rb:291 0.164
After features/support/hooks.rb:75 0.012
Tags: @product
2:41.591
Before features/support/hooks.rb:245 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 12.597
And I log in to a new session 20.662
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.451
And I plug USB drive "to_upgrade" 2.417
And I cancel the GNOME authentication prompt 2.067
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.095
Then the running Tails is installed on USB drive "to_upgrade" 18.904
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.184
After features/support/hooks.rb:291 1.802
After features/support/hooks.rb:75 0.000
Tags: @product
3:3.731
Before features/support/hooks.rb:245 0.008
Given a computer 0.206
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:53.398
Then all tps features from the old Tails version are active 1.679
And Tails is running from USB drive "to_upgrade" 0.359
And the boot device has safe access rights 3.869
And the expected persistent files created with the old Tails version are present in the filesystem 1.545
And all persistent directories from the old Tails version have safe access rights 2.671
After features/support/hooks.rb:291 0.800
After features/support/hooks.rb:75 0.012
Tags: @product @automatic_upgrade
8:6.138
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.785
And no SquashFS delta is installed 0.097
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.375
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.322
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.511
When the network is plugged 0.119
And Tor is ready 20.136
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.157
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.253
Given I shutdown Tails and wait for the computer to power off 7.511
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:47.989
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.124
And the file system changes introduced in version 6.2~testoverlayfs are present 0.337
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.307
# 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.328
When the network is plugged 0.049
And Tor is ready 21.167
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.440
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.300
Given I shutdown Tails and wait for the computer to power off 5.424
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:48.197
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.879
And the file system changes introduced in version 6.3~testoverlayfs are present 0.488
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.332
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.250
When the network is plugged 0.052
And Tor is ready 17.072
Then the Upgrader considers the system as up-to-date 10.727
# 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.236
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.926
After features/support/hooks.rb:291 0.728
After features/support/hooks.rb:75 0.025
Tags: @product @automatic_upgrade
59.271
Before features/support/hooks.rb:245 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.596
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.069
And the signing key used by the Upgrader is outdated 0.516
But a current signing key is available on our website 0.000
When the network is plugged 0.259
And Tor is ready 46.850
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.529
After features/support/hooks.rb:291 0.664
After features/support/hooks.rb:75 0.000