All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: Simon Glass <sjg@chromium.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
	Walter Lozano <walter.lozano@collabora.com>,
	 Alper Nebi Yasak <alpernebiyasak@gmail.com>
Subject: Re: [PATCH 3/5] patman: test_util: Use unittest text runner to print test results
Date: Tue, 28 Jun 2022 09:38:13 -0400	[thread overview]
Message-ID: <CAPnjgZ3dh55sFOqDYuO_G7RpTb+mYcL1d5aWq=0wHVGZddNRSg@mail.gmail.com> (raw)
In-Reply-To: <CAPnjgZ2xRm7=E1tr19A0xWje35=7H-QULvj7LVa3vP_9FJucaQ@mail.gmail.com>

On Sat, 2 Apr 2022 at 11:06, Alper Nebi Yasak <alpernebiyasak@gmail.com> wrote:
>
> The python tools' test utilities handle printing test results, but the
> output is quite bare compared to an ordinary unittest run. Delegate
> printing the results to a unittest text runner, which gives us niceties
> like clear separation between each test's result and how long it took to
> run the test suite.
>
> Unfortunately it does not print info for skipped tests by default, but
> this can be handled later by a custom test result subclass. It also does
> not print the tool name; manually print a heading that includes the
> toolname so that the outputs of each tool's tests are distinguishable in
> the CI output.
>
> Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
> ---
>
>  tools/binman/main.py      |  8 ++----
>  tools/buildman/main.py    |  8 ++----
>  tools/dtoc/main.py        |  9 +++---
>  tools/dtoc/test_fdt.py    |  8 +++---
>  tools/patman/main.py      |  8 ++----
>  tools/patman/test_util.py | 58 ++++++++++++++-------------------------
>  6 files changed, 38 insertions(+), 61 deletions(-)
>

Reviewed-by: Simon Glass <sjg@chromium.org>

Applied to u-boot-dm, thanks!

  parent reply	other threads:[~2022-06-28 13:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-02 17:06 [PATCH 0/5] patman: test_util: Prettify test report outputs for python tools Alper Nebi Yasak
2022-04-02 17:06 ` [PATCH 1/5] patman: test_util: Fix printing results for failed tests Alper Nebi Yasak
2022-04-19 21:54   ` Simon Glass
2022-06-28 13:38   ` Simon Glass
2022-04-02 17:06 ` [PATCH 2/5] patman: test_util: Handle nonexistent tests while loading tests Alper Nebi Yasak
2022-04-19 21:54   ` Simon Glass
2022-06-28 13:38   ` Simon Glass
2022-04-02 17:06 ` [PATCH 3/5] patman: test_util: Use unittest text runner to print test results Alper Nebi Yasak
2022-04-19 21:54   ` Simon Glass
2022-06-28 13:38   ` Simon Glass [this message]
2022-04-02 17:06 ` [PATCH 4/5] patman: test_util: Customize unittest test results for more info Alper Nebi Yasak
2022-04-02 17:06 ` [PATCH 5/5] patman: test_util: Print test stdout/stderr within test summaries Alper Nebi Yasak
2022-04-19 21:54   ` Simon Glass
2022-06-28 13:38   ` Simon Glass
2022-06-28 13:38 ` [PATCH 4/5] patman: test_util: Customize unittest test results for more info Simon Glass

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='CAPnjgZ3dh55sFOqDYuO_G7RpTb+mYcL1d5aWq=0wHVGZddNRSg@mail.gmail.com' \
    --to=sjg@chromium.org \
    --cc=alpernebiyasak@gmail.com \
    --cc=u-boot@lists.denx.de \
    --cc=walter.lozano@collabora.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.