Continuous integration

[cberzan]

@chrisgioia64

"build passing" badge using travis-ci.org (docs, live example)

Travis build should test the following things:

• compilation succeeds
• all junit tests pass
• all examples run
• verify that blog errors (parse error, nonexistent engine, file doesn't exit, etc) are caught and result in non-zero return code
• a simple example (e.g. burglary) with fixed seed produces consistent output

Also integrate it with github (see docs). For an example of what this looks like, see here -- the checkmark or x mark next to each pull request shows whether the build passed / failed.

[chrisgioia64]

The following are issues that should be covered by continuous integration:

290 (Problems with Matrix Indexing)

[chrisgioia64]

@cberzan @lileicc any good way to run all the junit cases? I need to be able to run it from the command line and I would prefer not to write a test suite that includes all the individual junit files.

[lileicc]

sbt/sbt test

On Fri, Aug 1, 2014 at 3:16 PM, Christopher Gioia notifications@github.com wrote:

@cberzan https://github.com/cberzan @lileicc https://github.com/lileicc any good way to run all the junits cases? I need to be able to run it from the command line and I would prefer not to write a test suite that includes all the individual junit files.

— Reply to this email directly or view it on GitHub https://github.com/BayesianLogic/blog/issues/288#issuecomment-50940973.

[chrisgioia64]

I don't think bullet point #5 is going to work. Tried using bash, but I don't think it's that robust. There's a package that has test examples for Burglary and Hurricane.

Also, Lei didn't think bullet point 4 was necessary.

[cberzan]

Bullet 4 is necessary to avoid false positives when testing. For example, if we run blog on a model where parsing fails, it currently returns 0. If we only check the return code, we incorrectly conclude that the run was OK.

[chrisgioia64]

We should add a test that gives consistent results across different inference and sampling engines

[lileicc]

@chrisgioia64 Yes, we should do that in regression test. There are a few examples about the testing the result against the true result. check under test.