Project Number Date
test_Tails_ISO_devel 3366 29 Apr 2024, 12:40

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:43.920 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:24.804
Before features/support/hooks.rb:259 0.007
Given a computer 0.212
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 32.435
When I start Tails from USB drive "old" with network unplugged 1:47.144
Then the boot device has safe access rights 2.923
And Tails is running from USB drive "old" 0.324
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.298
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:305 7.531
After features/support/hooks.rb:89 0.011
Tags: @product
2:10.744
Before features/support/hooks.rb:259 0.007
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login 1:22.912
Then Tails is running from USB drive "old" 0.389
And I create a persistent partition 35.723
And I take note of which tps features are available 1.780
Then a Tails persistence partition exists on USB drive "old" 0.872
And I shutdown Tails and wait for the computer to power off 8.864
After features/support/hooks.rb:305 0.209
After features/support/hooks.rb:89 0.014
Tags: @product
3:3.603
Before features/support/hooks.rb:259 0.011
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.885
Then Tails is running from USB drive "old" 0.460
And all tps features are active 2.327
When I write some files expected to persist 2.140
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.300
And all persistence configuration files have safe access rights 0.464
And all persistent directories from the old Tails version have safe access rights 2.583
And I take note of which tps features are available 0.455
And I shutdown Tails and wait for the computer to power off 4.615
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.138
After features/support/hooks.rb:305 0.150
After features/support/hooks.rb:89 0.013
Tags: @product
2:32.919
Before features/support/hooks.rb:259 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.007
And I log in to a new session 18.012
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.313
And I plug USB drive "to_upgrade" 2.464
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.456
Then the running Tails is installed on USB drive "to_upgrade" 23.186
And I unplug USB drive "to_upgrade" 0.277
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:305 3.398
After features/support/hooks.rb:89 0.000
Tags: @product
2:17.412
Before features/support/hooks.rb:259 0.009
Given a computer 0.304
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.708
Then all tps features from the old Tails version are active 1.917
And Tails is running from USB drive "to_upgrade" 0.434
And the boot device has safe access rights 3.679
And the expected persistent files created with the old Tails version are present in the filesystem 1.570
And all persistent directories from the old Tails version have safe access rights 2.798
After features/support/hooks.rb:305 0.657
After features/support/hooks.rb:89 0.037
Tags: @product @automatic_upgrade
6:36.535
Before features/support/hooks.rb:259 0.024
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.384
And no SquashFS delta is installed 0.143
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.537
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.405
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.505
When the network is plugged 0.041
And Tor is ready 22.553
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.093
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.637
Given I shutdown Tails and wait for the computer to power off 9.141
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.435
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.209
And the file system changes introduced in version 6.2~testoverlayfs are present 0.490
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.334
# 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.268
When the network is plugged 0.060
And Tor is ready 20.172
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.555
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.959
Given I shutdown Tails and wait for the computer to power off 4.467
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.205
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.060
And the file system changes introduced in version 6.3~testoverlayfs are present 0.479
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.338
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.255
When the network is plugged 0.040
And Tor is ready 21.675
Then the Upgrader considers the system as up-to-date 0.328
# 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.575
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.928
After features/support/hooks.rb:305 1.020
After features/support/hooks.rb:89 0.022
Tags: @product @automatic_upgrade
37.900
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.953
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.384
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.513
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 18.987
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.956
After features/support/hooks.rb:305 0.731
After features/support/hooks.rb:89 0.000