On Mar 24, 2012, at 5:32 PM, Nicolas Cellier wrote:
Then if I introduce a new test documenting an old bug, it will then be rejected right ? I wonder if I'd really want such a dumb system without an ounce of human expertiseâ¦
This is not the idea :) How do I see the process: for the test we publish it in a bug entry and as soon as there a code that makes it green then we integrate it. Now we should have a way to say check that entry -> load the code -> run the tests and say if this is ok then in parallel - we should be able to look at the code - say ok please integrate - and the system does it So benjamin has a bunch of scripts for that. stef
Nicolas
Le 24 mars 2012 15:37, Stéphane Ducasse <stephane.ducasse@inria.fr> a écrit :
.. 1.4 has now all tests green on jenkins (Mac and Linux).
The nice side-effect is that all the jobs that check VM builds are now green, too.
https://ci.lille.inria.fr/pharo/view/Pharo%201.4/
The idea is to now to just never ever integrate anything that makes a test break...
ok but it means that we should run 20 min tests each we integrate somethingâ¦. how boring. We can try.
Stef
That's why you should use a full automatized process .... :whistle: ^^
indeed. I want :)
Stef