Project Number Date
test_Tails_ISO_devel 3597 23 Nov 2024, 12:22

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 18:50.203 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:11.161
Before features/support/hooks.rb:269 0.006
Given a computer 0.180
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 30.596
When I start Tails from USB drive "old" with network unplugged 1:35.135
Then the boot device has safe access rights 3.159
And Tails is running from USB drive "old" 0.325
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.121
And udev-watchdog is monitoring the correct device 0.290
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:326 3.508
After features/support/hooks.rb:100 0.010
Tags: @product
2:5.019
Before features/support/hooks.rb:269 0.006
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login 1:21.737
Then Tails is running from USB drive "old" 0.324
And I create a persistent partition 32.139
And I take note of which tps features are available 1.385
Then a Tails persistence partition exists on USB drive "old" 0.802
And I shutdown Tails and wait for the computer to power off 8.453
After features/support/hooks.rb:326 0.168
After features/support/hooks.rb:100 0.010
Tags: @product
2:47.409
Before features/support/hooks.rb:269 0.007
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:9.298
Then Tails is running from USB drive "old" 0.851
And all tps features are active 1.884
When I write some files expected to persist 2.937
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.377
And all persistent directories from the old Tails version have safe access rights 2.377
And I take note of which tps features are available 0.425
And I shutdown Tails and wait for the computer to power off 4.256
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.572
After features/support/hooks.rb:326 0.121
After features/support/hooks.rb:100 0.008
Tags: @product
2:32.577
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 11.702
And I log in to a new session 19.635
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.813
And I plug USB drive "to_upgrade" 2.399
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.984
Then the running Tails is installed on USB drive "to_upgrade" 21.643
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.197
After features/support/hooks.rb:326 2.243
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.376
Before features/support/hooks.rb:269 0.007
Given a computer 0.183
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.540
Then all tps features from the old Tails version are active 1.487
And Tails is running from USB drive "to_upgrade" 0.327
And the boot device has safe access rights 3.282
And the expected persistent files created with the old Tails version are present in the filesystem 1.338
And all persistent directories from the old Tails version have safe access rights 2.216
After features/support/hooks.rb:326 0.683
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:26.896
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 25.793
And no SquashFS delta is installed 0.106
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.439
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.266
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.411
When the network is plugged 0.081
And Tor is ready 21.435
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.406
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.646
Given I shutdown Tails and wait for the computer to power off 8.712
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.706
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.242
And the file system changes introduced in version 6.2~testoverlayfs are present 0.365
And only the 6.2~testoverlayfs SquashFS delta is installed 0.105
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.346
# 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.300
When the network is plugged 0.069
And Tor is ready 17.190
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.422
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.753
Given I shutdown Tails and wait for the computer to power off 4.334
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.801
Then Tails is running version 6.3~testoverlayfs 0.033
And all tps features are active 2.015
And the file system changes introduced in version 6.3~testoverlayfs are present 0.510
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.356
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.310
When the network is plugged 0.086
And Tor is ready 19.768
Then the Upgrader considers the system as up-to-date 0.317
# 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.285
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.111
After features/support/hooks.rb:326 0.769
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
36.762
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.494
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.337
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.842
But a current signing key is available on our website 0.000
When the network is plugged 0.083
And Tor is ready 19.417
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.525
After features/support/hooks.rb:326 0.931
After features/support/hooks.rb:100 0.000