From: Joshua Brindle <method@manicmethod.com>
To: Jeff Johnson <n3npq@mac.com>
Cc: Chad Sellers <csellers@tresys.com>,
SE Linux <selinux@tycho.nsa.gov>,
James Carter <jwcart2@tycho.nsa.gov>,
Eamon Walsh <ewalsh@tycho.nsa.gov>,
Stephen Smalley <sds@tycho.nsa.gov>,
Stephen Lawrence <slawrence@tresys.com>
Subject: Re: Unit testing userspace
Date: Tue, 14 Dec 2010 15:28:24 -0500 [thread overview]
Message-ID: <4D07D368.5050104@manicmethod.com> (raw)
In-Reply-To: <40341D7F-2276-4DFD-9380-AAE56F81C343@mac.com>
Jeff Johnson wrote:
> On Dec 14, 2010, at 2:07 PM, Chad Sellers wrote:
>> Note that we've been using CuTest in CIL, and it is very simple and easy to
>> use. There's almost no spin up to using it.
>>
>
> Try the ISPRAS api-sanity-autotest.pl (same people doing LSB testing).
If CIL is already using cutest that would be helpful. AFAIK Perl isn't installed
by default on fedora or gentoo, and we'd want to have the tests run in the
default make target in a clean build environment (for RPM builds and such). FWIW
I discounted other test frameworks outright because they use ruby or other
non-default packages.
>
> There is zero spin-up to shallow testing using ISPRAS, and some modest thought
> writing some XML templates can go a long ways towards reasonable
> unit testing with significant coverage.
>
> OTOH, if you truly need mocking with symbol replacemnet, well ... good luck! That's hard.
>
test-dept does mocking with symbol replacement and all that. Yes it is hard (not
nearly as hard as doing it without something like test-dept) but Chad may be
right, it could be just too hard to encourage unit tests to be written.
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2010-12-14 20:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 19:59 Unit testing userspace Joshua Brindle
2010-12-14 19:07 ` Chad Sellers
2010-12-14 19:21 ` Jeff Johnson
2010-12-14 20:28 ` Joshua Brindle [this message]
2010-12-15 8:17 ` Michal Svoboda
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=4D07D368.5050104@manicmethod.com \
--to=method@manicmethod.com \
--cc=csellers@tresys.com \
--cc=ewalsh@tycho.nsa.gov \
--cc=jwcart2@tycho.nsa.gov \
--cc=n3npq@mac.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=slawrence@tresys.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.