Project Number Date
test_Tails_ISO_devel 3353 17 Apr 2024, 12:17

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:30.253 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:42.405
Before features/support/hooks.rb:259 0.007
Given a computer 0.228
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 23.048
When I start Tails from USB drive "old" with network unplugged 1:14.138
Then the boot device has safe access rights 2.898
And Tails is running from USB drive "old" 0.373
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.285
And I unplug USB drive "old" 0.177
After features/support/hooks.rb:305 3.572
After features/support/hooks.rb:89 0.014
Tags: @product
2:1.260
Before features/support/hooks.rb:259 0.007
Given a computer 0.171
And I start Tails from USB drive "old" with network unplugged and I login 1:14.556
Then Tails is running from USB drive "old" 0.316
And I create a persistent partition 35.390
And I take note of which tps features are available 1.451
Then a Tails persistence partition exists on USB drive "old" 0.908
And I shutdown Tails and wait for the computer to power off 8.465
After features/support/hooks.rb:305 0.201
After features/support/hooks.rb:89 0.010
Tags: @product
2:30.442
Before features/support/hooks.rb:259 0.005
Given a computer 0.169
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:2.351
Then Tails is running from USB drive "old" 0.352
And all tps features are active 1.847
When I write some files expected to persist 1.615
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.231
And all persistence configuration files have safe access rights 0.402
And all persistent directories from the old Tails version have safe access rights 2.669
And I take note of which tps features are available 0.443
And I shutdown Tails and wait for the computer to power off 4.167
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.191
After features/support/hooks.rb:305 0.164
After features/support/hooks.rb:89 0.009
Tags: @product
2:20.010
Before features/support/hooks.rb:259 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.556
And I log in to a new session 17.941
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.476
And I plug USB drive "to_upgrade" 2.452
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.149
Then the running Tails is installed on USB drive "to_upgrade" 16.049
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.177
After features/support/hooks.rb:305 1.801
After features/support/hooks.rb:89 0.000
Tags: @product
2:11.932
Before features/support/hooks.rb:259 0.007
Given a computer 0.177
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.595
Then all tps features from the old Tails version are active 1.957
And Tails is running from USB drive "to_upgrade" 0.323
And the boot device has safe access rights 3.221
And the expected persistent files created with the old Tails version are present in the filesystem 1.817
And all persistent directories from the old Tails version have safe access rights 2.839
After features/support/hooks.rb:305 1.576
After features/support/hooks.rb:89 0.012
Tags: @product @automatic_upgrade
7:12.298
Before features/support/hooks.rb:259 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 30.652
And no SquashFS delta is installed 0.179
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.391
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.364
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.507
When the network is plugged 0.047
And Tor is ready 19.900
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.582
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.806
Given I shutdown Tails and wait for the computer to power off 1:7.004
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.499
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.949
And the file system changes introduced in version 6.2~testoverlayfs are present 0.273
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.309
# 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.259
When the network is plugged 0.039
And Tor is ready 14.206
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.315
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.022
Given I shutdown Tails and wait for the computer to power off 4.459
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.709
Then Tails is running version 6.3~testoverlayfs 0.024
And all tps features are active 1.945
And the file system changes introduced in version 6.3~testoverlayfs are present 0.429
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.305
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.262
When the network is plugged 0.046
And Tor is ready 17.944
Then the Upgrader considers the system as up-to-date 0.234
# 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.446
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.945
After features/support/hooks.rb:305 0.704
After features/support/hooks.rb:89 0.059
Tags: @product @automatic_upgrade
31.903
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.707
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.380
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.084
And the signing key used by the Upgrader is outdated 0.486
But a current signing key is available on our website 0.000
When the network is plugged 0.103
And Tor is ready 15.913
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.227
After features/support/hooks.rb:305 0.631
After features/support/hooks.rb:89 0.000