On Dec 16, 2010, at 1:06 PM, laurent laffont wrote:

Thank you Marcus.

Is it hard / possible to add test coverage ?

problematic... when testing system level code, you soon run into meta-recursion (e.g. Array is used by the code used for doing

test coverage). (we should really fix reflection as a concept... but that's more research and not engineering... I should continue with that).

So this would only make sense on a package by package case. But there it can make sense, yes.

What I want to add before test coverage is code-critique style checking.

Marcus

Laurent

On Thu, Dec 16, 2010 at 12:11 PM, Marcus Denker <marcus.denker@inria.fr> wrote:

Hi,

- the pharo 1.2 (and 1.1) full builds are now triggered by a successful build of the core images (failing tests are ok, failing builds do not trigger)
- One-Click of full is now build automatically:
https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/20/artifact/PharoOneClick1.2.zip
- just image and sources are available at this link https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastSuccessfulBuild/artifact/dev1.2.zip
- tests are now run on 1.2 full. 24 are failing, of which 12 are from core:
https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastCompletedBuild/testReport/

Next step:

- re-use the core images in the full image builds, do not update again. (saves 5 minutes build time)

Later:
- build all VMs from source automatically
- run tests on MacOS and Windows in addition to linux (to validate the VM and to check that image side is working on all plattforms)

--
Marcus Denker -- http://www.marcusdenker.de
INRIA Lille -- Nord Europe. Team RMoD.