mirror of
https://github.com/u-boot/u-boot.git
synced 2025-04-24 06:24:17 +00:00
752c376987
This fixture name is quite long and results in lots of verbose code. We know this is U-Boot so the 'u_boot_' part is not necessary. But it is also a bit of a misnomer, since it provides access to all the information available to tests. It is not just the console. It would be too confusing to use con as it would be confused with config and it is probably too short. So shorten it to 'ubman'. Signed-off-by: Simon Glass <sjg@chromium.org> Link: https://lore.kernel.org/u-boot/CAFLszTgPa4aT_J9h9pqeTtLCVn4x2JvLWRcWRD8NaN3uoSAtyA@mail.gmail.com/
26 lines
846 B
Python
26 lines
846 B
Python
# SPDX-License-Identifier: GPL-2.0+
|
|
# Copyright (c) 2021, Asherah Connor <ashe@kivikakk.ee>
|
|
|
|
# Test qfw command implementation
|
|
|
|
import pytest
|
|
|
|
@pytest.mark.buildconfigspec('cmd_qfw')
|
|
def test_qfw_cpus(ubman):
|
|
"Test QEMU firmware config reports the CPU count."
|
|
|
|
output = ubman.run_command('qfw cpus')
|
|
# The actual number varies depending on the board under test, so only
|
|
# assert a non-zero output.
|
|
assert 'cpu(s) online' in output
|
|
assert '0 cpu(s) online' not in output
|
|
|
|
@pytest.mark.buildconfigspec('cmd_qfw')
|
|
def test_qfw_list(ubman):
|
|
"Test QEMU firmware config lists devices."
|
|
|
|
output = ubman.run_command('qfw list')
|
|
# Assert either:
|
|
# 1) 'test-one', from the sandbox driver, or
|
|
# 2) 'bootorder', found in every real QEMU implementation.
|
|
assert ("bootorder" in output) or ("test-one" in output)
|