From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] support/testing: test_audio_codec_base.py: new helper class
Date: Wed, 7 Aug 2024 23:20:16 +0200 [thread overview]
Message-ID: <20240807232016.6ea6cd1e@windsurf> (raw)
In-Reply-To: <e238dc68395d1c1cf415d9f133dae262@free.fr>
Hello,
On Wed, 07 Aug 2024 23:09:00 +0200
Julien Olivain <ju.o@free.fr> wrote:
> I think the reason the test gets registered many times is because the
> "abstract" class contains a test_run() function. The way nose2 scans
> for test will search in all the class hierarchy. The only way to
> prevent that for now is the __test__ = False.
>
> We can see the selection of test if we add debug in nose2 discovery:
>
> nose2.discover(argv=[script_path,
> "-s", test_dir,
> "-v",
> "--collect-only",
> "--log-level", "debug"],
> plugins=["nose2.plugins.collect"])
>
> in support/testing/run-tests, and invoking with "run-tests -l".
>
> The reason I've put a test_run() function in the abstract class is
> because
> I would like to keep the same test sequence for all those audio tests.
Right, and I think it makes sense.
> Maybe nose2 discovery should not recurse in the class hierarchy? The
> only
> way I to prevent that would be to modify the loader at:
> https://github.com/nose-devs/nose2/blob/main/nose2/plugins/loader/discovery.py
>
> Would you like me to propose a change of this nose2 behavior?
No strong opinion. I'm not particularly attached to nose2. I think
someone mentioned pytest as an alternative?
I don't know if nose2 is still actively developed, if it makes sense to
"invest" in this compared to some other solutions.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-08-07 21:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-15 9:16 [Buildroot] [PATCH 1/2] support/testing: test_audio_codec_base.py: new helper class Julien Olivain
2024-06-15 9:16 ` [Buildroot] [PATCH 2/2] support/testing: add lame runtime test Julien Olivain
2024-06-15 18:09 ` [Buildroot] [PATCH 1/2] support/testing: test_audio_codec_base.py: new helper class Yann E. MORIN
2024-06-21 14:40 ` Julien Olivain
2024-08-07 19:35 ` Thomas Petazzoni via buildroot
2024-08-07 21:09 ` Julien Olivain
2024-08-07 21:20 ` Thomas Petazzoni via buildroot [this message]
2024-08-06 21:24 ` Thomas Petazzoni via buildroot
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=20240807232016.6ea6cd1e@windsurf \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.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