[Pharo-dev] Idea and proof of concept: Accept for Test

Denis Kudriashov dionisiydk at gmail.com
Wed May 16 12:21:13 EDT 2018


Hi Marcus.
I commented on github.

2018-05-16 18:34 GMT+03:00 Marcus Denker <marcus.denker at inria.fr>:

>
>
> > On 4 Apr 2018, at 18:02, Marcus Denker <marcus.denker at inria.fr> wrote:
> >
> > Hi,
> >
> > Some code is very “active”, executed all the time, e.g. collections,
> graphics… or imagine if you work on the compiler or debugger.
> >
> > It would really be nice if we could test a change before accepting it.
> Something like “Accept for Test” where magically the original method
> > does not change, yet, when running tests, the version of the code we
> accepted for testing is executed.
> >
> here is a version done using a Calypso command:
>
>         https://github.com/pharo-project/pharo/pull/1372
>
> missing:
>         -we need to have some visual clue in the footer
>         - a tool that lists all “accepted for test” method with the
> possibility to “commit” all at once.
>

We will have it almost for free with Calypso as soon as this new metalink
will be managed similar way as breakpoints.
"Commit" is of course needs to be implemented.


>
>         Marcus
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20180516/9b977e43/attachment.html>


More information about the Pharo-dev mailing list