Project Number Date
test_Tails_ISO_devel 3457 11 Jul 2024, 15:39

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:26.743 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:4.494
Before features/support/hooks.rb:269 0.010
Given a computer 0.241
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 31.970
When I start Tails from USB drive "old" with network unplugged 1:27.244
Then the boot device has safe access rights 2.969
And Tails is running from USB drive "old" 0.351
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.284
And I unplug USB drive "old" 0.184
After features/support/hooks.rb:326 3.498
After features/support/hooks.rb:100 0.024
Tags: @product
2:11.948
Before features/support/hooks.rb:269 0.008
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login 1:29.544
Then Tails is running from USB drive "old" 0.343
And I create a persistent partition 31.077
And I take note of which tps features are available 1.652
Then a Tails persistence partition exists on USB drive "old" 0.827
And I shutdown Tails and wait for the computer to power off 8.288
After features/support/hooks.rb:326 0.180
After features/support/hooks.rb:100 0.012
Tags: @product
2:48.123
Before features/support/hooks.rb:269 0.008
Given a computer 0.220
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.337
Then Tails is running from USB drive "old" 0.320
And all tps features are active 1.982
When I write some files expected to persist 1.724
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.243
And all persistence configuration files have safe access rights 0.394
And all persistent directories from the old Tails version have safe access rights 2.428
And I take note of which tps features are available 0.428
And I shutdown Tails and wait for the computer to power off 4.282
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.760
After features/support/hooks.rb:326 0.139
After features/support/hooks.rb:100 0.011
Tags: @product
2:36.077
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 11.615
And I log in to a new session 18.950
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.577
And I plug USB drive "to_upgrade" 2.381
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.729
Then the running Tails is installed on USB drive "to_upgrade" 19.414
And I unplug USB drive "to_upgrade" 0.218
And I unplug USB drive "__internal" 0.189
After features/support/hooks.rb:326 2.444
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.256
Before features/support/hooks.rb:269 0.008
Given a computer 0.957
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.484
Then all tps features from the old Tails version are active 1.525
And Tails is running from USB drive "to_upgrade" 0.287
And the boot device has safe access rights 3.185
And the expected persistent files created with the old Tails version are present in the filesystem 1.365
And all persistent directories from the old Tails version have safe access rights 2.450
After features/support/hooks.rb:326 0.718
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
6:51.874
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 11.866
And no SquashFS delta is installed 0.127
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.399
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.284
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.462
When the network is plugged 0.045
And Tor is ready 48.381
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.676
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.929
Given I shutdown Tails and wait for the computer to power off 9.047
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.239
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.398
And the file system changes introduced in version 6.2~testoverlayfs are present 0.319
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.350
# 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.251
When the network is plugged 0.244
And Tor is ready 18.830
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.304
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.553
Given I shutdown Tails and wait for the computer to power off 4.534
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.374
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.243
And the file system changes introduced in version 6.3~testoverlayfs are present 0.526
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.337
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.300
When the network is plugged 0.051
And Tor is ready 16.674
Then the Upgrader considers the system as up-to-date 10.831
# 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.188
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.859
After features/support/hooks.rb:326 0.803
After features/support/hooks.rb:100 0.063
Tags: @product @automatic_upgrade
39.967
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.226
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.396
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.814
But a current signing key is available on our website 0.000
When the network is plugged 0.044
And Tor is ready 21.577
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.857
After features/support/hooks.rb:326 0.679
After features/support/hooks.rb:100 0.000