The Jmlunit tool should generate a hook that allows it
to get all test cases for a method in a way different
than the usual cross product. This would allow easier
customization and support automatic tools.
I plan to have a strategy-pattern approach to solving this.
The idea is that the current default way of finding test cases
for a method would be the default strategy.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I now think that the best approach for this is to add an
option to only generate these hooks if the user wants them.
Otherwise we have (a) extra code in the JMLTestData file
that clutters it up, and (b) this extra code isn't used, and (c)
the extra code would be out of date easily, if new methods
are added.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=633675
I plan to have a strategy-pattern approach to solving this.
The idea is that the current default way of finding test cases
for a method would be the default strategy.
Logged In: YES
user_id=633675
I now think that the best approach for this is to add an
option to only generate these hooks if the user wants them.
Otherwise we have (a) extra code in the JMLTestData file
that clutters it up, and (b) this extra code isn't used, and (c)
the extra code would be out of date easily, if new methods
are added.