Posts in this welcome thread are not eligible for the drawing.
Joined: Apr 10, 2006
Hi Cedric and Hani, Welcome to the forum. One query: Why is the name of the book kept "Next Generation Java Testing"? For me it sounds confusing whether the book will tell me about any testing tool built in Java or does it really tells about testing Java applications? Again, what type of testing does it cover? Does it focus on writing JUnit TCs?
Joined: Oct 12, 2004
Originally posted by Biju Kumar: Hi Cedric and Hani, Welcome to the forum. One query: Why is the name of the book kept "Next Generation Java Testing"? For me it sounds confusing whether the book will tell me about any testing tool built in Java or does it really tells about testing Java applications? Again, what type of testing does it cover? Does it focus on writing JUnit TCs?
The name is derived from TestNG, which stands for "Next Generation".
The book illustrates a lot of concepts starting with unit testing but going beyond, and covering topics like functional, performance, multithread, etc... testing.
I have been working as a software developer in China for just under 5 years in two separate and large international companies. Both companies are here to get the "China Price" for research and development and both appear to have very similar problems, i.e. quality.
Both companies see testing, as the answer to their quality problems, but theory and execution seem be miles apart.
Problem 1, Testing is boring. It must be because in my previous company and current, if you ask a tester if they like their job, they say "no, it's boring" and they would rather be developers. In fact my previous company would do a written exam during interview day and those with high scores became developers, those with low scores became testers. In my current company I asked where the tests are located on our Clearcase server and was told there aren't any. Development time pressure meant there was no time to write any. The project I joined is 7 years old :-)
So will this book make testing sound sexy?
While this question may sound flippant, it is not, until testing is seen as sexy and cool and fun (like software development), it will not attract talented people. Since you are both talented, what attracted you to testing?
Does this new framework provide one type of interface for all of this testing (the xml file), thus reducing test extension setup time?