Project Number Date
test_Tails_ISO_devel 3557 21 Oct 2024, 15:00

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:8.176 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:21.801
Before features/support/hooks.rb:269 0.008
Given a computer 0.307
And I create a 7200 MiB disk named "old" 0.058
And I plug USB drive "old" 1.063
And I write an old version of the Tails USB image to disk "old" 36.383
When I start Tails from USB drive "old" with network unplugged 1:39.871
Then the boot device has safe access rights 3.145
And Tails is running from USB drive "old" 0.318
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.306
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:326 3.510
After features/support/hooks.rb:100 0.010
Tags: @product
2:11.722
Before features/support/hooks.rb:269 0.006
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login 1:27.024
Then Tails is running from USB drive "old" 0.447
And I create a persistent partition 33.050
And I take note of which tps features are available 1.770
Then a Tails persistence partition exists on USB drive "old" 0.813
And I shutdown Tails and wait for the computer to power off 8.409
After features/support/hooks.rb:326 0.206
After features/support/hooks.rb:100 0.008
Tags: @product
2:54.323
Before features/support/hooks.rb:269 0.005
Given a computer 0.235
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.954
Then Tails is running from USB drive "old" 0.799
And all tps features are active 2.121
When I write some files expected to persist 1.835
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.224
And all persistence configuration files have safe access rights 0.418
And all persistent directories from the old Tails version have safe access rights 3.200
And I take note of which tps features are available 0.468
And I shutdown Tails and wait for the computer to power off 4.331
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.734
After features/support/hooks.rb:326 0.157
After features/support/hooks.rb:100 0.012
Tags: @product
2:45.814
Before features/support/hooks.rb:269 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 12.076
And I log in to a new session 21.155
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.711
And I plug USB drive "to_upgrade" 2.436
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.671
Then the running Tails is installed on USB drive "to_upgrade" 25.299
And I unplug USB drive "to_upgrade" 0.220
And I unplug USB drive "__internal" 0.242
After features/support/hooks.rb:326 2.861
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.248
Before features/support/hooks.rb:269 0.006
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.768
Then all tps features from the old Tails version are active 1.739
And Tails is running from USB drive "to_upgrade" 0.370
And the boot device has safe access rights 4.069
And the expected persistent files created with the old Tails version are present in the filesystem 1.553
And all persistent directories from the old Tails version have safe access rights 2.557
After features/support/hooks.rb:326 0.718
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
6:56.895
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 15.086
And no SquashFS delta is installed 0.115
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.606
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.393
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.486
When the network is plugged 0.068
And Tor is ready 22.180
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.694
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.404
Given I shutdown Tails and wait for the computer to power off 11.662
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.499
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.574
And the file system changes introduced in version 6.2~testoverlayfs are present 0.396
And only the 6.2~testoverlayfs SquashFS delta is installed 0.109
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.347
# 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.308
When the network is plugged 0.100
And Tor is ready 22.327
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.602
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.964
Given I shutdown Tails and wait for the computer to power off 4.641
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.772
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 2.490
And the file system changes introduced in version 6.3~testoverlayfs are present 0.558
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.389
When the network is plugged 0.099
And Tor is ready 21.593
Then the Upgrader considers the system as up-to-date 0.347
# 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.356
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.192
After features/support/hooks.rb:326 0.771
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
42.370
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 11.929
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.836
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.114
And the signing key used by the Upgrader is outdated 1.014
But a current signing key is available on our website 0.000
When the network is plugged 0.339
And Tor is ready 20.849
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.287
After features/support/hooks.rb:326 0.843
After features/support/hooks.rb:100 0.000