Project Number Date
test_Tails_ISO_stable 5060 31 Aug 2024, 09:05

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:54.432 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:49.172
Before features/support/hooks.rb:269 0.005
Given a computer 1.121
And I create a 7200 MiB disk named "old" 0.926
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 48.395
When I start Tails from USB drive "old" with network unplugged 1:53.315
Then the boot device has safe access rights 3.220
And Tails is running from USB drive "old" 0.407
And there is no persistence partition on USB drive "old" 0.085
And process "udev-watchdog" is running 0.117
And udev-watchdog is monitoring the correct device 0.318
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:326 3.621
After features/support/hooks.rb:100 0.009
Tags: @product
2:25.107
Before features/support/hooks.rb:269 0.009
Given a computer 0.347
And I start Tails from USB drive "old" with network unplugged and I login 1:39.862
Then Tails is running from USB drive "old" 0.346
And I create a persistent partition 33.304
And I take note of which tps features are available 2.028
Then a Tails persistence partition exists on USB drive "old" 0.835
And I shutdown Tails and wait for the computer to power off 8.382
After features/support/hooks.rb:326 0.203
After features/support/hooks.rb:100 0.007
Tags: @product
3:4.901
Before features/support/hooks.rb:269 0.004
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.996
Then Tails is running from USB drive "old" 0.416
And all tps features are active 2.338
When I write some files expected to persist 1.914
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.226
And all persistence configuration files have safe access rights 0.385
And all persistent directories from the old Tails version have safe access rights 2.483
And I take note of which tps features are available 0.499
And I shutdown Tails and wait for the computer to power off 4.527
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.934
After features/support/hooks.rb:326 0.117
After features/support/hooks.rb:100 0.011
Tags: @product
2:38.378
Before features/support/hooks.rb:269 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 10.725
And I log in to a new session 21.038
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.874
And I plug USB drive "to_upgrade" 2.396
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.384
Then the running Tails is installed on USB drive "to_upgrade" 24.506
And I unplug USB drive "to_upgrade" 0.232
And I unplug USB drive "__internal" 0.220
After features/support/hooks.rb:326 2.947
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.636
Before features/support/hooks.rb:269 0.004
Given a computer 0.238
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.856
Then all tps features from the old Tails version are active 1.720
And Tails is running from USB drive "to_upgrade" 0.344
And the boot device has safe access rights 3.168
And the expected persistent files created with the old Tails version are present in the filesystem 1.733
And all persistent directories from the old Tails version have safe access rights 2.573
After features/support/hooks.rb:326 0.746
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
7:2.014
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 13.178
And no SquashFS delta is installed 0.293
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.419
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.348
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.532
When the network is plugged 0.075
And Tor is ready 18.705
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.926
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.769
Given I shutdown Tails and wait for the computer to power off 9.005
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.485
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.471
And the file system changes introduced in version 6.2~testoverlayfs are present 0.381
And only the 6.2~testoverlayfs SquashFS delta is installed 0.091
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.300
# 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.315
When the network is plugged 0.060
And Tor is ready 45.648
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.636
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.629
Given I shutdown Tails and wait for the computer to power off 4.259
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.511
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.206
And the file system changes introduced in version 6.3~testoverlayfs are present 0.496
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.308
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.295
When the network is plugged 0.227
And Tor is ready 18.416
Then the Upgrader considers the system as up-to-date 10.888
# 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.982
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.980
After features/support/hooks.rb:326 0.746
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
35.222
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.287
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.549
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.942
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 15.820
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.483
After features/support/hooks.rb:326 0.955
After features/support/hooks.rb:100 0.000