After looking into using Aspectj to now be used for doing the design pattern tests (and potentially more), I don't think we can get away with the current scheme for running junit-object tests. Right now we require the test creator to implement a main method with a set of code to trigger the tests to be ran.
In order to facilitate greater control over stages of building the test data and classes I think we need to do one of two things: 1. Add a default main method to the ObjectTestCase which relies on abstract methods to get the subclasses name, this method can then kick off the stages of the test building and etc. 2. Create a test runner which is seperate from the actual TestCase which will be responsible for kicking off building of tests and the running.
any thoughts?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
What about using object proxies to trap invocations? It would mean that all classes under test have to be provided by JO but that could be similar to TestNG's @DataProvider scheme.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
After looking into using Aspectj to now be used for doing the design pattern tests (and potentially more), I don't think we can get away with the current scheme for running junit-object tests. Right now we require the test creator to implement a main method with a set of code to trigger the tests to be ran.
In order to facilitate greater control over stages of building the test data and classes I think we need to do one of two things: 1. Add a default main method to the ObjectTestCase which relies on abstract methods to get the subclasses name, this method can then kick off the stages of the test building and etc. 2. Create a test runner which is seperate from the actual TestCase which will be responsible for kicking off building of tests and the running.
any thoughts?
What about using object proxies to trap invocations? It would mean that all classes under test have to be provided by JO but that could be similar to TestNG's @DataProvider scheme.