Hello everybody,
how do you get confidence that your rule works as expected? Only
performing extensive and thorough code reviews? Or by compiling the
content, modifying your system, and finally executing oscap, hoping that
the results will match expectations? Or maybe by using your custom-built
test suite that you have to maintain?
If that's the case, then stop right there! The ComplianceAsCode project
contains tests and test scenarios for a long time, but our effort to
make those approachable has just reached a significant milestone. If you
use an OS with working podman>3.0 (or at least podman<2.2), you can run
and review pretty much any rule test 5 minutes from now if you know what
to do. And if you don't, you just need to read the fresh blog post,
which, being a 5-minutes read, enables anybody with no prior knowledge
to run and review their first rule test run in no more than 10 minutes.
Check it out:
https://complianceascode.github.io/template/2021/03/25/tests_howto.html
Obviously, you can test like no tomorrow even without podman, and there
may be glitches, so those five minutes may protract a little bit. In any
case, let us know about your experience either here on the mailing list,
or in the discussion below the blog post. More people in the team
participate in efforts to make tests more approachable, and we are
interested in any kind of feedback - especially if you would like to
know more about testing.
Looking forward to hearing from you!
_______________________________________________
scap-security-guide mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedorahosted.org/archives/list/[email protected]
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
