[Radioactive-developers] RE: quality

[Randall B. <ran...@gm...>]

All,
Yes we definitely need someone to write a coding standard or at least
we will have to agree to use one that is already written(I am sure
there some that are freely available).  Am I wrong in thinking that a
coding standard really would not have any specific info about the
radioactive project in it? To me it just defines the format of the
code.

Just to open up a discussion I will let you know how the company I
work for handles testing.

Unit Testing - Unit testing is preformed by the developers involved in
writing the new feature or fixing the bug. The developers are
responsible for defining the set of test they are to run.

System Testing - Tests the functionality of the new feature or bug fix
within the context of the whole system. This testing is handled by a
dedicated team of testers. The system test people are responsible for
defining the complete set of tests for a each feature of the software.

Regression Testing - Tests to make sure that nothing has been broken
during the new development. One way to do this testing is to automate
it. The company I work for has a set of  pearl scripts and test
programs that are run on every new version of our software. These
scripts produce a pass or fail for a set of tests. The benefits of
using testing scripts is once the script is written it take very
little human time to preform the regression testing. Of course that
every time a new feature is added to the software new test cases will
have to be added to the script. The system test group is responsible
for the maintenance of the scripts. Of course we will probably have to
have some regression testing that is not preformed by scripts, but I
think we should try to minimize the amount of human time spent
regression testing while still maintaining a high standard of care.

Thanks,
Randy



On Wed, 11 Aug 2004 21:55:15 -0400, Shaun Ricci
<sha...@ra...> wrote:
>
> Hi Everyone,
>
> I was wondering if anyone was interested in doing quality work.  I think
> this is a huge job, and probably could
> use more than one person.  Things that you will do are manage unit
> testing, regression testing, releases, write coding standards etc.
> Probably a lot of communicating to the other developers as well.  You will
> get a very good knowledge of the entire piece of software.  If you are
> interested, let me know.
>
> Cheers,
> Shaun
>