You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Alex Karasulu <ak...@apache.org> on 2007/01/29 22:24:37 UTC
[Unit Testing] This is a great attitude (Re: [jira] Commented: (DIRSERVER-831)
Proposed protocol-dns changes)
Richard Wallace (JIRA) wrote:
> [ https://issues.apache.org/jira/browse/DIRSERVER-831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468411 ]
>
> Richard Wallace commented on DIRSERVER-831:
> -------------------------------------------
>
> I can work on doing that. I also plan on adding more tests cause I hate doing refactorings without having a safety net.
Wow I could not have said it better myself. Test cases = safety net for
refactoring? You bet but that's not all.
When an open source developer gets considerable code coverage with a
code base those coming into the code after him/her can easily see how
the code is working. They can try to make small bug fixes. And perhaps
even try to introduce new features as they get more comfortable with the
code base. Tests from the original developers and themselves are a
great way for them to be somewhat reassured that nothing is broken.
Unit test cases are good for open source. They help bring new committers
and contributors to the community.
Alex
Re: [Unit Testing] This is a great attitude (Re: [jira] Commented: (DIRSERVER-831) Proposed protocol-dns changes)
Posted by Ersin Er <er...@gmail.com>.
On 1/29/07, Alex Karasulu <ak...@apache.org> wrote:
> Richard Wallace (JIRA) wrote:
> > [ https://issues.apache.org/jira/browse/DIRSERVER-831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468411 ]
> >
> > Richard Wallace commented on DIRSERVER-831:
> > -------------------------------------------
> >
> > I can work on doing that. I also plan on adding more tests cause I hate doing refactorings without having a safety net.
>
> Wow I could not have said it better myself. Test cases = safety net for
> refactoring? You bet but that's not all.
>
> When an open source developer gets considerable code coverage with a
> code base those coming into the code after him/her can easily see how
> the code is working. They can try to make small bug fixes. And perhaps
> even try to introduce new features as they get more comfortable with the
> code base. Tests from the original developers and themselves are a
> great way for them to be somewhat reassured that nothing is broken.
>
> Unit test cases are good for open source. They help bring new committers
> and contributors to the community.
Although we are sometimes lazy about them, I am in love with unit
tests. They are not only safety nets, but also great documentation for
API users.
--
Ersin