ATL VM Testing
This page consists in a report of emfvm non-regression tests. Those tests are available on CVS 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||FAIL||0.016s.||Incomplete collections implementation.|
|UML2Relational||FAIL||0.046s.||Unsupported model elements containing "::".|
|ATL2Problem||FAIL||0.094s.||Missing EnumLiteral implementation.|
|SpreadsheetMLSimplified2Trace||FAIL||0.031s.||Transformation fails without errors.|
- Processor : Pentium 2 GHz
- RAM : 2 Go
- Operating system : Windows XP
- JVM : JRE 1.6
- Eclipse 3.3 Europa
- ATL 2.0
emfvm missing features
Here is the list of the missing features of the emfvm. This list attemps 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 (eventually with your contact) :
- Complete UML2 support
- AsmEmitter equivalent (for ACG support)
- Metamodel java methods support
- Debugging protocol
- Exceptions logger
- Refining mode, with in-place model transformation support
How to contribute
To contribute, you can add your own test to the non-regression test. Ensure that : - your work isn't copyrighted - the transformation doesn't uses MDR metamodels (not supported by the emfvm) - the transformation correctly runs on the Regular VM NOTE : At this time, UML2 profiled target models generation isn't supported, but you can submit any concerned tests, in prevision of a future implementation.
To contribute a test, you can either put them into CVS (if you are committer), or contact William Piers.
A non-regression test is never complete, so feel free to contribute your tests !