Hi All,
> If everything worked as it was supposed to, bugs wouldn't exist.
> Unfortunately that isn't the case. You have to do some sort of testing
> to verify that everything works. What I am proposing is a more
> structured set of tests.
While I do agree that Unit testing will definitely keep some tab on the
quality of methods (especially in the development phase, where they are
changed ever so often), what we have to look into is whether the effort
would be really worth it.
> It is nice to know that when you make a change to GtkWindow that nothing
> else broke. By running the suite of tests after making a change you can
> be sure that get_type() still functions as it should. If you only write
> tests for bugs that have been found, you will always be a step behind.
> If you write tests first you will find the bugs before they get into
> production.
That's a good point. Maybe you could just mail the list the script that
you wrote, and interested people can have a look at it, and that way we
can move it forward.
> Unit tests can also be used to drive development. Writing the test now
> for yet to be developed methods makes sure that what you write works the
> way it should. It reduces the number of bugs that make it to the end user.
Agreed!
Cheers,
--
Anant
Find Freedom, Go Open Source!
http://www.kix.in/
--
PHP-GTK Development Mailing List (http://gtk.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
|
Try Searching:
servers, voip, java, networking, microsoft ...
|
|
|
| 
