The JaCoCo Work Flow Flow

I'm in the middle of rearranging the structure of our fork of ODK Aggregate
so that the integration tests are moved into their own module
aggregate-integration.

I'm not familiar with JaCoCo and not sure why a JaCoCo war is being
imported into Cargo for the integration tests instead of a plain old war.
I was wondering if there was any documentation about how JaCoCo is used in
ODK. Mostly I am interested in what flows into it, and where its outputs
go, and why.

This was for code coverage, though we never got the code coverage reporting
stitched together for the unit and integration tests.

You can use a different code coverage library or remove the jacoco logic
and base the integration and unit tests off of just the war itself instead
of the instrumented one.

··· On Tue, Feb 21, 2017 at 3:59 PM, C. Howell wrote:

I'm in the middle of rearranging the structure of our fork of ODK
Aggregate so that the integration tests are moved into their own module
aggregate-integration.

I'm not familiar with JaCoCo and not sure why a JaCoCo war is being
imported into Cargo for the integration tests instead of a plain old war.
I was wondering if there was any documentation about how JaCoCo is used in
ODK. Mostly I am interested in what flows into it, and where its outputs
go, and why.

--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com

Hi Mitch,

If Caden sends in these as PRs, can these changes be merged back into trunk?

Yaw

··· On Wed, Feb 22, 2017 at 8:06 AM, Mitch Sundt wrote: > This was for code coverage, though we never got the code coverage reporting > stitched together for the unit and integration tests. > > You can use a different code coverage library or remove the jacoco logic and > base the integration and unit tests off of just the war itself instead of > the instrumented one. > > > > On Tue, Feb 21, 2017 at 3:59 PM, C. Howell wrote: >> >> >> I'm in the middle of rearranging the structure of our fork of ODK >> Aggregate so that the integration tests are moved into their own module >> aggregate-integration. >> >> I'm not familiar with JaCoCo and not sure why a JaCoCo war is being >> imported into Cargo for the integration tests instead of a plain old war. I >> was wondering if there was any documentation about how JaCoCo is used in >> ODK. Mostly I am interested in what flows into it, and where its outputs >> go, and why. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "ODK Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to opendatakit-developers+unsubscribe@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. > > > > > -- > Mitch Sundt > Software Engineer > University of Washington > mitchellsundt@gmail.com > > -- > You received this message because you are subscribed to the Google Groups > "ODK Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to opendatakit-developers+unsubscribe@googlegroups.com. > For more options, visit https://groups.google.com/d/optout.

Don't know -- at the moment, I don't know what he's doing.

The database integration tests and unit tests (xxx-unit-tests) are already
in a separate maven module from the build-WAR-and-quick-end-to-end-UI-test
flow.

If the end-to-end-UI-test flow is extracted out so that it depends upon a
new build-WAR module and the resulting WAR file is used during the UI test,
then that's fine. If the WAR isn't reused, then I think that is the wrong
restructuring of the modules.

It would be desirable to preserve the code coverage instrumentation in the
UI test so that an overall code coverage could be computed. And ideally
get the code coverage instrumentation in the integration and unit tests to
fold together with the UI coverage to get a combined code coverage score.

··· On Tue, Feb 21, 2017 at 4:13 PM, Yaw Anokwa wrote:

Hi Mitch,

If Caden sends in these as PRs, can these changes be merged back into
trunk?

Yaw

On Wed, Feb 22, 2017 at 8:06 AM, Mitch Sundt mitchellsundt@gmail.com wrote:

This was for code coverage, though we never got the code coverage
reporting
stitched together for the unit and integration tests.

You can use a different code coverage library or remove the jacoco logic
and
base the integration and unit tests off of just the war itself instead of
the instrumented one.

On Tue, Feb 21, 2017 at 3:59 PM, C. Howell caden@cadenconsulting.com wrote:

I'm in the middle of rearranging the structure of our fork of ODK
Aggregate so that the integration tests are moved into their own module
aggregate-integration.

I'm not familiar with JaCoCo and not sure why a JaCoCo war is being
imported into Cargo for the integration tests instead of a plain old
war. I

was wondering if there was any documentation about how JaCoCo is used in
ODK. Mostly I am interested in what flows into it, and where its
outputs

go, and why.

--
You received this message because you are subscribed to the Google
Groups

"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send
an

email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com

--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com