Project Number Date
test_Tails_ISO_devel 3514 12 Sep 2024, 12:52

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:0.169 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:10.613
Before features/support/hooks.rb:269 0.006
Given a computer 0.863
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 34.091
When I start Tails from USB drive "old" with network unplugged 1:30.709
Then the boot device has safe access rights 2.868
And Tails is running from USB drive "old" 0.322
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.293
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:326 3.569
After features/support/hooks.rb:100 0.013
Tags: @product
2:4.215
Before features/support/hooks.rb:269 0.006
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:21.579
Then Tails is running from USB drive "old" 0.314
And I create a persistent partition 31.593
And I take note of which tps features are available 1.435
Then a Tails persistence partition exists on USB drive "old" 0.821
And I shutdown Tails and wait for the computer to power off 8.280
After features/support/hooks.rb:326 0.163
After features/support/hooks.rb:100 0.009
Tags: @product
2:51.877
Before features/support/hooks.rb:269 0.008
Given a computer 0.215
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.479
Then Tails is running from USB drive "old" 0.333
And all tps features are active 2.128
When I write some files expected to persist 1.659
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.222
And all persistence configuration files have safe access rights 0.440
And all persistent directories from the old Tails version have safe access rights 2.469
And I take note of which tps features are available 0.444
And I shutdown Tails and wait for the computer to power off 4.283
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.200
After features/support/hooks.rb:326 0.109
After features/support/hooks.rb:100 0.010
Tags: @product
2:33.988
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.030
And I log in to a new session 22.469
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.506
And I plug USB drive "to_upgrade" 2.449
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.253
Then the running Tails is installed on USB drive "to_upgrade" 20.876
And I unplug USB drive "to_upgrade" 0.200
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:326 2.111
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.279
Before features/support/hooks.rb:269 0.006
Given a computer 0.185
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.902
Then all tps features from the old Tails version are active 1.712
And Tails is running from USB drive "to_upgrade" 0.276
And the boot device has safe access rights 3.144
And the expected persistent files created with the old Tails version are present in the filesystem 1.539
And all persistent directories from the old Tails version have safe access rights 2.519
After features/support/hooks.rb:326 0.969
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:20.878
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.729
And no SquashFS delta is installed 0.197
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.329
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.292
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.556
When the network is plugged 0.062
And Tor is ready 24.096
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.486
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.274
Given I shutdown Tails and wait for the computer to power off 8.358
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.729
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.179
And the file system changes introduced in version 6.2~testoverlayfs are present 0.301
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.313
# 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.272
When the network is plugged 0.071
And Tor is ready 17.441
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.505
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.756
Given I shutdown Tails and wait for the computer to power off 4.294
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.389
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.132
And the file system changes introduced in version 6.3~testoverlayfs are present 0.475
And only the 6.3~testoverlayfs SquashFS delta is installed 0.091
# 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.314
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.300
When the network is plugged 0.071
And Tor is ready 17.161
Then the Upgrader considers the system as up-to-date 10.825
# 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 13.819
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.881
After features/support/hooks.rb:326 0.747
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
39.317
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.178
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.358
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 0.870
But a current signing key is available on our website 0.000
When the network is plugged 0.122
And Tor is ready 21.208
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.510
After features/support/hooks.rb:326 1.381
After features/support/hooks.rb:100 0.000