Project Number Date
test_Tails_ISO_devel 3577 05 Nov 2024, 12:30

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:33.383 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:13.134
Before features/support/hooks.rb:269 0.009
Given a computer 0.620
And I create a 7200 MiB disk named "old" 0.400
And I plug USB drive "old" 1.164
And I write an old version of the Tails USB image to disk "old" 34.047
When I start Tails from USB drive "old" with network unplugged 1:32.302
Then the boot device has safe access rights 3.393
And Tails is running from USB drive "old" 0.416
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.368
And I unplug USB drive "old" 0.244
After features/support/hooks.rb:326 7.188
After features/support/hooks.rb:100 0.013
Tags: @product
2:14.346
Before features/support/hooks.rb:269 0.008
Given a computer 0.222
And I start Tails from USB drive "old" with network unplugged and I login 1:27.261
Then Tails is running from USB drive "old" 0.459
And I create a persistent partition 34.964
And I take note of which tps features are available 1.963
Then a Tails persistence partition exists on USB drive "old" 0.809
And I shutdown Tails and wait for the computer to power off 8.665
After features/support/hooks.rb:326 0.210
After features/support/hooks.rb:100 0.010
Tags: @product
3:11.279
Before features/support/hooks.rb:269 0.007
Given a computer 0.219
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:32.369
Then Tails is running from USB drive "old" 0.424
And all tps features are active 2.329
When I write some files expected to persist 1.892
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.259
And all persistence configuration files have safe access rights 0.442
And all persistent directories from the old Tails version have safe access rights 2.710
And I take note of which tps features are available 0.764
And I shutdown Tails and wait for the computer to power off 4.044
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.822
After features/support/hooks.rb:326 0.143
After features/support/hooks.rb:100 0.011
Tags: @product
2:41.407
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 16.632
And I log in to a new session 19.769
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.719
And I plug USB drive "to_upgrade" 2.409
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.868
Then the running Tails is installed on USB drive "to_upgrade" 23.577
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.227
After features/support/hooks.rb:326 3.591
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.671
Before features/support/hooks.rb:269 0.006
Given a computer 0.252
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.395
Then all tps features from the old Tails version are active 1.818
And Tails is running from USB drive "to_upgrade" 0.386
And the boot device has safe access rights 3.471
And the expected persistent files created with the old Tails version are present in the filesystem 1.621
And all persistent directories from the old Tails version have safe access rights 2.726
After features/support/hooks.rb:326 0.706
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
7:3.240
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 18.203
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.305
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.465
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.642
When the network is plugged 0.098
And Tor is ready 23.207
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.737
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.303
Given I shutdown Tails and wait for the computer to power off 9.122
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.634
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.569
And the file system changes introduced in version 6.2~testoverlayfs are present 0.411
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.373
# 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.365
When the network is plugged 0.110
And Tor is ready 20.317
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.695
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.240
Given I shutdown Tails and wait for the computer to power off 6.635
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.688
Then Tails is running version 6.3~testoverlayfs 0.030
And all tps features are active 2.429
And the file system changes introduced in version 6.3~testoverlayfs are present 0.670
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.361
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.306
When the network is plugged 0.086
And Tor is ready 22.196
Then the Upgrader considers the system as up-to-date 0.341
# 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 16.140
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.215
After features/support/hooks.rb:326 0.827
After features/support/hooks.rb:100 0.028
Tags: @product @automatic_upgrade
46.305
Before features/support/hooks.rb:269 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.381
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.392
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.080
And the signing key used by the Upgrader is outdated 0.967
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 25.357
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.056
After features/support/hooks.rb:326 0.934
After features/support/hooks.rb:100 0.000