Automated testing has plenty of advantages, but also plenty of pitfalls. Since it is “automatic”, any mistake made in the set-up or procedure of testing is likely to carry throughout the entire testing process, dooming the testing to be a failure. This blog post by Ken Miller explores just a few of the ins-and-outs of API automation testing. These tips cover things like planning the test, organizing the entire process, setting priorities, development, configuration, and validation. Setting the priorities is often overlooked, however, and this is what Miller has to say about that:
As and when the test cases are developed, against the popular practice of going straight away to an invalid test, it is important to set priorities. It makes easier for the testers to put more emphasis on the mainline cases at first, before opting for any other issue.
In fact, one should ascertain the test cases that need to be conducted at first. This purely depends upon the instinct of the tester. It is the tester who will have to ascertain which cases that will have to be tested first. Prioritizing the tests will only make the process simpler.
Miller also explains how organizing the testing must occur early and effectively. Organization is key in any automated process, and spending time on this step is likely to save quite a bit of time an effort later in the testing lifecycle. Read the full post here: https://softwaretestingtips2.wordpress.com/2014/04/30/best-practices-in-api-automation-testing/