Project Number Date
test_Tails_ISO_devel 3477 13 Aug 2024, 12:47

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:20.239 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:26.874
Before features/support/hooks.rb:269 0.006
Given a computer 0.181
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 30.680
When I start Tails from USB drive "old" with network unplugged 1:50.434
Then the boot device has safe access rights 3.343
And Tails is running from USB drive "old" 0.368
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.350
And I unplug USB drive "old" 0.231
After features/support/hooks.rb:326 7.209
After features/support/hooks.rb:100 0.012
Tags: @product
2:15.569
Before features/support/hooks.rb:269 0.007
Given a computer 0.216
And I start Tails from USB drive "old" with network unplugged and I login 1:31.864
Then Tails is running from USB drive "old" 0.342
And I create a persistent partition 32.194
And I take note of which tps features are available 1.587
Then a Tails persistence partition exists on USB drive "old" 0.858
And I shutdown Tails and wait for the computer to power off 8.506
After features/support/hooks.rb:326 0.191
After features/support/hooks.rb:100 0.009
Tags: @product
2:52.867
Before features/support/hooks.rb:269 0.005
Given a computer 0.279
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.276
Then Tails is running from USB drive "old" 0.310
And all tps features are active 1.926
When I write some files expected to persist 1.657
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.218
And all persistence configuration files have safe access rights 0.385
And all persistent directories from the old Tails version have safe access rights 2.814
And I take note of which tps features are available 0.878
And I shutdown Tails and wait for the computer to power off 4.450
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.668
After features/support/hooks.rb:326 0.162
After features/support/hooks.rb:100 0.010
Tags: @product
2:23.838
Before features/support/hooks.rb:269 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 10.906
And I log in to a new session 19.096
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.676
And I plug USB drive "to_upgrade" 2.389
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.203
Then the running Tails is installed on USB drive "to_upgrade" 16.156
And I unplug USB drive "to_upgrade" 0.193
And I unplug USB drive "__internal" 0.215
After features/support/hooks.rb:326 4.563
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.448
Before features/support/hooks.rb:269 0.005
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.609
Then all tps features from the old Tails version are active 1.627
And Tails is running from USB drive "to_upgrade" 0.372
And the boot device has safe access rights 3.617
And the expected persistent files created with the old Tails version are present in the filesystem 1.526
And all persistent directories from the old Tails version have safe access rights 2.496
After features/support/hooks.rb:326 1.101
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
8:27.353
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.423
And no SquashFS delta is installed 0.126
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.328
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.328
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.501
When the network is plugged 0.071
And Tor is ready 19.100
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.871
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.956
Given I shutdown Tails and wait for the computer to power off 1:29.430
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.471
Then Tails is running version 6.2~testoverlayfs 0.029
And all tps features are active 2.873
And the file system changes introduced in version 6.2~testoverlayfs are present 0.345
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.392
# 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.372
When the network is plugged 0.094
And Tor is ready 20.377
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.901
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.795
Given I shutdown Tails and wait for the computer to power off 6.747
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:21.251
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.114
And the file system changes introduced in version 6.3~testoverlayfs are present 0.612
And only the 6.3~testoverlayfs SquashFS delta is installed 0.108
# 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.343
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.298
When the network is plugged 0.070
And Tor is ready 17.451
Then the Upgrader considers the system as up-to-date 10.915
# 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.525
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.972
After features/support/hooks.rb:326 0.819
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
38.286
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 10.144
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.352
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.103
And the signing key used by the Upgrader is outdated 0.904
But a current signing key is available on our website 0.000
When the network is plugged 0.065
And Tor is ready 20.108
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.607
After features/support/hooks.rb:326 0.728
After features/support/hooks.rb:100 0.000