Web Services API Testing Books

10Here are some books you might find useful when developing your web services API testing strategy.

The Art of Application Performance Testing by Ian Molyneaux — This book was just released and I found it an outstanding conceptual overview of performance testing a web based application. The book does a great job of reviewing the various types of performance testing, the key performance indicators, and the various steps needed throughout the performance testing process. I particularly liked the various checklists. A short book, at around 130 pages, I’d rate it 9 on a scale of 10.

How to Break Software by James Whittaker — This is software testing 101 put in the context of a series of attacks on a software application. The book presents about 20 attacks, which cover most of the fundamentals of testing, such as “Find input that may interact and test combinations of their values”. About 170 pages. An easy to read, well organized, although I found the “attack” notion a bit distracting. I’d give this a 9 on a scale of 10.

How to Break Web Software by Mike Andrews and James Whittaker — I was a bit disappointed in this book in that I thought that it primarily covered functional testing and had a dedicated chapter on web services. In reality, 99% of the book covered security testing. However, the security testing was covered quite well using the same “attack” approach as noted in the previous review. I’d give this one an 8 on a scale of 10.

Testing Applications on the Web by Hung Nguyen, Bob
Johnson, and Michael Hackett — This book is a bit dated, with the last revision in 2003. Nevertheless, it thoroughly and extensively covers almost all the basics of Web technology and web testing in its 600 plus pages. It does not deal with some of the more recent web developments such as Ajax, mashups, Web API’s, and Flash. I’d give it an 8 out of 10 due to its dated nature, otherwise it would easily get a 10.

Although not a book, I found a publication on a proposed framework work for security testing web services published by SIFT Information Security Services. This is pretty amazing document with very detailed test cases documenting a very wide range of threats to web services. I actually found this more useful than any of the books above with respect to security testing web services.

(This article was originally published on https://www.qualitylogic.com/community/index.php/web-services-api-testing-books/.)

Jim Zuber

Jim Zuber is a co-founder of QualityLogic and the company’s Chief Test Architect. Many of the testing products architected by Mr. Zuber and released by QualityLogic over the past 20 years have become de facto testing standards in the smart grid, imaging, facsimile, and telephony

Jim Zuber
Jim Zuber is a co-founder of QualityLogic and the company’s Chief Test Architect. Many of the testing products architected by Mr. Zuber and released by QualityLogic over the past 20 years have become de facto testing standards in the smart grid, imaging, facsimile, and telephony industries.

The Related Post

Social APIs are omnipresent and create special cases for testing. If you understand API testing, especially web service type APIs, testing social APIs is easy to grasp. The use of social APIs makes them a special case. They are omnipresent and very well understood. What this means is you need to have a good understanding ...
APIs are subtly altering our expectations that there should be an app for everything. The concept of disruption has been given regal status across businesses, startups, and tech circles in recent years. With such great emphasis placed on change, user experiences are inevitably facing evolution as well. Application programming interfaces or APIs have great transformative powers to disrupt business, but are ...
 Understanding the pieces of the web service testing puzzle can make testing easier For people wanting a broader understanding of more pieces in the web service testing puzzle, here is a breakdown of the various possible components of an API.
APIs are the unsung hero of our connected world We live in an exciting age of intelligence, where progress moves at the speed of imagination. We are connected to the world and one another like never before. API (Application Programming Interface) is the unsung hero of our connected world. Here’s everything you need to know ...
These are the popular authentication methods in TestArchitect Authentication in API testing is usually a complicated subject for both developers and testers since it requires extensive knowledge on various types of security protocols and encryption algorithms.
An overview of web service testing solutions for traditional or non-technical testers. Much has been written on the technical execution of API tests, yet there are gaps in the details of what tests to design and how to design them. The articles tend to either get too technical too fast, or are too vague and ...
Lack of information and access to information isn’t an issue with web services. Web service documentation is widely available. Overview     One of the major persistent complaints from people who test is lack of information and lack of access to information. Luckily this is not the case with web services. If in the rare case with ...
An API provides much of the functional capabilities in complex software systems. Most customers are accustomed to interacting with a graphical user interface on the computer. But, many do not realize that much of the functionality of a program comes from APIs in the operating system or the program’s dynamic-link libraries (DLL).
API testing is different from GUI testing, but it doesn’t take long to master. What is an API? API is an acronym for Application Programming Interface. It enables communication and data exchange between two separate software systems. A software system implementing an API contains functions/subroutines which can be executed by another software system.
API testing has long been misunderstood as well-confined in the territory of developers. It’s natural to think that we must write code to test our code. However, it doesn’t have to be that way anymore. Business testers who have deep domain knowledge are now able to take on the challenges of API testing without coding. ...
Summary Remember that Agile is not an SDLC. Neither are Scrum and XP for that matter. Instead, these are frameworks for projects; they are built from practices (for example, XP has 12 core practices). Scrum and XP advocates will freely recommend that you pick a few practices to implement, then keep what works and discard ...

Leave a Reply

Your email address will not be published. Required fields are marked *

Stay in the loop with the lastest
software testing news