> On 6 Oct 2019, at 07:04, James Foster <[email protected]> wrote:
>
> Hi Pharo developers,
>
> I have a few undergraduate students taking OO programming and I’m using the
> Pharo MOOC to get started. One of the goals in our CS program is to get
> students familiar with a development process using Git, so we require
> contributions to an open source project is a few classes. I’d like to assign
> a Pharo contribution and am looking for easy first issues.
Excellent idea!
> I’ll take a look at the issues marked ‘Easy’ as well as the “Simple Issues
> for Beginners” project, but would welcome additional ones.
It would be super cool to add executable examples to number and others.
> My current thought is to go through tests looking for use of #’assert:’ that
> could be changed to #’assert:equals:’. I view this as being an improvement
> but still quite safe and easy to describe. Most of the work will be setting
> up the environment and going through the development cycle; I want the actual
> coding to be minimal (but still useful).
Yes.
Once back in 2005 I gave as exercise to write tests for collections (because
they were none back then) after I reviewed revise them and committed them.
So looking at coverage of classes may be a nice option too.
I think that what you can also ask them is to
- reproduce issue
- comment issue
This is an important aspect too.
Stef
>
> James Foster
