On Wed, May 1, 2013 at 10:29 PM, Christopher Sean Morrison
<[email protected]> wrote:
> but you still should speak to what code, how, and why in your proposal.
>
What code - code (code smell) that's doing too many things is hard to maintain.
Why code - to improve maintainability and readability.
How code - Shorter methods, smaller classes, write tests with high coverage,
run all tests.
> You should look at our existing test infrastructure as a starting point (and
> speak to how).
I can also use CTEST that BRL-CAD is currently using.
--
Avneet Kaur
www.avneetkhasla.wordpress.com
------------------------------------------------------------------------------
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
_______________________________________________
BRL-CAD Developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/brlcad-devel
