public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Implement pytest-based test infrastructure
Date: Thu, 19 Nov 2015 12:09:31 -0700	[thread overview]
Message-ID: <564E1E6B.7010708@wwwdotorg.org> (raw)
In-Reply-To: <564E0030.9090808@wwwdotorg.org>

On 11/19/2015 10:00 AM, Stephen Warren wrote:
> On 11/19/2015 07:45 AM, Simon Glass wrote:
>> Hi Stephen,
>>
>> On 14 November 2015 at 23:53, Stephen Warren <swarren@wwwdotorg.org>
>> wrote:
>>> 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.
>>
>> It's great to see this and thank you for putting in the effort!
>>
>> It looks like a good way of doing functional tests. I still see a role
>> for unit tests and things like test/dm. But if we can arrange to call
>> all U-Boot tests (unit and functional) from one 'test.py' command that
>> would be a win.
>>
>> I'll look more when I can get it to work - see below.
...
> made it print a message about checking the docs for missing
> requirements. I can probably patch the top-level test.py to do the same.

I've pushed such a patch to:

git://github.com/swarren/u-boot.git tegra_dev
(the separate pytests branch has now been deleted)

There are also a variety of other patches there related to this testing 
infra-structure. I guess I'll hold off sending them to the list until 
there's been some general feedback on the patches I've already posted, 
but feel free to pull the branch down and play with it. Note that it's 
likely to get rebased as I work.

  reply	other threads:[~2015-11-19 19:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-15  6:53 [U-Boot] [PATCH] Implement pytest-based test infrastructure Stephen Warren
2015-11-19 14:45 ` Simon Glass
2015-11-19 17:00   ` Stephen Warren
2015-11-19 19:09     ` Stephen Warren [this message]
2015-11-21 16:49       ` Simon Glass
2015-11-22 17:30         ` Stephen Warren
2015-11-24  1:45           ` Simon Glass
2015-11-24  2:18             ` Simon Glass
2015-11-24  4:24               ` Stephen Warren
2015-11-24  4:44             ` Stephen Warren
2015-11-24 19:04               ` Simon Glass
2015-11-24 21:28                 ` Stephen Warren
2015-11-27  2:52                   ` Simon Glass
2015-11-30 17:13                     ` Stephen Warren
2015-12-01 16:40                       ` Simon Glass
2015-12-01 23:24                         ` Stephen Warren
2015-12-02 13:37                           ` Simon Glass
2015-11-23 23:44     ` Tom Rini
2015-11-23 23:55       ` 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=564E1E6B.7010708@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