Project Number Date
test_Tails_ISO_stable 5222 25 Oct 2024, 12:44

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:19.064 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:48.772
Before features/support/hooks.rb:269 0.005
Given a computer 0.337
And I create a 7200 MiB disk named "old" 0.072
And I plug USB drive "old" 1.067
And I write an old version of the Tails USB image to disk "old" 1:6.355
When I start Tails from USB drive "old" with network unplugged 1:36.042
Then the boot device has safe access rights 3.745
And Tails is running from USB drive "old" 0.375
And there is no persistence partition on USB drive "old" 0.089
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.348
And I unplug USB drive "old" 0.236
After features/support/hooks.rb:326 7.265
After features/support/hooks.rb:100 0.010
Tags: @product
2:13.114
Before features/support/hooks.rb:269 0.006
Given a computer 0.289
And I start Tails from USB drive "old" with network unplugged and I login 1:26.329
Then Tails is running from USB drive "old" 0.384
And I create a persistent partition 34.532
And I take note of which tps features are available 2.060
Then a Tails persistence partition exists on USB drive "old" 0.812
And I shutdown Tails and wait for the computer to power off 8.705
After features/support/hooks.rb:326 0.192
After features/support/hooks.rb:100 0.010
Tags: @product
3:2.863
Before features/support/hooks.rb:269 0.005
Given a computer 0.241
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.342
Then Tails is running from USB drive "old" 0.748
And all tps features are active 2.432
When I write some files expected to persist 1.996
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.601
And all persistence configuration files have safe access rights 0.464
And all persistent directories from the old Tails version have safe access rights 3.060
And I take note of which tps features are available 0.662
And I shutdown Tails and wait for the computer to power off 4.500
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.812
After features/support/hooks.rb:326 0.159
After features/support/hooks.rb:100 0.009
Tags: @product
2:58.068
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 33.314
And I log in to a new session 21.839
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.173
And I plug USB drive "to_upgrade" 2.547
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.192
Then the running Tails is installed on USB drive "to_upgrade" 19.556
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.234
After features/support/hooks.rb:326 7.132
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.272
Before features/support/hooks.rb:269 0.008
Given a computer 0.227
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.868
Then all tps features from the old Tails version are active 2.020
And Tails is running from USB drive "to_upgrade" 0.389
And the boot device has safe access rights 3.549
And the expected persistent files created with the old Tails version are present in the filesystem 1.534
And all persistent directories from the old Tails version have safe access rights 2.680
After features/support/hooks.rb:326 0.797
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:19.000
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 32.605
And no SquashFS delta is installed 0.104
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.384
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.415
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.600
When the network is plugged 0.101
And Tor is ready 25.211
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.473
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.090
Given I shutdown Tails and wait for the computer to power off 11.611
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.210
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 5.715
And the file system changes introduced in version 6.2~testoverlayfs are present 0.353
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.354
# 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.296
When the network is plugged 0.357
And Tor is ready 19.431
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.848
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.763
Given I shutdown Tails and wait for the computer to power off 4.817
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.122
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.137
And the file system changes introduced in version 6.3~testoverlayfs are present 0.580
And only the 6.3~testoverlayfs SquashFS delta is installed 0.093
# 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.319
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.535
When the network is plugged 0.078
And Tor is ready 18.592
Then the Upgrader considers the system as up-to-date 0.336
# 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.197
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.068
After features/support/hooks.rb:326 0.841
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
36.973
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.760
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.399
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.762
But a current signing key is available on our website 0.000
When the network is plugged 0.095
And Tor is ready 17.243
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.649
After features/support/hooks.rb:326 1.541
After features/support/hooks.rb:100 0.000