Project Number Date
test_Tails_ISO_devel 3612 14 Dec 2024, 12:38

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 18:43.863 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:1.639
Before features/support/hooks.rb:269 0.006
Given a computer 0.201
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 30.818
When I start Tails from USB drive "old" with network unplugged 1:25.431
Then the boot device has safe access rights 3.066
And Tails is running from USB drive "old" 0.331
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.323
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:326 3.599
After features/support/hooks.rb:100 0.008
Tags: @product
2:4.830
Before features/support/hooks.rb:269 0.006
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login 1:21.946
Then Tails is running from USB drive "old" 0.301
And I create a persistent partition 31.590
And I take note of which tps features are available 1.837
Then a Tails persistence partition exists on USB drive "old" 0.818
And I shutdown Tails and wait for the computer to power off 8.148
After features/support/hooks.rb:326 0.143
After features/support/hooks.rb:100 0.012
Tags: @product
2:47.614
Before features/support/hooks.rb:269 0.007
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.432
Then Tails is running from USB drive "old" 1.027
And all tps features are active 2.012
When I write some files expected to persist 2.255
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.219
And all persistence configuration files have safe access rights 0.371
And all persistent directories from the old Tails version have safe access rights 2.326
And I take note of which tps features are available 0.491
And I shutdown Tails and wait for the computer to power off 4.292
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.974
After features/support/hooks.rb:326 0.114
After features/support/hooks.rb:100 0.010
Tags: @product
2:28.131
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.114
And I log in to a new session 17.773
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.589
And I plug USB drive "to_upgrade" 2.435
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.132
Then the running Tails is installed on USB drive "to_upgrade" 20.675
And I unplug USB drive "to_upgrade" 0.196
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:326 7.178
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.400
Before features/support/hooks.rb:269 0.007
Given a computer 0.207
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:18.127
Then all tps features from the old Tails version are active 1.729
And Tails is running from USB drive "to_upgrade" 0.397
And the boot device has safe access rights 3.117
And the expected persistent files created with the old Tails version are present in the filesystem 1.487
And all persistent directories from the old Tails version have safe access rights 2.333
After features/support/hooks.rb:326 0.737
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:17.242
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.748
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.600
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.268
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.488
When the network is plugged 0.066
And Tor is ready 21.178
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.020
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.101
Given I shutdown Tails and wait for the computer to power off 8.805
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.881
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.209
And the file system changes introduced in version 6.2~testoverlayfs are present 0.298
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.303
# 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.250
When the network is plugged 0.066
And Tor is ready 19.010
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.191
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.812
Given I shutdown Tails and wait for the computer to power off 4.304
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.523
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.154
And the file system changes introduced in version 6.3~testoverlayfs are present 0.542
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.324
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.320
When the network is plugged 0.085
And Tor is ready 20.105
Then the Upgrader considers the system as up-to-date 0.318
# 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.762
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.182
After features/support/hooks.rb:326 0.750
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
37.003
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.251
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.277
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.770
But a current signing key is available on our website 0.000
When the network is plugged 0.174
And Tor is ready 19.173
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.293
After features/support/hooks.rb:326 0.863
After features/support/hooks.rb:100 0.000