bcm63xx/u-boot/test/README, branch master

test: Add a 'make qcheck' target for quicker testing

2018-11-29T16:30:05Z

At present tests are quite slow to run, over a minute on my machine. This presents a considerable barrier to bisecting for failures. The slowest tests are the filesystem ones and the buildman --fetch-arch test. Add a new 'qcheck' target that skips these tests. This reduces test time down to about 40 second, still too long, but bearable. Signed-off-by: Simon Glass

tools/tbot: update README

2017-06-12T12:38:44Z

refer in the README to tbots webpage, and delete the README in tools/tbot, as the latest documentation for tbot is on this webpage. Signed-off-by: Heiko Schocher

test: Fix typos and tidy up

2016-08-06T00:55:19Z

Fix review comments that were missed at the time. Also explain why we need to regenerate the device tree for each test. Reported-by: Teddy Reed Suggested-by: Stephen Warren Signed-off-by: Simon Glass Fixes: f6349c3c (test: Add a README)

test: Convert the vboot test to test/py

2016-07-14T22:22:40Z

Now that we have a suitable test framework we should move all tests into it. The vboot test is a suitable candidate. Rewrite it in Python and move the data files into an appropriate directory. Signed-off-by: Simon Glass

test: Add a simple script to run tests on sandbox

2016-07-14T22:22:32Z

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 Reviewed-by: Teddy Reed

test: Add a README

2016-07-14T22:22:31Z

Add a few notes about how testing works in U-Boot. Signed-off-by: Simon Glass Reviewed-by: Teddy Reed