This is the front page of the portion of the MIWG Wiki intended for internal use by the MIWG.
If you are an OMG member interested in the interchange of models based on OMG standards, you can join the MIWG:
Release 15 has now been made public as the current MIWG test suite.
Briefing from the March 26, 2010, Jacksonville meeting here.
Minutes from 2010: here
Minutes from 2011: here
Minutes from 2012: here
Minutes from 2013:
See also the testing process diagrams.
The following guidelines do not necessarily reflect constraints imposed by the XMI specification, but are used for the purposes of the model interchange testing:
The following testing guidelines are related specifically to the interchange of profile models and their application in user models:
The internal MIWG test suite repository is found at https://dev.enterprisecomponent.com/repository/repos/OMG-Model-Interchange. Login is required. To obtain an account, contact Ed Seidewitz.
The following is the draft recommended practice for file naming in the test case repository. (And yes, the names below begin literally with 'our'):
The only version information in the names of the files here is for UML, XMI and the vendor's product. The toolNameX directory contains all the deliverables concerning Test-Case-N from the vendor owning toolnameX. Versioning of these files is handled by the CM system itself.
The latest version of the test suites reside in the SVN repository under trunk/tests. Periodically, the current version of all the tests will be declared an official “release”. At this point, the trunk revision of the entire tests directory will be branched in SVN. The directories for release R will reside in the SVN repository under branches/Release-R/Tests, with the subdirectory structure under tests as given above.
When making submissions, vendors should observe the following:
Vendors should not normally make changes to files on branch releases outside of the appropriate submission directories for their tools. The creation of release branches, under direction of the MIWG, will be done by Ed Seidewitz, and any questions on branches and related CM should be directed to him.
Incremental Plan: The model interchange testing plan will include the following incremental capabilities. It is expected to take 3-4 weeks to complete a test case once we achieve a cadence. It is also expected that there will be more than one test case per unit of functionality outlined below, based on the level of complexity.
Incremental Process:
Incremental Deliverables: