| Issue 34: | MXUnit Annotations | |
| 1 person starred this issue and may be notified of changes. | Back to list |
Consider implementing annotations as way to pass additional information to mxunit to facilitate testing - test generation, test running, db transactions, mocks, etc.. This could be implemented as additional attributes added to either test methods or component methods. This is explained and was briefly proven in the /generator/ package. See attached. This could be used similar to java annotations and run similar to JUnit 4 tests. E.g., <cffunction name="myTestFunction" mxunit:annotate="runtest" ...> this would tell mxunit simply to run this method as a test. Additionally, this kind of annotation, or parameter, could also be used to articulate meta data about the test so as to perform database transactions - mxunit:transaction="begin" mxunit:transaction="rollback". Marc described this behavior earlier. As a way to generate tests, as decribed in the attached, something like mxunit:type="text" mxunit:regex="[foo]" ...
Jan 24, 2008
Project Member
#1
virtix
Labels:
-Priority-Medium Priority-Low
Jun 30, 2010
added some annotations. need to revamp for a more generic processor
Status:
Fixed
Cc: -marc.esher -AnodynePres -v.rajkumar |