This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Would you mind sharing your thoughts regarding the use of TestMaker as the sole testing tool in the book (I've understood that the TestMaker is the only tool used in the examples?). You see, for some reason I'm getting a bad vibe about the book being about TestMaker and not about testing web applications in general.
I know many people have written good reviews on it, but I'd still appreciate it if I could hear your analysis about how useful the book is for someone who will not use TestMaker but an alternative set of tools?
Hi Lasse: I love a good technical book. Over the years I've bought a lot of them. Some have been the kind of book that is basically a detailed reference guide to a very specific topic. Others are an introduction to a new technology or a new way of doing something. In Java Testing and Design (JTD) I cover the high level issues of testing services and also gives you code-level examples.
The goal of the book is to make this case: Delivering service excellence requires a new level of cooperation between software developers, QA technicians, and IT managers. JTD defines services as any software application that is accessible over a routed network using open protocols. JTD is a book about testing services, including Web applications, Service Oriented Applications, and n-tier applications. JTD begins with testing methodology, covers protocols and architecture decisions, and delivers code-level examples in TestMaker scripts.
TestMaker is a framework and utility that is composed of a number of open-source libraries and tools. The book uses TestMaker to show you by example how to accomplish testing tasks. The examples can easily be applied to other testing tools, languages and platforms.
For example, chapter 7 talks about the move developers made from HTTP applications through XML-RPC and into SOAP-based Web Services. The chapter shows the reasons why XML-RPC is cool and appropriate applications for XML-RPC. It then covers the things that typically go wrong with XML-RPC to give you some thoughts on how to test an XML-RPC application. The chapter then presents a TestMaker script showing how to make an XML-RPC call. TestMaker uses the Apache XML-RPC library. So, the example script shows by example how Apache XML-RPC could be used in a Java application too.
The book breaks down into three parts: JTD starts with an understanding of the reasons the existing testing methodologies fail to deliver excellent services. This part describes a test methodology and several techniques for measuring service excellence. The second part introduces the technologies used to deliver scalable and well performing services, make the case for where they are appropriately used, talks about the problems, and then shows a how-to example in code. The third part of JTD shows three case studies of how the methodology is applied to solving enterprise scalability, regression, functionality, and quality-of-service problems in information services.
I hope this answers your question and concern. Feel free to reply if it was off-the-mark.
Thanks for your interest in Java Testing and Design.
---<br />Frank Cohen, <a href="http://www.PushToTest.com" target="_blank" rel="nofollow">http://www.PushToTest.com</a> phone: 408 374 7426<br />Enterprise test automation solutions to check and monitor Web-enabled <br />applications for functionality, scalability and reliability.
Joined: Jan 23, 2002
Thanks for a quite comprehensive answer, Frank.
This paragraph in your reply raised further questions, though:
Originally posted by Frank Cohen: The book breaks down into three parts: JTD starts with an understanding of the reasons the existing testing methodologies fail to deliver excellent services. This part describes a test methodology and several techniques for measuring service excellence. The second part introduces the technologies used to deliver scalable and well performing services, make the case for where they are appropriately used, talks about the problems, and then shows a how-to example in code.
Dare I ask a 10-word summary of what "existing testing methodologies" you're referring to here?