java - Reg - Unit Testing and Technology Knowledge -
I'm new to unit testing and I have worked on automating most functional tests (front end using selenium and jmter).
.
I would like to know that if I need a unit test for Java based web applications after seeing in code, then I should have a clear understanding of the underlying technologies like servlet, jsp, ezb, and design patterns; On which application has been created? Or is it just enough to keep knowledge on Core Java, to see the code and understand them and write unit test in Junit
Please provide your suggestions Thank you.
For me, unit tests are two very different things, depending on what you are writing To test whether they are trying to test some test after the test (test-dowry development) before writing or if you are under the test, then it has already been written, after some pre-practice, Very easy to go, while later often very challenging Oga (especially if the code was not developed with testability)
If I suspect, you'll test that the code is already written, Michael Feather is a great resource to look in, in the book, the description of the wings is done in very detail that surround the code How to get the exam so that it can be safely modified and enhanced without changing the inappropriate behavior. There will be many test unit tests for them, but there may be other integration tests - in their case the goal code is to be able to work safely. At any rate, she introduces a great vocabulary for testing related development and provides a good strategy to test that anybody involved in the software testing will be interested in reading.
In relation to the tools, I would suggest learning a mock object library such as knowledge of either or any of the things would be very useful, whether you are checking sublets, EJB or something else. Their purpose is to stand for cooperative classes so that they can provide accurate results, which requires an examination of the subject in an interesting way, without realizing the real partners in the right state to achieve it. for. Personally, I like Jmokit for this and I can say that if you have to write a test for the code already present then it is mandatory.
Comments
Post a Comment