Just had some ideas to improve JO following the normal clamor one hears from all the other unit testing frameworks (TestNG and junit4 especially):
- Make tests NOT have to extend ObjectTestCase (simplifies things)
- Let JO metaphors be run from junit (might get messy, but would be helpful to use junit's asserts, especially with JO mocks)
- Use a proper schema (XSD) for objects.xml files
- Change the direct use of <methodName> in tags (as this cant be validated against a schema)
- Make JO more focused on design patterns and mocks
Feel free to post your thoughts.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
State-chain init would be the
ideal place for injecting mock objects, ideally it should be injected before and across a
single test unit. Which would be a metaphor (or with more granularity, a state-chain).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Just had some ideas to improve JO following the normal clamor one hears from all the other unit testing frameworks (TestNG and junit4 especially):
- Make tests NOT have to extend ObjectTestCase (simplifies things)
- Let JO metaphors be run from junit (might get messy, but would be helpful to use junit's asserts, especially with JO mocks)
- Use a proper schema (XSD) for objects.xml files
- Change the direct use of <methodName> in tags (as this cant be validated against a schema)
- Make JO more focused on design patterns and mocks
Feel free to post your thoughts.
MOCK OBJECTS ADD
State-chain init would be the
ideal place for injecting mock objects, ideally it should be injected before and across a
single test unit. Which would be a metaphor (or with more granularity, a state-chain).