From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Simon South <simon@simonsouth.net>
Cc: Nathan Dehnel <ncdehnel@gmail.com>, guix-devel@gnu.org
Subject: Re: How to test modified shepherd services
Date: Sun, 26 Dec 2021 22:20:21 -0500 [thread overview]
Message-ID: <8735meybre.fsf@gmail.com> (raw)
In-Reply-To: <87ee67s718.fsf@simonsouth.net> (Simon South's message of "Mon, 20 Dec 2021 09:08:35 -0500")
Hello,
Simon South <simon@simonsouth.net> writes:
> Nathan Dehnel <ncdehnel@gmail.com> writes:
>> I modified a shepherd service to accept a new field from config.scm
>> and I was wondering how to test that it works correctly.
>
> Assuming this is an existing Guix service, it's probably easiest to
> update the corresponding system test suite under gnu/tests (if
> necessary) to reflect your change, then run the suite with "make
> check-system" (setting "TESTS" to limit it to the service in question)
> to make sure everything works the way you expect.
>
> If you're planning on contributing the change to Guix it would be good
> to submit it along with an updated test suite anyway.
>
> The Guix manual has a bit of information about this in Section 2.3,
> "Running the Test Suite":
>
> https://guix.gnu.org/en/manual/en/html_node/Running-the-Test-Suite.html#Running-the-Test-Suite
+1. System tests are the best way to validate system services. You'll
save time by writing/extending one.
Maxim
prev parent reply other threads:[~2021-12-27 3:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-19 22:47 How to test modified shepherd services Nathan Dehnel
2021-12-20 3:28 ` raingloom
2021-12-20 10:00 ` Attila Lendvai
2021-12-20 22:38 ` Nathan Dehnel
2021-12-20 14:08 ` Simon South
2021-12-27 3:20 ` Maxim Cournoyer [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8735meybre.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ncdehnel@gmail.com \
--cc=simon@simonsouth.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).