From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2 1/7] test/py: Implement pytest infrastructure
Date: Mon, 7 Dec 2015 14:51:26 -0700 [thread overview]
Message-ID: <5665FF5E.2010502@wwwdotorg.org> (raw)
In-Reply-To: <565FE567.1070909@denx.de>
On 12/02/2015 11:47 PM, Heiko Schocher wrote:
> Hello Stephen,
>
> Am 02.12.2015 um 23:18 schrieb Stephen Warren:
>> This tool aims to test U-Boot by executing U-Boot shell commands using
>> the
>> console interface. A single top-level script exists to execute or attach
>> to the U-Boot console, run the entire script of tests against it, and
>> summarize the results. Advantages of this approach are:
>>
>> - Testing is performed in the same way a user or script would interact
>> with U-Boot; there can be no disconnect.
>> - There is no need to write or embed test-related code into U-Boot
>> itself.
>> It is asserted that writing test-related code in Python is simpler and
>> more flexible that writing it all in C.
>> - It is reasonably simple to interact with U-Boot in this way.
>>
>> A few simple tests are provided as examples. Soon, we should convert as
>> many as possible of the other tests in test/* and test/cmd_ut.c too.
>>
>> In the future, I hope to publish (out-of-tree) the hook scripts, relay
>> control utilities, and udev rules I will use for my own HW setup.
>>
>> See README.md for more details!
>>
>> Signed-off-by: Stephen Warren <swarren@wwwdotorg.org>
>> Signed-off-by: Stephen Warren <swarren@nvidia.com>
>> ---
>
> Nice work!
>
> I am working on another python approach, not only good for testing
> u-boot, also works with linux, or other console based tests, see:
>
> [1] tbot
> https://github.com/hsdenx/tbot
That looks nice too.
I assume the scope there is too large to aim at inclusion into the
U-Boot source tree, since it also aims at Linux testing too?
next prev parent reply other threads:[~2015-12-07 21:51 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 22:18 [U-Boot] [PATCH V2 1/7] test/py: Implement pytest infrastructure Stephen Warren
2015-12-02 22:18 ` [U-Boot] [PATCH V2 2/7] test/py: test that sandbox exits when asked Stephen Warren
2015-12-19 22:24 ` Simon Glass
2015-12-02 22:18 ` [U-Boot] [PATCH V2 3/7] test/py: add test of setenv/printenv/echo Stephen Warren
2015-12-18 13:50 ` Michal Simek
2015-12-18 18:09 ` Stephen Warren
2016-01-04 8:36 ` Michal Simek
2015-12-19 22:24 ` Simon Glass
2015-12-02 22:18 ` [U-Boot] [PATCH V2 4/7] test/py: test the md/mw commands Stephen Warren
2015-12-18 13:51 ` Michal Simek
2015-12-18 18:15 ` Stephen Warren
2015-12-19 22:24 ` Simon Glass
2015-12-02 22:18 ` [U-Boot] [PATCH V2 5/7] test/py: add test of basic shell functionality Stephen Warren
2015-12-19 22:24 ` Simon Glass
2015-12-02 22:18 ` [U-Boot] [PATCH V2 6/7] test/py: test the shell if command Stephen Warren
2015-12-19 22:24 ` Simon Glass
2016-01-04 21:18 ` Stephen Warren
2015-12-02 22:18 ` [U-Boot] [PATCH V2 7/7] test/py: test the ums command Stephen Warren
2015-12-19 22:24 ` Simon Glass
2016-01-04 21:19 ` Stephen Warren
2015-12-03 6:47 ` [U-Boot] [PATCH V2 1/7] test/py: Implement pytest infrastructure Heiko Schocher
2015-12-07 21:51 ` Stephen Warren [this message]
2015-12-08 5:42 ` Heiko Schocher
2015-12-09 16:32 ` Stephen Warren
2015-12-16 15:11 ` Michal Simek
2015-12-16 16:27 ` Stephen Warren
2015-12-16 17:43 ` Michal Simek
2015-12-16 18:09 ` Stephen Warren
2015-12-16 18:32 ` Michal Simek
2015-12-16 18:41 ` Stephen Warren
2015-12-18 14:50 ` Michal Simek
2015-12-18 18:33 ` Stephen Warren
2015-12-18 22:36 ` Stephen Warren
2016-01-04 8:50 ` Michal Simek
2016-01-04 12:41 ` Michal Simek
2016-01-04 20:34 ` Stephen Warren
2015-12-17 5:45 ` Heiko Schocher
2016-01-14 23:12 ` Simon Glass
2016-01-16 6:29 ` [U-Boot] U-Boot: using tbot for U-Boot tests was: " Heiko Schocher
2016-01-19 3:42 ` Simon Glass
2016-01-19 11:42 ` Heiko Schocher
2015-12-19 22:24 ` [U-Boot] " Simon Glass
2016-01-04 21:16 ` Stephen Warren
2016-01-04 22:23 ` Stephen Warren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5665FF5E.2010502@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).