Project Number Date
test_Tails_ISO_stable 5007 07 Aug 2024, 18:55

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 20:21.791 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:29.243
Before features/support/hooks.rb:269 0.007
Given a computer 0.224
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 31.510
When I start Tails from USB drive "old" with network unplugged 1:51.992
Then the boot device has safe access rights 3.366
And Tails is running from USB drive "old" 0.331
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.316
And I unplug USB drive "old" 0.214
After features/support/hooks.rb:326 3.526
After features/support/hooks.rb:100 0.012
Tags: @product
2:17.130
Before features/support/hooks.rb:269 0.009
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login 1:32.594
Then Tails is running from USB drive "old" 0.388
And I create a persistent partition 32.367
And I take note of which tps features are available 2.009
Then a Tails persistence partition exists on USB drive "old" 0.824
And I shutdown Tails and wait for the computer to power off 8.749
After features/support/hooks.rb:326 0.267
After features/support/hooks.rb:100 0.009
Tags: @product
2:58.595
Before features/support/hooks.rb:269 0.007
Given a computer 0.264
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.698
Then Tails is running from USB drive "old" 0.390
And all tps features are active 2.311
When I write some files expected to persist 1.965
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.276
And all persistence configuration files have safe access rights 0.499
And all persistent directories from the old Tails version have safe access rights 3.331
And I take note of which tps features are available 0.588
And I shutdown Tails and wait for the computer to power off 4.403
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.867
After features/support/hooks.rb:326 0.142
After features/support/hooks.rb:100 0.011
Tags: @product
2:36.877
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.835
And I log in to a new session 20.652
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.619
And I plug USB drive "to_upgrade" 2.406
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.696
Then the running Tails is installed on USB drive "to_upgrade" 19.234
And I unplug USB drive "to_upgrade" 0.215
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:326 3.788
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.258
Before features/support/hooks.rb:269 0.010
Given a computer 0.248
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.287
Then all tps features from the old Tails version are active 1.809
And Tails is running from USB drive "to_upgrade" 0.342
And the boot device has safe access rights 3.415
And the expected persistent files created with the old Tails version are present in the filesystem 1.566
And all persistent directories from the old Tails version have safe access rights 2.587
After features/support/hooks.rb:326 0.671
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
7:2.489
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.387
And no SquashFS delta is installed 0.218
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.377
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.161
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.296
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.517
When the network is plugged 0.097
And Tor is ready 21.627
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.154
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 16.174
Given I shutdown Tails and wait for the computer to power off 11.127
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.265
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.431
And the file system changes introduced in version 6.2~testoverlayfs are present 0.360
And only the 6.2~testoverlayfs SquashFS delta is installed 0.091
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.387
# 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.312
When the network is plugged 0.082
And Tor is ready 16.129
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.045
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.938
Given I shutdown Tails and wait for the computer to power off 4.539
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.826
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.278
And the file system changes introduced in version 6.3~testoverlayfs are present 0.542
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.340
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.322
When the network is plugged 0.083
And Tor is ready 17.052
Then the Upgrader considers the system as up-to-date 10.918
# 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.244
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.047
After features/support/hooks.rb:326 0.843
After features/support/hooks.rb:100 0.030
Tags: @product @automatic_upgrade
36.196
Before features/support/hooks.rb:269 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.805
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.409
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the signing key used by the Upgrader is outdated 1.200
But a current signing key is available on our website 0.000
When the network is plugged 0.082
And Tor is ready 18.041
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.584
After features/support/hooks.rb:326 0.850
After features/support/hooks.rb:100 0.000