I wondered if it were possible to split the firing of
MyProcessor.init()out of TestRunner.run()so that I have finer
granularity in testing? Maybe I'm abusing init()by what I'm doing in it,
but I'd like to see that run and give control back to my test case for
some assertions and other things, before moving on. In fact, it would be
nice to have granularity for @OnScheduledmethods that way, maybe others too.
TestRunner runner = TestRunners( new MyProcessor() );
runner.setProperty(), etc.
runner.enqueue(), etc.
*runner.init(), etc.**
**runner.onScheduled(), etc.*
runner.run( 1 );
Did I miss a turn somewhere and this is already supported? I've pored
through the test framework Javadoc and missed it?
Russ
