Project Number Date
test_Tails_ISO_devel 3578 05 Nov 2024, 13:07

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:35.838 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.304
Before features/support/hooks.rb:269 0.010
Given a computer 0.238
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 32.137
When I start Tails from USB drive "old" with network unplugged 1:46.684
Then the boot device has safe access rights 3.084
And Tails is running from USB drive "old" 0.385
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.302
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:326 3.777
After features/support/hooks.rb:100 0.011
Tags: @product
2:15.198
Before features/support/hooks.rb:269 0.009
Given a computer 0.259
And I start Tails from USB drive "old" with network unplugged and I login 1:31.018
Then Tails is running from USB drive "old" 0.358
And I create a persistent partition 32.084
And I take note of which tps features are available 1.920
Then a Tails persistence partition exists on USB drive "old" 0.853
And I shutdown Tails and wait for the computer to power off 8.703
After features/support/hooks.rb:326 0.145
After features/support/hooks.rb:100 0.011
Tags: @product
3:4.178
Before features/support/hooks.rb:269 0.007
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.131
Then Tails is running from USB drive "old" 0.499
And all tps features are active 2.286
When I write some files expected to persist 2.360
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.263
And all persistence configuration files have safe access rights 0.436
And all persistent directories from the old Tails version have safe access rights 2.754
And I take note of which tps features are available 0.472
And I shutdown Tails and wait for the computer to power off 4.188
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.598
After features/support/hooks.rb:326 0.163
After features/support/hooks.rb:100 0.017
Tags: @product
2:35.641
Before features/support/hooks.rb:269 0.013
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.038
And I log in to a new session 19.205
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.759
And I plug USB drive "to_upgrade" 2.446
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.886
Then the running Tails is installed on USB drive "to_upgrade" 23.476
And I unplug USB drive "to_upgrade" 0.220
And I unplug USB drive "__internal" 0.606
After features/support/hooks.rb:326 8.155
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.058
Before features/support/hooks.rb:269 0.008
Given a computer 0.228
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.444
Then all tps features from the old Tails version are active 1.813
And Tails is running from USB drive "to_upgrade" 0.355
And the boot device has safe access rights 3.628
And the expected persistent files created with the old Tails version are present in the filesystem 1.677
And all persistent directories from the old Tails version have safe access rights 2.910
After features/support/hooks.rb:326 0.940
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
7:13.855
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 14.019
And no SquashFS delta is installed 0.183
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.441
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.100
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.331
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.548
When the network is plugged 0.071
And Tor is ready 23.003
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.193
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.942
Given I shutdown Tails and wait for the computer to power off 11.523
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.578
Then Tails is running version 6.2~testoverlayfs 0.030
And all tps features are active 2.423
And the file system changes introduced in version 6.2~testoverlayfs are present 0.341
And only the 6.2~testoverlayfs SquashFS delta is installed 0.096
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.514
# 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.397
When the network is plugged 0.096
And Tor is ready 47.330
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.641
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.010
Given I shutdown Tails and wait for the computer to power off 4.542
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.262
Then Tails is running version 6.3~testoverlayfs 0.026
And all tps features are active 2.380
And the file system changes introduced in version 6.3~testoverlayfs are present 0.646
And only the 6.3~testoverlayfs SquashFS delta is installed 0.140
# 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.541
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.329
When the network is plugged 0.102
And Tor is ready 20.940
Then the Upgrader considers the system as up-to-date 0.370
# 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.632
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.119
After features/support/hooks.rb:326 0.771
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
39.601
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 12.528
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.489
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.621
And the signing key used by the Upgrader is outdated 0.988
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 18.073
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.826
After features/support/hooks.rb:326 1.555
After features/support/hooks.rb:100 0.000