mschepens wrote:
First of all, thank you for your answers, your precious advices and for
having taken time to answer us. Answers to Ben Coman :
It's our first experience with Pharo, but we'll take more time to learn this
project if it's necessary.
We're a little comfortable with the tool, we already took the time to
discover it, to do the first tutorial which is proposed when pharo is
launched, and to develop first classes and tests for learning about pharo.
We never used the TestRunner previously, we just ran our tests for our
classes yesterday.
We never submitted a code Slice for Intergration before.

We're still waiting propositions of Test or code to cover, and again thank
you for your attention.


So there was the "contractTo:" example that I provided. This provides a simple end-to-end practice example for getting "some" code integrated into Pharo. Try that first.

Now perhaps no one has a "list" missing tests. Either new tests get written together with new system code, or just when people bump into problems. Open source is about scratching your own itch, and learning how to discover gaps is nearly as important a skill as filling them. Did you try my recipe to find gaps? Report what you found, then it is less of a burden for all to review and advise on those, than for us to do this task for you. Now an alternative recipe to find gaps is in the Browser, scroll down to Collections-** and for various classes look in the "testing" protocol of the third pane, then right-click of various methods and choose "Senders of..." to see if it is sent from a test method. btw, it is just co-incidence the protocol is called "testing". This is the general protocol for method that return a "true or false" result. I'd chose this to start with since it should be simpler to work out what each method does from looking at its Senders, and how to write a test for it, than other infrastructure methods.

Now you may find it useful to review....
http://www.catb.org/esr/faqs/smart-questions.html

Good luck with it, and I feel free to ask more questions.
cheers -ben

Reply via email to