On Tue, 15 Dec 2015, Donald Sharp wrote:
Unit test requirements:
Openswitch has framework for testing that might suffice
That would be here, python + mininet:
http://git.openswitch.net/cgit/openswitch/ops-quagga/tree/ops/tests
These specific ones are likely too tied in with the rest of OPS, but maybe
interesting examples.
Blackbox unit testing - mini-net?
Vincent - project to do Quagga testing?
Daniel - once upstream quagga closer to ours, we could use our test
suites to evaluate upstream patches, Cumulus is working on a way to run
patches against internal tests. Michael asked for an overview of what is
tested in Cumulus
Agreement - need more unit testing and multiple people have ideas
on how best to do it
Talk to Martin with ideas
We should probably make running the unit tests part of the build. I have
actually caught introduced bugs simply by running the tests. Maybe not
often, but I have done. It also helps with adding changes and getting
coverage of existing code.
Which reminds: Coverage reports to figure out what is _not_ being tested
might be an idea.
We perhaps should start demanding tests to cover introduced code (esp for
any kind of parser).
Quagga,net not working? may now be fixed
Documentation requirements for new features/commands?
Currently missing but should be necessary
Someone with good documentation donate to the community?
If everyone gave themselves a 'chore' to pick an arbitrary bit of
documentation and write/improve it, we might make progress.
Writing documentation is also a really good way to really inform
/yourself/. Self-improvement too. ;)
"Touching commands requires documentation" might be a good rule to apply
from now on.
regards,
--
Paul Jakma [email protected] @pjakma Key ID: 64A2FF6A
Fortune:
QOTD:
"I never met a man I couldn't drink handsome."
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
