Project Number Date
test_Tails_ISO_devel 3585 13 Nov 2024, 12:54

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:33.501 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
1:54.234
Before features/support/hooks.rb:269 0.006
Given a computer 0.173
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 29.205
When I start Tails from USB drive "old" with network unplugged 1:19.977
Then the boot device has safe access rights 2.822
And Tails is running from USB drive "old" 0.316
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.282
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:326 3.507
After features/support/hooks.rb:100 0.049
Tags: @product
2:12.093
Before features/support/hooks.rb:269 0.006
Given a computer 0.239
And I start Tails from USB drive "old" with network unplugged and I login 1:28.425
Then Tails is running from USB drive "old" 0.344
And I create a persistent partition 32.431
And I take note of which tps features are available 1.482
Then a Tails persistence partition exists on USB drive "old" 0.823
And I shutdown Tails and wait for the computer to power off 8.345
After features/support/hooks.rb:326 0.177
After features/support/hooks.rb:100 0.009
Tags: @product
2:46.289
Before features/support/hooks.rb:269 0.006
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.291
Then Tails is running from USB drive "old" 0.340
And all tps features are active 1.872
When I write some files expected to persist 1.636
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.349
And all persistence configuration files have safe access rights 0.427
And all persistent directories from the old Tails version have safe access rights 2.451
And I take note of which tps features are available 0.377
And I shutdown Tails and wait for the computer to power off 4.299
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.056
After features/support/hooks.rb:326 0.103
After features/support/hooks.rb:100 0.009
Tags: @product
2:27.404
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.931
And I log in to a new session 18.014
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.808
And I plug USB drive "to_upgrade" 2.428
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.451
Then the running Tails is installed on USB drive "to_upgrade" 20.378
And I unplug USB drive "to_upgrade" 0.192
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:326 2.328
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.608
Before features/support/hooks.rb:269 0.006
Given a computer 0.167
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.738
Then all tps features from the old Tails version are active 1.536
And Tails is running from USB drive "to_upgrade" 0.428
And the boot device has safe access rights 3.160
And the expected persistent files created with the old Tails version are present in the filesystem 1.330
And all persistent directories from the old Tails version have safe access rights 2.247
After features/support/hooks.rb:326 0.852
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:21.884
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.615
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.457
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.260
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.434
When the network is plugged 0.065
And Tor is ready 26.157
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.423
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.517
Given I shutdown Tails and wait for the computer to power off 10.646
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.092
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 1.892
And the file system changes introduced in version 6.2~testoverlayfs are present 0.399
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.341
# 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.264
When the network is plugged 0.076
And Tor is ready 19.720
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.095
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.308
Given I shutdown Tails and wait for the computer to power off 4.242
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.410
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.831
And the file system changes introduced in version 6.3~testoverlayfs are present 0.444
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.400
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.356
When the network is plugged 0.080
And Tor is ready 15.354
Then the Upgrader considers the system as up-to-date 0.287
# 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.449
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.974
After features/support/hooks.rb:326 0.724
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
41.987
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.328
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.337
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.112
And the signing key used by the Upgrader is outdated 0.719
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 23.248
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.169
After features/support/hooks.rb:326 0.671
After features/support/hooks.rb:100 0.000