Project Number Date
test_Tails_ISO_devel 3364 27 Apr 2024, 12:52

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:24.306 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:2.615
Before features/support/hooks.rb:259 0.005
Given a computer 0.259
And I create a 7200 MiB disk named "old" 0.057
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 30.868
When I start Tails from USB drive "old" with network unplugged 1:26.441
Then the boot device has safe access rights 2.901
And Tails is running from USB drive "old" 0.306
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.081
And udev-watchdog is monitoring the correct device 0.359
And I unplug USB drive "old" 0.220
After features/support/hooks.rb:305 3.885
After features/support/hooks.rb:89 0.015
Tags: @product
2:19.941
Before features/support/hooks.rb:259 0.008
Given a computer 1.702
And I start Tails from USB drive "old" with network unplugged and I login 1:27.578
Then Tails is running from USB drive "old" 0.393
And I create a persistent partition 37.923
And I take note of which tps features are available 2.575
Then a Tails persistence partition exists on USB drive "old" 0.844
And I shutdown Tails and wait for the computer to power off 8.921
After features/support/hooks.rb:305 0.192
After features/support/hooks.rb:89 0.010
Tags: @product
3:4.193
Before features/support/hooks.rb:259 0.006
Given a computer 0.523
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.277
Then Tails is running from USB drive "old" 0.483
And all tps features are active 2.493
When I write some files expected to persist 2.147
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
And all persistence configuration files have safe access rights 0.408
And all persistent directories from the old Tails version have safe access rights 2.471
And I take note of which tps features are available 0.459
And I shutdown Tails and wait for the computer to power off 4.518
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.200
After features/support/hooks.rb:305 0.170
After features/support/hooks.rb:89 0.011
Tags: @product
2:34.567
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 16.945
And I log in to a new session 17.715
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.521
And I plug USB drive "to_upgrade" 2.486
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.281
Then the running Tails is installed on USB drive "to_upgrade" 17.220
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.180
After features/support/hooks.rb:305 2.883
After features/support/hooks.rb:89 0.000
Tags: @product
2:18.240
Before features/support/hooks.rb:259 0.006
Given a computer 0.179
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.173
Then all tps features from the old Tails version are active 1.873
And Tails is running from USB drive "to_upgrade" 0.351
And the boot device has safe access rights 3.721
And the expected persistent files created with the old Tails version are present in the filesystem 1.430
And all persistent directories from the old Tails version have safe access rights 2.509
After features/support/hooks.rb:305 0.719
After features/support/hooks.rb:89 0.011
Tags: @product @automatic_upgrade
7:26.950
Before features/support/hooks.rb:259 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.044
And no SquashFS delta is installed 0.149
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.399
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.102
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.288
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.446
When the network is plugged 0.037
And Tor is ready 21.819
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.886
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.733
Given I shutdown Tails and wait for the computer to power off 9.101
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.890
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.525
And the file system changes introduced in version 6.2~testoverlayfs are present 0.322
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# 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.305
When the network is plugged 0.048
And Tor is ready 21.681
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.388
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.232
Given I shutdown Tails and wait for the computer to power off 59.295
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.648
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.437
And the file system changes introduced in version 6.3~testoverlayfs are present 0.518
And only the 6.3~testoverlayfs SquashFS delta is installed 0.083
# 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.381
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.299
When the network is plugged 0.047
And Tor is ready 20.845
Then the Upgrader considers the system as up-to-date 0.308
# 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 16.372
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.858
After features/support/hooks.rb:305 0.716
After features/support/hooks.rb:89 0.018
Tags: @product @automatic_upgrade
37.799
Before features/support/hooks.rb:259 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.223
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.339
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.451
But a current signing key is available on our website 0.000
When the network is plugged 0.108
And Tor is ready 20.103
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.518
After features/support/hooks.rb:305 0.748
After features/support/hooks.rb:89 0.000