Project Number Date
test_Tails_ISO_stable 4941 15 Jul 2024, 12:13

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 20:43.058 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:38.641
Before features/support/hooks.rb:269 0.008
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.110
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 30.970
When I start Tails from USB drive "old" with network unplugged 2:1.863
Then the boot device has safe access rights 3.291
And Tails is running from USB drive "old" 0.375
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.150
And udev-watchdog is monitoring the correct device 0.377
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:326 3.594
After features/support/hooks.rb:100 0.011
Tags: @product
2:10.147
Before features/support/hooks.rb:269 0.006
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login 1:23.197
Then Tails is running from USB drive "old" 0.357
And I create a persistent partition 36.298
And I take note of which tps features are available 1.670
Then a Tails persistence partition exists on USB drive "old" 0.980
And I shutdown Tails and wait for the computer to power off 7.450
After features/support/hooks.rb:326 0.207
After features/support/hooks.rb:100 0.013
Tags: @product
2:56.000
Before features/support/hooks.rb:269 0.007
Given a computer 0.247
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.601
Then Tails is running from USB drive "old" 0.348
And all tps features are active 2.085
When I write some files expected to persist 1.943
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.479
And all persistent directories from the old Tails version have safe access rights 2.786
And I take note of which tps features are available 0.463
And I shutdown Tails and wait for the computer to power off 4.392
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.428
After features/support/hooks.rb:326 0.176
After features/support/hooks.rb:100 0.011
Tags: @product
2:26.783
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.467
And I log in to a new session 18.737
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.663
And I plug USB drive "to_upgrade" 2.479
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.405
Then the running Tails is installed on USB drive "to_upgrade" 17.549
And I unplug USB drive "to_upgrade" 0.242
And I unplug USB drive "__internal" 0.238
After features/support/hooks.rb:326 6.713
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.089
Before features/support/hooks.rb:269 0.006
Given a computer 0.204
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.848
Then all tps features from the old Tails version are active 1.563
And Tails is running from USB drive "to_upgrade" 0.338
And the boot device has safe access rights 3.138
And the expected persistent files created with the old Tails version are present in the filesystem 1.520
And all persistent directories from the old Tails version have safe access rights 2.474
After features/support/hooks.rb:326 0.767
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:41.117
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.149
And no SquashFS delta is installed 0.350
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.546
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.308
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.457
When the network is plugged 0.124
And Tor is ready 21.059
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.326
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.089
Given I shutdown Tails and wait for the computer to power off 1:27.246
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.618
Then Tails is running version 6.2~testoverlayfs 0.036
And all tps features are active 2.278
And the file system changes introduced in version 6.2~testoverlayfs are present 0.318
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.334
# 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.279
When the network is plugged 0.035
And Tor is ready 17.706
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.648
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.770
Given I shutdown Tails and wait for the computer to power off 4.435
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.301
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.935
And the file system changes introduced in version 6.3~testoverlayfs are present 0.549
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.331
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.373
When the network is plugged 0.039
And Tor is ready 17.904
Then the Upgrader considers the system as up-to-date 0.386
# 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.945
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.998
After features/support/hooks.rb:326 0.779
After features/support/hooks.rb:100 0.032
Tags: @product @automatic_upgrade
33.277
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.053
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.368
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.782
But a current signing key is available on our website 0.000
When the network is plugged 0.029
And Tor is ready 15.379
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.606
After features/support/hooks.rb:326 0.800
After features/support/hooks.rb:100 0.000