[Pharo-dev] Which tests should be run in CI?

Tudor Girba tudor at tudorgirba.com
Thu Dec 12 03:36:20 EST 2013


I meant to say that projects that use pharo should rethink the tests and
rules they run in order to ensure that they do not break the Pharo

For example, for Moose, we should have, like Stephan suggested, an
integration job that runs all tests in the image (at least). Ideally, it
should also run other rules that ensure that the system does not break due
to semantic mismatches.

If we do it this way, we push the signals upstream and discover the
problems sooner.


On Thu, Dec 12, 2013 at 8:16 AM, Stéphane Ducasse <stephane.ducasse at inria.fr
> wrote:

> >  We need to reconsider how we approach continuous integration for
> pharo-based images.
> can you expand ?


"Every thing has its own flow"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20131212/a4540e4e/attachment-0002.html>

More information about the Pharo-dev mailing list