Project Number Date
test_Tails_ISO_stable 5217 24 Oct 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:15.212 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:44.202
Before features/support/hooks.rb:269 0.006
Given a computer 0.198
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 40.546
When I start Tails from USB drive "old" with network unplugged 1:57.878
Then the boot device has safe access rights 3.319
And Tails is running from USB drive "old" 0.406
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.311
And I unplug USB drive "old" 0.259
After features/support/hooks.rb:326 3.810
After features/support/hooks.rb:100 0.010
Tags: @product
2:12.873
Before features/support/hooks.rb:269 0.005
Given a computer 0.254
And I start Tails from USB drive "old" with network unplugged and I login 1:26.957
Then Tails is running from USB drive "old" 0.351
And I create a persistent partition 33.712
And I take note of which tps features are available 1.758
Then a Tails persistence partition exists on USB drive "old" 0.886
And I shutdown Tails and wait for the computer to power off 8.953
After features/support/hooks.rb:326 0.208
After features/support/hooks.rb:100 0.009
Tags: @product
3:9.288
Before features/support/hooks.rb:269 0.006
Given a computer 0.267
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:29.256
Then Tails is running from USB drive "old" 0.467
And all tps features are active 2.406
When I write some files expected to persist 2.205
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.260
And all persistence configuration files have safe access rights 0.537
And all persistent directories from the old Tails version have safe access rights 2.426
And I take note of which tps features are available 0.638
And I shutdown Tails and wait for the computer to power off 4.388
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.435
After features/support/hooks.rb:326 0.128
After features/support/hooks.rb:100 0.008
Tags: @product
2:53.660
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 23.574
And I log in to a new session 20.758
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.156
And I plug USB drive "to_upgrade" 2.491
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.644
Then the running Tails is installed on USB drive "to_upgrade" 21.615
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.225
After features/support/hooks.rb:326 4.798
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.963
Before features/support/hooks.rb:269 0.006
Given a computer 0.241
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.139
Then all tps features from the old Tails version are active 3.679
And Tails is running from USB drive "to_upgrade" 0.339
And the boot device has safe access rights 3.529
And the expected persistent files created with the old Tails version are present in the filesystem 1.385
And all persistent directories from the old Tails version have safe access rights 2.649
After features/support/hooks.rb:326 0.912
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:9.962
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 32.778
And no SquashFS delta is installed 0.242
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.333
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.349
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.566
When the network is plugged 0.094
And Tor is ready 23.798
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.588
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.517
Given I shutdown Tails and wait for the computer to power off 12.883
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.961
Then Tails is running version 6.2~testoverlayfs 0.033
And all tps features are active 2.190
And the file system changes introduced in version 6.2~testoverlayfs are present 0.304
And only the 6.2~testoverlayfs SquashFS delta is installed 0.093
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.329
# 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.298
When the network is plugged 0.071
And Tor is ready 17.635
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.843
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.961
Given I shutdown Tails and wait for the computer to power off 4.471
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.915
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.409
And the file system changes introduced in version 6.3~testoverlayfs are present 0.547
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.356
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.335
When the network is plugged 0.138
And Tor is ready 16.712
Then the Upgrader considers the system as up-to-date 10.790
# 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 15.330
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.943
After features/support/hooks.rb:326 0.805
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
40.261
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 11.303
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.473
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the signing key used by the Upgrader is outdated 0.896
But a current signing key is available on our website 0.000
When the network is plugged 0.084
And Tor is ready 21.637
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.795
After features/support/hooks.rb:326 0.738
After features/support/hooks.rb:100 0.000