-- _289921294 ALT Content-Type: text/plain; charset="us-ascii"; format=flowed At 12:44 PM 11/25/2002 +0900, you wrote: >I am new to Ruby and to programming. One thing I like about Ruby is that >one very quickly starts thinking about object-oriented programming >concepts and practices. Most of these concepts are quite difficult to >learn, but one can see the beginnings of the path ahead fairly >easily. For example, objects, classes, methods, UML, patterns, uses >cases, CRC cards, and so on, are all difficult and can be thought about >and or studied for years, but one can learn what they are about fairly >quickly. > >If only this were true for me for unit testing. I have looked around and >read a little, not all of it helpful. I have formulated the following >ideas about unit testing: (1) unit testing is good; (2) it is a good idea >to write unit tests before coding a class; (3) uh . . . . > >This leads to me to many questions: (1) how do you write a unit test?; (2) >uh . . . . [lots of good stuff snipped here] >Any comments, suggestions, references to other resources, thoughts, >teaching, etc. would be very welcome. I second this request! I have a vague concept of what Unit Testing is, but I don't really understand how or when to apply it. What are some good starting points for studying something like this? Books? Web sites? How do you test a GUI? and ... and ... This would be good enough information that it could probably go up on the rubygarden Wiki, too. There are a few ragged starting points in there, but not much for the person who _really_ doesn't know about testing. Thanks, - Brian W Brian Wisti brian / coolnamehere.com http://coolnamehere.com/ -- _289921294 ALT Content-Type: text/html; charset="us-ascii" <html> <br> At 12:44 PM 11/25/2002 +0900, you wrote:<br> <blockquote typee class¥¿te cite>I am new to Ruby and to programming. One thing I like about Ruby is that one very quickly starts thinking about object-oriented programming concepts and practices. Most of these concepts are quite difficult to learn, but one can see the beginnings of the path ahead fairly easily. For example, objects, classes, methods, UML, patterns, uses cases, CRC cards, and so on, are all difficult and can be thought about and or studied for years, but one can learn what they are <u>about</u> fairly quickly. <br><br> If only this were true for me for unit testing. I have looked around and read a little, not all of it helpful. I have formulated the following ideas about unit testing: (1) unit testing is good; (2) it is a good idea to write unit tests before coding a class; (3) uh . . . . <br><br> This leads to me to many questions: (1) how do you write a unit test?; (2) uh . . . . <br> </blockquote><br> [lots of good stuff snipped here]<br><br> <blockquote type¥¿te class¥¿te cite>Any comments, suggestions, references to other resources, thoughts, teaching, etc. would be very welcome.</blockquote><br> I second this request! I have a vague concept of what Unit Testing is, but I don't really understand how or when to apply it. What are some good starting points for studying something like this? Books? Web sites? How do you test a GUI? and ... and ...<br><br> This would be good enough information that it could probably go up on the rubygarden Wiki, too. There are a few ragged starting points in there, but not much for the person who _really_ doesn't know about testing.<br><br> Thanks,<br> - Brian W<br><br> <x-sigsep><p></x-sigsep> <font face rial, Helvetica">Brian Wisti<br> brian / coolnamehere.com<br> <a href ttp://coolnamehere.com/" eudora utourl">http://coolnamehere.com/</a></font></html> -- _289921294 ALT--