Thanks Alexandre and Peter for your inputs, In the end I think I will use the Annotation Testing view.
On a different note, I just created a small project to expose Apache RUTA projects as web services: http://renaud.github.io/easily-deploying-apache-ruta-projects-as-web-services.html Let me know if you would be interested in integrating it into the RUTA codebase. It's basically 3 java classes and 1 config file. Best, Renaud On Tue, Aug 19, 2014 at 9:59 AM, Peter Klügl <pklu...@uni-wuerzburg.de> wrote: > Hi, > > in addition to alexandre's reply: > > We normally use the Annotation Testing view in the Ruta Workbench for > only testing the functionality of rules for an application (not the ruta > implementation), but view builts on xmi and supports no text specification. > > If you implement something, consider to contribute it :-) > > Best, > > Peter > > Am 18.08.2014 23:30, schrieb Renaud Richardet: > > Hello, > > > > What are best practices for writing unit tests for Ruta? > > > > Ideally, I would like to have 1) tests that can be run on the command > line > > (so as to automate them in Jenkins), and 2) where input and expected > output > > can be edited in a text editor (meaning: not xmi's or java code). > > > > For 1), I was thinking about writing a script to automate testing > > For 2), I was about to write the expected output in a simple xml or json > > format, but if something already exists, that would be great. > > > > Thanks, Renaud > > > >
