Extend reset tests to cover both -c/-w 'reset' command flags. Make sure sandbox reset tests are passing.
Signed-off-by: Denis Mukhin <[email protected]> --- Changes since v3: - switch to ' strings in the pytest --- test/py/tests/test_reset.py | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/test/py/tests/test_reset.py b/test/py/tests/test_reset.py index af079a706647..7a12fe5f73c3 100644 --- a/test/py/tests/test_reset.py +++ b/test/py/tests/test_reset.py @@ -52,12 +52,12 @@ def test_reset(ubman): test_000_version.test_version(ubman) @pytest.mark.buildconfigspec('hush_parser') -def test_reset_w(ubman): - """Test the reset -w command in non-JTAG bootmode. - It does WARM reset, which resets CPU but keep DDR/peripherals active. [email protected]('reset_type', ['c', 'w']) +def test_reset_type(ubman, reset_type): + """Test the reset {-c|-w} command in non-JTAG bootmode. """ setup_reset_env(ubman) - ubman.run_command('reset -w', wait_for_reboot=True) + ubman.run_command('reset -' + reset_type, wait_for_reboot=True) # Checks the u-boot command prompt's functionality after reset test_000_version.test_version(ubman) -- 2.54.0
