On 10/29/07, Daniel L. Rall <dlr@finemaltcoding.com> wrote:
> On Sat, 27 Oct 2007, Troy Curtis Jr wrote:
>
> > On 10/27/07, Troy Curtis Jr <troycurtisjr@gmail.com> wrote:
> ...
> > > Thanks for the pointers. The fact that you didn't say "Oh my goodness
> > > you shouldn't have even bothered to code that!" or "Why did you do
> > > THAT!" is promising. I guess I start in on the other commands. And
> > > then I'll work on figuring out those tests. I know that kogel
> > > recommended writing the tests before doing the code, but how do I test
> > > that my tests are doing what they are supposed to be doing? :)
>
> Stefan's comments sound good to me.
>
> API and command-line client support for relative URLs sounds great to me!
> I probably would've started with something more useful than 'info' (which
> is more often run against the WC), but it still conveys the idea fine.
>
Ah, but the nice thing about the info command as a first run is that
it dumps out the full URL, makes for a nice check that you function is
working as expected. :)
> I recommend writing the test in conjunction with an API that returns
> nothing (or some known value). That way, when the test fails, you'll see
> a comparison of the expected value against what your code is actually
> producing, allowing you to debug both test and API.
>
>
Yeah yeah, that sounds reasonable. But I'm not used to writing tests
:) Which I know isn't really a valid excuse. Maybe I should jump
over and make the tests for everything before I proceed with the
remainder of the APIs (I'm a little over half done). I'll think on
it. Thanks for you comments!
Troy
--
"Beware of spyware. If you can, use the Firefox browser." - USA Today
Download now at http://getfirefox.com
Registered Linux User #354814 ( http://counter.li.org/)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Oct 29 12:45:06 2007