alexroldugin / spray

Automatically exported from code.google.com/p/spray
0 stars 0 forks source link

Write automated tests for the generated diagram editors #202

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
There are currently some bugs in the generated diagram editors that should be 
disovered inside the automated build.

I have checked in some example diagram projects done with our example DSL 
projects:
 * http://code.google.com/a/eclipselabs.org/p/spray/source/browse/examples/bpmn2.0/org.eclipselabs.spray.examples.bpmn.diagrams
 * http://code.google.com/a/eclipselabs.org/p/spray/source/browse/examples/fowlerdsl/org.eclipse.xtext.example.fowlerdsl.diagrams
 * http://code.google.com/a/eclipselabs.org/p/spray/source/browse/examples/fowlerdsl/org.eclipse.xtext.example.fowlerdsl.diagrams
 * http://code.google.com/a/eclipselabs.org/p/spray/source/browse/examples/lwc2012/org.eclipselabs.spray.examples.lwc2012.diagrams
 * http://code.google.com/a/eclipselabs.org/p/spray/source/browse/examples/one/org.eclipselabs.spray.examples.one.diagrams
 * http://code.google.com/a/eclipselabs.org/p/spray/source/browse/examples/petrinet/org.eclipselabs.spray.examples.petrinet.diagrams

For how to test, see the following resources:

Graphiti Dark Feature Processing
 * http://help.eclipse.org/juno/index.jsp?topic=%2Forg.eclipse.graphiti.doc%2Fresources%2Fdocu%2Fgfw%2Fdark-feature-processing.htm
 * http://5ise.quanxinquanyi.de/2012/08/06/testing-graphiti-applications-with-dark-feature-processing/

Graphiti SWTBot Tests
 * http://git.eclipse.org/c/gmp/org.eclipse.gmp.graphiti.git/tree/tests/org.eclipse.graphiti.bot.tests
 * I (Joerg) actually developed some Graphiti SWTBot tests to, I should make the generic factored out super/helper classes available to Spray

See also the already existing SWTBot test for the Spray wizard (that currently 
fails)
 * http://code.google.com/a/eclipselabs.org/p/spray/issues/detail?id=8
 * http://code.google.com/a/eclipselabs.org/p/spray/source/browse/tests/org.eclipselabs.spray.examples.one.tests/pom.xml

The tests should be part of the example project builds: After having build the 
diagram DSL project an Eclipse instance should be started with the just build 
diagram DSL plug-in and creating a new diagram, adding and updating shapes 
should be tested either as SWTBot tests or dark feature processing tests.

For test concepts see here:
https://spray.ci.cloudbees.com/job/spray-docs-build/lastSuccessfulBuild/artifact
/docs/org.eclipselabs.spray.doc.dev/docs/html/SprayDeveloperGuide.html#Testingth
egeneratedGraphitieditor

Original issue reported on code.google.com by de.abg.r...@gmail.com on 18 Nov 2012 at 5:03

GoogleCodeExporter commented 8 years ago

Original comment by de.abg.r...@gmail.com on 19 Jul 2013 at 11:30