INACTIVE - http://mzl.la/ghe-archive - Unit Tests for your Network -
Перейти к файлу
Dustin J. Mitchell fa9dbbfb59
Merge pull request #48 from Mozilla-GitHub-Standards/master
Add Mozilla Code of Conduct
2019-03-29 12:51:45 -04:00
docs Merge pull request #44 from tolleiv/patch-1 2017-06-07 09:09:18 -04:00
example Merge djmitche/build-fwunit:bug1118451 (PR #31) 2015-03-17 12:32:55 -04:00
fwunit Sort global policies and always interpret them after local policies 2016-06-27 14:50:41 +00:00
media/lisa15 final tweaks 2015-11-11 22:25:59 -05:00
.gitattributes Start using python-versioneer 2014-09-12 17:29:42 -04:00
.gitignore add a validate.sh script 2014-10-21 17:27:43 -04:00
.travis.yml enable coveralls (only for github.com/djmitche) 2014-10-27 19:05:49 -04:00
CODE_OF_CONDUCT.md Add Mozilla Code of Conduct file 2019-03-29 09:50:00 -07:00
MANIFEST.in Start using python-versioneer 2014-09-12 17:29:42 -04:00
README.md WIP 2014-11-04 17:12:26 -05:00
coveragerc convert to using coverage directly, rather than via nosetests 2014-10-24 11:20:26 -04:00
release.sh fix release.sh to specify tarball name 2014-11-04 13:33:21 -05:00
setup.py Limit to moto<0.4.24 to avoid triggering a bug 2016-06-27 14:50:08 +00:00
validate.sh convert to using coverage directly, rather than via nosetests 2014-10-24 11:20:26 -04:00
versioneer.py Start using python-versioneer 2014-09-12 17:29:42 -04:00

README.md

Unit Tests for your Network

Any developer worth their salt tests their software. The benefits are many:

  • Exercise the code

  • Reduce ambiguity by stating the desired behaviors twice (in the implementation, in the tests, and maybe even a third time in the documentation)

  • Enable code refactoring without changing expected behavior

With fwunit, you can do the same for security policies on your network.

demo

Documentation

See http://fwunit.readthedocs.org/