Project Number Date
test_Tails_ISO_stable 4916 29 Jun 2024, 12:45

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 17:48.981 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
1:58.772
Before features/support/hooks.rb:269 0.007
Given a computer 0.192
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 30.208
When I start Tails from USB drive "old" with network unplugged 1:23.598
Then the boot device has safe access rights 2.780
And Tails is running from USB drive "old" 0.286
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.088
And udev-watchdog is monitoring the correct device 0.285
And I unplug USB drive "old" 0.174
After features/support/hooks.rb:326 7.037
After features/support/hooks.rb:100 0.010
Tags: @product
2:0.366
Before features/support/hooks.rb:269 0.007
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 1:18.356
Then Tails is running from USB drive "old" 0.288
And I create a persistent partition 31.100
And I take note of which tps features are available 1.421
Then a Tails persistence partition exists on USB drive "old" 0.772
And I shutdown Tails and wait for the computer to power off 8.233
After features/support/hooks.rb:326 0.151
After features/support/hooks.rb:100 0.012
Tags: @product
2:41.687
Before features/support/hooks.rb:269 0.007
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:5.070
Then Tails is running from USB drive "old" 0.386
And all tps features are active 1.861
When I write some files expected to persist 1.524
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.206
And all persistence configuration files have safe access rights 0.612
And all persistent directories from the old Tails version have safe access rights 2.421
And I take note of which tps features are available 0.384
And I shutdown Tails and wait for the computer to power off 4.281
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.726
After features/support/hooks.rb:326 0.103
After features/support/hooks.rb:100 0.011
Tags: @product
2:23.480
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.273
And I log in to a new session 18.240
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.548
And I plug USB drive "to_upgrade" 2.428
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.509
Then the running Tails is installed on USB drive "to_upgrade" 18.103
And I unplug USB drive "to_upgrade" 0.192
And I unplug USB drive "__internal" 0.184
After features/support/hooks.rb:326 1.906
After features/support/hooks.rb:100 0.000
Tags: @product
2:4.395
Before features/support/hooks.rb:269 0.007
Given a computer 0.209
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:55.811
Then all tps features from the old Tails version are active 1.445
And Tails is running from USB drive "to_upgrade" 0.328
And the boot device has safe access rights 2.913
And the expected persistent files created with the old Tails version are present in the filesystem 1.445
And all persistent directories from the old Tails version have safe access rights 2.240
After features/support/hooks.rb:326 0.698
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:7.105
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.231
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.343
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.277
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.404
When the network is plugged 0.045
And Tor is ready 20.474
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.996
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.475
Given I shutdown Tails and wait for the computer to power off 8.364
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.663
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.916
And the file system changes introduced in version 6.2~testoverlayfs are present 0.287
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.375
# 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.256
When the network is plugged 0.031
And Tor is ready 18.602
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.095
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.509
Given I shutdown Tails and wait for the computer to power off 4.163
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.324
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.858
And the file system changes introduced in version 6.3~testoverlayfs are present 0.438
And only the 6.3~testoverlayfs SquashFS delta is installed 0.055
# 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.337
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.285
When the network is plugged 0.035
And Tor is ready 19.436
Then the Upgrader considers the system as up-to-date 0.327
# 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.199
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.080
After features/support/hooks.rb:326 0.727
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
33.174
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 9.923
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.314
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.100
And the signing key used by the Upgrader is outdated 0.713
But a current signing key is available on our website 0.000
When the network is plugged 0.044
And Tor is ready 17.172
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.904
After features/support/hooks.rb:326 0.899
After features/support/hooks.rb:100 0.000