From: Keith Seitz <keiths@redhat.com>
To: bunsen@sourceware.org
Subject: Test suite?
Date: Fri, 30 Jul 2021 12:00:58 -0700 [thread overview]
Message-ID: <e7f30c18-58d2-6788-6ea6-351e30f2136d@redhat.com> (raw)
Hi,
I've got a patch (coming soon) for bunsen/repo.py which fixes an exception
that is raised when running summarize.py.
This got me thinking... Bunsen does not yet have a test suite that can
be used to verify correct functioning of the module(s). Is there a procedure
I should follow to make sure I didn't break something else?
Do we have any plans to implement a test suite or any ideas/requirements
on how one should be done? [DejaGNU vs unittest vs pytest, ...]
Keith
reply other threads:[~2021-07-30 19:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=e7f30c18-58d2-6788-6ea6-351e30f2136d@redhat.com \
--to=keiths@redhat.com \
--cc=bunsen@sourceware.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).