Project Number Date
test_Tails_ISO_devel 3471 08 Aug 2024, 16:20

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 19:49.517 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:33.702
Before features/support/hooks.rb:269 0.008
Given a computer 0.357
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 1:1.567
When I start Tails from USB drive "old" with network unplugged 1:26.454
Then the boot device has safe access rights 3.209
And Tails is running from USB drive "old" 0.327
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.325
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:326 3.714
After features/support/hooks.rb:100 0.011
Tags: @product
2:6.532
Before features/support/hooks.rb:269 0.008
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login 1:22.884
Then Tails is running from USB drive "old" 0.362
And I create a persistent partition 31.593
And I take note of which tps features are available 1.976
Then a Tails persistence partition exists on USB drive "old" 0.929
And I shutdown Tails and wait for the computer to power off 8.579
After features/support/hooks.rb:326 0.221
After features/support/hooks.rb:100 0.012
Tags: @product
2:56.083
Before features/support/hooks.rb:269 0.009
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.130
Then Tails is running from USB drive "old" 0.346
And all tps features are active 1.931
When I write some files expected to persist 1.753
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.229
And all persistence configuration files have safe access rights 0.551
And all persistent directories from the old Tails version have safe access rights 2.927
And I take note of which tps features are available 0.458
And I shutdown Tails and wait for the computer to power off 4.442
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.095
After features/support/hooks.rb:326 0.134
After features/support/hooks.rb:100 0.023
Tags: @product
2:39.153
Before features/support/hooks.rb:269 0.011
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 18.701
And I log in to a new session 18.962
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.905
And I plug USB drive "to_upgrade" 2.534
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.773
Then the running Tails is installed on USB drive "to_upgrade" 21.761
And I unplug USB drive "to_upgrade" 0.230
And I unplug USB drive "__internal" 0.284
After features/support/hooks.rb:326 9.613
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.037
Before features/support/hooks.rb:269 0.008
Given a computer 0.240
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.219
Then all tps features from the old Tails version are active 1.609
And Tails is running from USB drive "to_upgrade" 0.398
And the boot device has safe access rights 3.374
And the expected persistent files created with the old Tails version are present in the filesystem 1.547
And all persistent directories from the old Tails version have safe access rights 2.647
After features/support/hooks.rb:326 0.897
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
6:27.259
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.444
And no SquashFS delta is installed 0.111
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.451
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.092
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.384
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.484
When the network is plugged 0.072
And Tor is ready 20.572
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.446
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.176
Given I shutdown Tails and wait for the computer to power off 8.835
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.707
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 4.172
And the file system changes introduced in version 6.2~testoverlayfs are present 0.316
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.333
# 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.270
And Tor is ready 18.420
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.156
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.279
Given I shutdown Tails and wait for the computer to power off 4.348
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.698
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.164
And the file system changes introduced in version 6.3~testoverlayfs are present 0.500
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.323
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.298
When the network is plugged 0.068
And Tor is ready 18.147
Then the Upgrader considers the system as up-to-date 0.334
# 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 15.092
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.097
After features/support/hooks.rb:326 0.758
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
49.748
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 23.419
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.348
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.097
And the signing key used by the Upgrader is outdated 0.803
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 19.816
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.188
After features/support/hooks.rb:326 0.746
After features/support/hooks.rb:100 0.000