Project Number Date
test_Tails_ISO_devel 3628 31 Dec 2024, 12:23

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:54.142 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:2.147
Before features/support/hooks.rb:269 0.007
Given a computer 0.209
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 28.375
When I start Tails from USB drive "old" with network unplugged 1:28.322
Then the boot device has safe access rights 2.980
And Tails is running from USB drive "old" 0.471
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.110
And udev-watchdog is monitoring the correct device 0.304
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:326 7.059
After features/support/hooks.rb:100 0.010
Tags: @product
2:8.737
Before features/support/hooks.rb:269 0.007
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login 1:25.890
Then Tails is running from USB drive "old" 0.328
And I create a persistent partition 31.729
And I take note of which tps features are available 1.458
Then a Tails persistence partition exists on USB drive "old" 0.848
And I shutdown Tails and wait for the computer to power off 8.283
After features/support/hooks.rb:326 0.165
After features/support/hooks.rb:100 0.010
Tags: @product
2:49.834
Before features/support/hooks.rb:269 0.007
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.088
Then Tails is running from USB drive "old" 0.362
And all tps features are active 2.021
When I write some files expected to persist 3.300
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.247
And all persistence configuration files have safe access rights 0.385
And all persistent directories from the old Tails version have safe access rights 2.416
And I take note of which tps features are available 0.459
And I shutdown Tails and wait for the computer to power off 4.250
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.112
After features/support/hooks.rb:326 0.084
After features/support/hooks.rb:100 0.008
Tags: @product
2:30.057
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.084
And I log in to a new session 17.876
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.564
And I plug USB drive "to_upgrade" 2.418
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.468
Then the running Tails is installed on USB drive "to_upgrade" 24.206
And I unplug USB drive "to_upgrade" 0.215
And I unplug USB drive "__internal" 0.221
After features/support/hooks.rb:326 2.300
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.723
Before features/support/hooks.rb:269 0.007
Given a computer 0.223
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.368
Then all tps features from the old Tails version are active 1.640
And Tails is running from USB drive "to_upgrade" 0.361
And the boot device has safe access rights 3.189
And the expected persistent files created with the old Tails version are present in the filesystem 1.550
And all persistent directories from the old Tails version have safe access rights 2.388
After features/support/hooks.rb:326 0.611
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:22.052
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 11.586
And no SquashFS delta is installed 0.108
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.339
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.324
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.519
When the network is plugged 0.079
And Tor is ready 22.859
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.770
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.157
Given I shutdown Tails and wait for the computer to power off 8.441
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.285
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.267
And the file system changes introduced in version 6.2~testoverlayfs are present 0.302
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.301
# 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.287
When the network is plugged 0.071
And Tor is ready 16.130
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.467
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.118
Given I shutdown Tails and wait for the computer to power off 4.287
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.197
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.932
And the file system changes introduced in version 6.3~testoverlayfs are present 0.527
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.298
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.306
When the network is plugged 0.091
And Tor is ready 18.443
Then the Upgrader considers the system as up-to-date 0.301
# 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.610
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.399
After features/support/hooks.rb:326 0.766
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
39.590
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 11.014
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.548
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 1.990
But a current signing key is available on our website 0.000
When the network is plugged 0.255
And Tor is ready 19.170
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.560
After features/support/hooks.rb:326 0.708
After features/support/hooks.rb:100 0.000