Project Number Date
test_Tails_ISO_devel 3449 07 Jul 2024, 12:27

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:26.564 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:24.295
Before features/support/hooks.rb:269 0.006
Given a computer 0.218
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 29.988
When I start Tails from USB drive "old" with network unplugged 1:48.990
Then the boot device has safe access rights 3.013
And Tails is running from USB drive "old" 0.334
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.300
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:326 3.513
After features/support/hooks.rb:100 0.011
Tags: @product
2:1.124
Before features/support/hooks.rb:269 0.007
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login 1:18.055
Then Tails is running from USB drive "old" 0.301
And I create a persistent partition 31.925
And I take note of which tps features are available 1.600
Then a Tails persistence partition exists on USB drive "old" 0.816
And I shutdown Tails and wait for the computer to power off 8.217
After features/support/hooks.rb:326 0.184
After features/support/hooks.rb:100 0.010
Tags: @product
2:44.707
Before features/support/hooks.rb:269 0.007
Given a computer 0.215
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.375
Then Tails is running from USB drive "old" 0.314
And all tps features are active 1.812
When I write some files expected to persist 1.624
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.257
And all persistence configuration files have safe access rights 0.325
And all persistent directories from the old Tails version have safe access rights 2.201
And I take note of which tps features are available 0.412
And I shutdown Tails and wait for the computer to power off 4.335
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 22.832
After features/support/hooks.rb:326 0.155
After features/support/hooks.rb:100 0.010
Tags: @product
2:25.572
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 10.620
And I log in to a new session 16.667
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.362
And I plug USB drive "to_upgrade" 2.348
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.946
Then the running Tails is installed on USB drive "to_upgrade" 21.211
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:326 3.493
After features/support/hooks.rb:100 0.000
Tags: @product
2:2.927
Before features/support/hooks.rb:269 0.007
Given a computer 0.209
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:54.252
Then all tps features from the old Tails version are active 1.647
And Tails is running from USB drive "to_upgrade" 0.293
And the boot device has safe access rights 2.797
And the expected persistent files created with the old Tails version are present in the filesystem 1.344
And all persistent directories from the old Tails version have safe access rights 2.383
After features/support/hooks.rb:326 0.891
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:11.635
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 10.377
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.356
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.303
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.540
When the network is plugged 0.042
And Tor is ready 17.101
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.344
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.930
Given I shutdown Tails and wait for the computer to power off 8.607
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.798
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.065
And the file system changes introduced in version 6.2~testoverlayfs are present 0.275
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.320
# 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.261
When the network is plugged 0.044
And Tor is ready 17.800
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.168
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.323
Given I shutdown Tails and wait for the computer to power off 4.249
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.101
Then Tails is running version 6.3~testoverlayfs 0.036
And all tps features are active 2.073
And the file system changes introduced in version 6.3~testoverlayfs are present 0.495
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.318
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.223
When the network is plugged 0.037
And Tor is ready 17.883
Then the Upgrader considers the system as up-to-date 0.306
# 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 13.866
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.132
After features/support/hooks.rb:326 0.686
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
36.300
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 9.762
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.350
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.681
But a current signing key is available on our website 0.000
When the network is plugged 0.047
And Tor is ready 19.044
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.365
After features/support/hooks.rb:326 0.633
After features/support/hooks.rb:100 0.000