Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: ricardo.martincoski@gmail.com
To: romain.naour@smile.fr
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH-next 1/4] utils/checkpackagelib: add unit tests
Date: Mon, 10 Jan 2022 19:42:07 -0300	[thread overview]
Message-ID: <61dcb63fc08f3_8fcf9ec-3fa@xultri.mail> (raw)
In-Reply-To: 30b13507-5744-de89-0e04-503e264bc1e5@smile.fr

[-- Attachment #1: Type: text/plain, Size: 1469 bytes --]

Hello Romain,

On Sat, Jan 08, 2022 at 07:37 PM, Romain Naour wrote:

> Hello Ricardo,
> 
> Le 05/12/2021 à 11:53, Ricardo Martincoski a écrit :
>> So anyone willing to contribute to check-package can run all tests in
>> less than 1 second by using:
>> $ python3 -m pytest -v utils/checkpackagelib/
>> 
>> Most test cases are in the form:
>> @pytest.mark.parametrize('testname,filename,string,expected', function)
>>  - testname: a short description of the scenario tested, added in order
>>    to improve readability of the log when some tests fail
>>  - filename: the filename the check-package function being tested thinks
>>    it is testing
>>  - string: the content of the file being sent to the function under test
>>  - expect: all expected warnings that a given function from
>>    check-package should generate for a given file named filename and
>>    with string as its content.
> 
> I spend some time to review this patch to find something to say :)

Thank you for your time.
I imagine how boring was to review this patch :)

> 
> Actually the test_lib_hash tests are not checking with the new spacing
> convention we want to use in .hash files.
> 
> I applied this patch [1] after your series and some tests failed.

Now it landed on master.

> 
> I would recommand to use the new spacing convention by default in this testsuite.

Sure. I will send v2.

Regards,
Ricardo

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-01-10 22:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-05 10:53 [Buildroot] [PATCH-next 1/4] utils/checkpackagelib: add unit tests Ricardo Martincoski
2021-12-05 10:53 ` [Buildroot] [PATCH-next 2/4] support/docker: add python3-pytest Ricardo Martincoski
2022-01-09 10:51   ` Romain Naour
2021-12-05 10:53 ` [Buildroot] [PATCH-next 3/4] utils/checkpackagelib: run unit tests on GitLab CI Ricardo Martincoski
2021-12-05 10:53 ` [Buildroot] [PATCH-next 4/4] utils/docker-run: new script Ricardo Martincoski
2022-01-08 22:37 ` [Buildroot] [PATCH-next 1/4] utils/checkpackagelib: add unit tests Romain Naour
2022-01-10 22:42   ` ricardo.martincoski [this message]

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=61dcb63fc08f3_8fcf9ec-3fa@xultri.mail \
    --to=ricardo.martincoski@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=romain.naour@smile.fr \
    /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