[Feature-dev] Test quality metrics and recovery plan

[Gurgen Tumanian]

Hi Mike.

A small comment from my side.

>>As we continue to eliminate unused code and understand the interactions
between >>classes, we need to finalize the API for each class and then write
tests (i.e. unit ??tests) to test each method.
I think that it is better not to wait for the API to finalize, but to start
writing unit tests now. I think it will be easier to do it now in the
process of refactoring the code, then to do a test-writing-death march
later.

BTW, what do you use for unit tests? Is that still the mini executables that
are in the unit-test dir? I propose to have a look at the existing
unit-testing frameworks and choose the one that suits our tasks best.
CppTest could be one solution.

Regards
Gurgen

On Wed, Jun 24, 2009 at 5:47 PM, Mike Wong <mikewong at sfsu.edu> wrote:

> Hi all,
>
> Just to confirm, there is an unresolved bug in our code base and Mauricio
> and I will address it.
>
> I've written some software to perform our regression test against our
> submissions to the FEATURE Subversion server, and the results are good and
> bad. As we increase coverage in our tests there are more failures. This is
> good because we know that our tests are pushing the envelope of the utility
> of FEATURE and our testing process is improving. This is bad because
> somewhere along the line we destroyed previously existing functionality in
> FEATURE and didn't know about it (because the test for the functionality
> didn't exist).
>
> Now, of course we can always roll back to r418 and restore all the old
> functionality and try to re-implement our changes. However, my plan is to
> move forward, find the error that caused the loss of functionality, patch
> that error, and apply the patch to the latest revision.
>
> Good news is that r454 passes all tests, so we know that r454 has
> equivalent functionality to r418 (for all functions that we test).
>
> Bottom line: As a team we need to make a commitment to software testing,
> and we need to share the QA duties. As we continue to eliminate unused code
> and understand the interactions between classes, we need to finalize the API
> for each class and then write tests (i.e. unit tests) to test each method.
>
> Best regards,
>
> - m.
>
> __________________________________
> Mike Wong, Staff Research Associate
> Center for Computing for Life Sciences (CCLS)
> San Francisco State University
> 1600 Holloway Avenue, Hensill Hall 301, SF, CA 94132
> (415) 405-2119
> mikewong at sfsu.edu
>
> _______________________________________________
> Feature-dev mailing list
> Feature-dev at simtk.org
> https://simtk.org/mailman/listinfo/feature-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://simtk.org/pipermail/feature-dev/attachments/20090625/eaeb8b7f/attachment.html