I am trying to automate manual testing of modules in my project. We are working with IBM websphere message queue software We have a trigger component in core Java, when the choice for the availability of the message in the configured queue was executed. During its indefinite period, the trigger component which loop keeps moving. In order to give message in Q, I have written tests in Junket and now I can be able to start / stop the trigger component on demand. The trigger continues on to turn on the component and I do not get control back to check the expected output if the log file is considered to trigger the trigger component when I start it in thread when message processing is not updated Used to be. How can I solve this situation? Your suggestions and directions are highly appreciated. Thanks, -Vinay
I would like to make a manual for your manual build through a few things like Apache ant Will look forward to proceed and see Junit Support.
Once you do your tests that you can run through the ant, you can integrate into a continuous integration container such as Hudson (Hudson- c.org) and make it one timer You can also schedule to run on a code check-in.
For more information on continuous integration, take a look at Martin Fowler's article.
Comments
Post a Comment