Project Number Date
test_Tails_ISO_stable 5160 08 Oct 2024, 20: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 21:13.626 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:46.306
Before features/support/hooks.rb:269 0.005
Given a computer 0.252
And I create a 7200 MiB disk named "old" 0.075
And I plug USB drive "old" 1.076
And I write an old version of the Tails USB image to disk "old" 52.835
When I start Tails from USB drive "old" with network unplugged 1:47.517
Then the boot device has safe access rights 3.463
And Tails is running from USB drive "old" 0.330
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.114
And udev-watchdog is monitoring the correct device 0.337
And I unplug USB drive "old" 0.221
After features/support/hooks.rb:326 3.854
After features/support/hooks.rb:100 0.009
Tags: @product
2:10.967
Before features/support/hooks.rb:269 0.005
Given a computer 0.378
And I start Tails from USB drive "old" with network unplugged and I login 1:27.834
Then Tails is running from USB drive "old" 0.369
And I create a persistent partition 33.405
And I take note of which tps features are available 1.671
Then a Tails persistence partition exists on USB drive "old" 0.815
And I shutdown Tails and wait for the computer to power off 6.492
After features/support/hooks.rb:326 0.184
After features/support/hooks.rb:100 0.015
Tags: @product
3:7.837
Before features/support/hooks.rb:269 0.005
Given a computer 0.222
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:25.652
Then Tails is running from USB drive "old" 1.223
And all tps features are active 2.346
When I write some files expected to persist 4.286
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.293
And all persistence configuration files have safe access rights 0.430
And all persistent directories from the old Tails version have safe access rights 2.461
And I take note of which tps features are available 0.567
And I shutdown Tails and wait for the computer to power off 4.429
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.925
After features/support/hooks.rb:326 0.128
After features/support/hooks.rb:100 0.009
Tags: @product
2:47.682
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.713
And I log in to a new session 23.243
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.675
And I plug USB drive "to_upgrade" 2.461
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.374
Then the running Tails is installed on USB drive "to_upgrade" 23.294
And I unplug USB drive "to_upgrade" 0.448
And I unplug USB drive "__internal" 0.470
After features/support/hooks.rb:326 2.430
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.992
Before features/support/hooks.rb:269 0.005
Given a computer 1.288
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.647
Then all tps features from the old Tails version are active 1.898
And Tails is running from USB drive "to_upgrade" 0.337
And the boot device has safe access rights 3.232
And the expected persistent files created with the old Tails version are present in the filesystem 1.974
And all persistent directories from the old Tails version have safe access rights 2.613
After features/support/hooks.rb:326 0.794
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
6:55.089
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.816
And no SquashFS delta is installed 0.107
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.411
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.343
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.488
When the network is plugged 0.264
And Tor is ready 23.052
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.002
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.907
Given I shutdown Tails and wait for the computer to power off 11.321
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.996
Then Tails is running version 6.2~testoverlayfs 0.046
And all tps features are active 2.722
And the file system changes introduced in version 6.2~testoverlayfs are present 0.343
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.319
# 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.288
When the network is plugged 0.096
And Tor is ready 19.774
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.170
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.369
Given I shutdown Tails and wait for the computer to power off 4.266
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.463
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.210
And the file system changes introduced in version 6.3~testoverlayfs are present 0.486
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.424
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.302
When the network is plugged 0.079
And Tor is ready 19.181
Then the Upgrader considers the system as up-to-date 0.345
# 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.203
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.065
After features/support/hooks.rb:326 0.769
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
57.750
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 26.985
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.925
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 2.042
But a current signing key is available on our website 0.000
When the network is plugged 0.089
And Tor is ready 21.957
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.681
After features/support/hooks.rb:326 1.525
After features/support/hooks.rb:100 0.000