diff options
| author | Simon Glass <sjg@chromium.org> | 2016-07-03 09:40:34 -0600 |
|---|---|---|
| committer | Tom Rini <trini@konsulko.com> | 2016-07-14 18:22:32 -0400 |
| commit | 07f4eadc99b365fa92114f19c02218ff39c45ed9 (patch) | |
| tree | bdd5536eb6d17cd19227c9b2fbc7290880a00f0d /test | |
| parent | f6349c3c4cd334148637c83bcfb6017b195102f5 (diff) | |
| download | u-boot-imx-07f4eadc99b365fa92114f19c02218ff39c45ed9.zip u-boot-imx-07f4eadc99b365fa92114f19c02218ff39c45ed9.tar.gz u-boot-imx-07f4eadc99b365fa92114f19c02218ff39c45ed9.tar.bz2 | |
test: Add a simple script to run tests on sandbox
A common check before sending patches is to run all available tests on
sandbox. But everytime I do this I have to look up the README. This presents
quite a barrier to actually doing this.
Add a shell script to help. To run the tests, type:
test/run
in the U-Boot directory, which should be easy to remember.
Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Teddy Reed <teddy.reed@gmail.com>
Diffstat (limited to 'test')
| -rw-r--r-- | test/README | 11 | ||||
| -rwxr-xr-x | test/run | 4 |
2 files changed, 15 insertions, 0 deletions
diff --git a/test/README b/test/README index dfd83d6..6cfee05 100644 --- a/test/README +++ b/test/README @@ -5,6 +5,17 @@ U-Boot has a large amount of code. This file describes how this code is tested and what tests you should write when adding a new feature. +Running tests +------------- + +To run most tests on sandbox, type this: + + test/run + +in the U-Boot directory. Note that only the pytest suite is run using this +comment. + + Sandbox ------- U-Boot can be built as a user-space application (e.g. for Linux). This diff --git a/test/run b/test/run new file mode 100755 index 0000000..a6dcf8f --- /dev/null +++ b/test/run @@ -0,0 +1,4 @@ +#!/bin/sh + +# Run all tests +./test/py/test.py --bd sandbox --build |