Continuous integration
<http://en.wikipedia.org/wiki/Continuous_integration>may help to do
some quality assurance in a automated way.

Using JUnit <http://junit.org/>, Jenkins <http://jenkins-ci.org/> and maven
you could have a little web server working as a qa specialist for the
project.

This could be the typical workflow:

Something triggers the integration (daily?, after a submit?, after
dependency changes?),
Checkout fresh sources from the repository,
Run findbugs and any other task to do static analysis,
Compile the sources,
Run test suites (test classes, check expected from tutorials, etc),
Package an snapshot jar,
Build a static site
<https://maven.apache.org/plugins/maven-site-plugin/>and deploy it in
webserver showing the status, stats, etc.
Deploy the jar in a website,
Any broken step may be reported by email,





On Wed, Feb 19, 2014 at 5:03 PM, Raymond Shpeley <[log in to unmask]>wrote:

> I've started on the application examples for basic operation, since I
> don't know
> much about how they work yet. The process I'm using is to run an example,
> save
> out.stat under a name suited to the example, save the console the same way,
> record the command line options, out.stat filename and console filename to
> a
> summary file for all run variants I can find of that example type. If I
> find an issue
> with warning errors or some such I record a mention of it in the summary
> file.
>
> This is kind of tedious to do by hand so I've thought of running it on our
> university server with a script to automate it. The problem is I'm
> currently holed
> up on a farm during reading week and internet access is spotty, or even
> non-
> existent, depending on the sun-spots...
>
> I don't know if this is enough information to do much good, but it should
> check for
> any obvious errors.
>
> -- ray
>



-- 


--------------------------------------------------
J. Alejandro Zepeda Cortés
Ing. Civil Informático
TMóvil: +56-9-98184077
[log in to unmask]
--------------------------------------------------