Project Number Date
test_Tails_ISO_stable 5174 11 Oct 2024, 02:33

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:56.547 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:40.151
Before features/support/hooks.rb:269 0.005
Given a computer 0.365
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 31.841
When I start Tails from USB drive "old" with network unplugged 2:1.718
Then the boot device has safe access rights 3.839
And Tails is running from USB drive "old" 0.411
And there is no persistence partition on USB drive "old" 0.091
And process "udev-watchdog" is running 0.126
And udev-watchdog is monitoring the correct device 0.369
And I unplug USB drive "old" 0.275
After features/support/hooks.rb:326 3.850
After features/support/hooks.rb:100 0.011
Tags: @product
2:6.596
Before features/support/hooks.rb:269 0.004
Given a computer 0.280
And I start Tails from USB drive "old" with network unplugged and I login 1:21.930
Then Tails is running from USB drive "old" 0.353
And I create a persistent partition 33.256
And I take note of which tps features are available 1.530
Then a Tails persistence partition exists on USB drive "old" 0.759
And I shutdown Tails and wait for the computer to power off 8.485
After features/support/hooks.rb:326 0.178
After features/support/hooks.rb:100 0.012
Tags: @product
2:52.757
Before features/support/hooks.rb:269 0.005
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.528
Then Tails is running from USB drive "old" 0.314
And all tps features are active 2.027
When I write some files expected to persist 1.753
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.317
And all persistence configuration files have safe access rights 0.435
And all persistent directories from the old Tails version have safe access rights 2.389
And I take note of which tps features are available 0.471
And I shutdown Tails and wait for the computer to power off 4.306
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.014
After features/support/hooks.rb:326 0.129
After features/support/hooks.rb:100 0.007
Tags: @product
2:32.948
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.069
And I log in to a new session 18.816
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.675
And I plug USB drive "to_upgrade" 2.387
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.077
Then the running Tails is installed on USB drive "to_upgrade" 23.501
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:326 2.812
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.496
Before features/support/hooks.rb:269 0.004
Given a computer 0.183
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.061
Then all tps features from the old Tails version are active 1.641
And Tails is running from USB drive "to_upgrade" 0.339
And the boot device has safe access rights 3.088
And the expected persistent files created with the old Tails version are present in the filesystem 1.531
And all persistent directories from the old Tails version have safe access rights 2.650
After features/support/hooks.rb:326 0.662
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:31.267
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 12.067
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.469
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.087
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.326
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.556
When the network is plugged 0.064
And Tor is ready 20.220
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.589
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.327
Given I shutdown Tails and wait for the computer to power off 10.840
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.782
Then Tails is running version 6.2~testoverlayfs 0.050
And all tps features are active 2.257
And the file system changes introduced in version 6.2~testoverlayfs are present 0.316
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.337
# 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.280
When the network is plugged 0.077
And Tor is ready 18.371
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.278
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.156
Given I shutdown Tails and wait for the computer to power off 4.282
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.603
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.109
And the file system changes introduced in version 6.3~testoverlayfs are present 0.590
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.281
When the network is plugged 0.064
And Tor is ready 16.475
Then the Upgrader considers the system as up-to-date 0.369
# 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.192
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.260
After features/support/hooks.rb:326 0.776
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
58.330
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 9.828
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.282
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 0.866
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 46.623
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.589
After features/support/hooks.rb:326 0.647
After features/support/hooks.rb:100 0.000