On 9/13/07, Sean Qiu wrote:
<SNIP>
>
> Yep, it is OK here.
> But to get emma report, we need run the emma adaptor again to generate the
> report.
> So the sequense here is:
>
> 1) setup (emma adaptor)
> download emma
> 2) run (emma adaptor)
> instrument jre
> 3) run (testsuites)
> run test within instrumented jre
>
No, emma adaptor shouldn't run any test suite. See snapshot adaptor -
'run' target only unpacks downloaded jre, nothing else.
To run a suite on jre instrumented by emma adaptor the adaptor should
set corresponding suite's property which points to jre for testing.
For example,
classlib-test.parameters.required.tested.jre=${EMMA.paremeters.shared.jre}
> 4) generate coverage report, ???? (emma adaptor is suppposed to finish
> this.)
>
Yes, it should provide publisher for suites to collect reports.
> Or we need to generate report manually after the running.
No, I think this should be automated.
Thanks,
Stepan.
> This violates the invoking sequence for usual adaptors.
>
> What's more, i think emma will invoke each adaptor just like "run-cc", they
> are in a higher abstraction than test suites.
> So i propose to maintain them in a similar place.
>
>
>
> > 5) create custom config.xml for CC with emma publisher for suites
> > (<suite>..parameters.cc.config=${adaptors.dir}/emma/custom-config.xml)
> >
> > Thanks,
> > Stepan.
> >
>
>
>
> --
> Sean Qiu
> China Software Development Lab, IBM
>
--
Stepan Mishura
Intel Enterprise Solutions Software Division
