Project Number Date
test_Tails_ISO_devel 3379 08 May 2024, 12:56

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:46.884 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:27.835
Before features/support/hooks.rb:259 0.008
Given a computer 1.102
And I create a 7200 MiB disk named "old" 0.360
And I plug USB drive "old" 1.191
And I write an old version of the Tails USB image to disk "old" 41.111
When I start Tails from USB drive "old" with network unplugged 1:40.036
Then the boot device has safe access rights 3.017
And Tails is running from USB drive "old" 0.352
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.319
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:305 3.520
After features/support/hooks.rb:89 0.013
Tags: @product
2:18.019
Before features/support/hooks.rb:259 0.006
Given a computer 0.247
And I start Tails from USB drive "old" with network unplugged and I login 1:30.514
Then Tails is running from USB drive "old" 0.353
And I create a persistent partition 35.566
And I take note of which tps features are available 2.103
Then a Tails persistence partition exists on USB drive "old" 0.833
And I shutdown Tails and wait for the computer to power off 8.399
After features/support/hooks.rb:305 0.161
After features/support/hooks.rb:89 0.011
Tags: @product
2:58.868
Before features/support/hooks.rb:259 0.007
Given a computer 0.913
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.061
Then Tails is running from USB drive "old" 0.377
And all tps features are active 5.329
When I write some files expected to persist 1.699
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.217
And all persistence configuration files have safe access rights 0.359
And all persistent directories from the old Tails version have safe access rights 2.338
And I take note of which tps features are available 1.551
And I shutdown Tails and wait for the computer to power off 4.450
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.567
After features/support/hooks.rb:305 0.144
After features/support/hooks.rb:89 0.009
Tags: @product
2:34.032
Before features/support/hooks.rb:259 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 17.193
And I log in to a new session 19.067
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.670
And I plug USB drive "to_upgrade" 2.402
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.302
Then the running Tails is installed on USB drive "to_upgrade" 17.984
And I unplug USB drive "to_upgrade" 0.230
And I unplug USB drive "__internal" 0.181
After features/support/hooks.rb:305 2.156
After features/support/hooks.rb:89 0.000
Tags: @product
2:18.154
Before features/support/hooks.rb:259 0.008
Given a computer 0.382
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.327
Then all tps features from the old Tails version are active 1.897
And Tails is running from USB drive "to_upgrade" 0.444
And the boot device has safe access rights 3.312
And the expected persistent files created with the old Tails version are present in the filesystem 1.999
And all persistent directories from the old Tails version have safe access rights 2.790
After features/support/hooks.rb:305 0.728
After features/support/hooks.rb:89 0.011
6:33.422
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 14.992
And no SquashFS delta is installed 0.125
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.147
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.093
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.340
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.512
When the network is plugged 0.081
And Tor is ready 20.840
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.898
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.633
Given I shutdown Tails and wait for the computer to power off 8.886
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.818
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.293
And the file system changes introduced in version 6.2~testoverlayfs are present 0.317
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.417
# 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.324
When the network is plugged 0.051
And Tor is ready 20.264
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.424
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.298
Given I shutdown Tails and wait for the computer to power off 4.609
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.205
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.340
And the file system changes introduced in version 6.3~testoverlayfs are present 0.656
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.330
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.281
When the network is plugged 0.046
And Tor is ready 20.682
Then the Upgrader considers the system as up-to-date 0.305
# 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.175
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.859
After features/support/hooks.rb:305 0.893
After features/support/hooks.rb:89 0.046
36.551
Before features/support/hooks.rb:259 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.788
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.556
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.877
But a current signing key is available on our website 0.000
When the network is plugged 0.091
And Tor is ready 19.109
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.073
After features/support/hooks.rb:305 1.004
After features/support/hooks.rb:89 0.000