ATL VM Testing
This page consists in a report of emfvm non-regression tests. Those tests are available in the ATL repository and reports all performances and regression issues between the two versions of the ATL VM. Here are also centralized all development informations about the emfvm, like missing features.
Some relevant EMF-based transformations are integrated to the test set and are launched with the Regular VM and the emfvm. The results of the transformations are comparated using EMF Compare. When a test pass successfully, execution times are reported for both VMs in order to detect performance issues. If a test fails, a short description of the problem (or eventually a bug) is reported in the "Comments" field. The test is excluded from the emfvm test set until it is corrected.
|FlattenTest||PASS||0.031s.||0.015s.||Collections implementation completed on 12/12/2007.|
|ATL2Problem||PASS||0.094s.||0.016s.||EnumLiteral support added on 25/01/2008.|
|Total time :||13.686s.||1.567s.|
Tests realized on Wed Mar 05 18:39:38 CET 2008 with : Hardware
- Processor : Pentium 2 GHz
- RAM : 2 Go
- Operating system : Windows XP
- JVM : JRE 1.6
- Eclipse 3.4 Ganymede
- ATL 2.0
emfvm missing features
Here is the list of the missing features of the emfvm. The purpose of this list is to attempt to prevent duplicate works, by signalizing current developments. So, if you are committer, or contributor, do not hesitate to update this list by shortly describing your current work (possibly with your contact):
- Compilation support using one of the following alternatives:
- Update ACG to directly generate an XML model instead of relying on specific "native types" like ASMEmitter.
- Add the ASMEmitter type to emfvm, so that compilers generated with the current version of ACG can work.
- ADWP debugging protocol.
- Exceptions logger.
- New bytecodes:
- "delete": to remove an element, and all references that point to it.
- "unset": to unset a feature (e.g., to support changing the value of a multi-valued feature).
- "newin": to create a given element in a specific model.
The "delete" and "unset" new bytecodes will for instance be usefull to implement the refining mode of ATL 2006 (with in-place model transformation support).
How to use
org.eclipse.m2m.atl.test is an Eclipse plugin embedding a lot of ATL use cases. It also provides a way to launch several non-regression tests :
- Transformation : a result of each transformation has been stored. Each transformation is launched using one of the atl vm's and the resulting models are compared with the old ones using EMF Compare.
- Parsing : each atl file can be parsed into its .atl.ecore equivalent, in order to compare them.
To be launched, the test needs the org.eclipse.test plugin to be present. The best way to install it is to use an atl psf. You can also checkout it from the /cvsroot/eclipse repository.
To launch the test, just right-click on the project, select Run As -> Junit Plug-in Test. Then in the launch configuration you will be able to choose the tests classes you want to launch. If you just want to test the EMFVM, just right click on the TestNonRegressionEMFVM.java file and launch a Junit Plug-in Test.
The data directory contains all the tests cases. If you want to avoid one are many tests, simply add their names in the emfvm.properties or vm.properties files (one per line).
When the transformation tests are launched, the execution time of each transformation is printed on the console. You can retrieve the results in a simple XML file, in the "results" folder. Basically, those files are used to generate the non-regression table on this page.
How to contribute
To contribute, you can add your own test to the non-regression test. Please make sure that:
- You are allowed to release the work under EPL.
- The transformation works with EMF (i.e., the only model handler currently supported by emfvm).
- The transformation correctly runs on the Regular VM.
NOTE : At this time, profiled UML2 target models are not supported. However, you can already submit any related test, in prevision of a future implementation.
To contribute a test, you can either put it into CVS (if you are committer), or contribute it on bugzilla. You may ask questions about how to do this on the M2M newsgroup, using the [ATL] prefix in your subject. You may also directly contact William Piers if you cannot follow the procedures described above.
A non-regression test is never complete, so feel free to contribute your tests!