Learning Resources for API testing

 Learning Resources for API testing

1. https://www.udemy.com/course/python-sdet-rest-api-automation/learn/lecture/21316794?start=0#overview. 

2. https://www.udemy.com/course/api-with-postman-for-absolute-beginners/learn/lecture/23890614?start=15#overview

3. https://www.coursera.org/learn/laura-gemmell-intro-postman-apis/home/welcome

4. https://www.coursera.org/learn/start-your-api-testing-journey-with-postman-tool/home/welcome

5. https://www.linkedin.com/learning/api-testing-foundations/stand-out-as-an-api-tester?autoplay=true

Although the above courses mentioned above cover how to use postman for API testing, than API testing approach.


Here are some other resources I found for API testing:

1. https://github.com/g33klady/TodoApiSample/tree/main/Resources. https://github.com/g33klady/TodoApiSample

2. http://katrinatester.blogspot.com/2015/09/api-web-services-microservices-testing.html

3. Manning Early Access Program Testing Web APIs, is another book, I'm yet to start

4. https://club.ministryoftesting.com/t/30-days-of-api-testing-day-1-define-api-testing/19570


Rest API testing Checklists

1. https://www.kennethlange.com/rest-api-checklist/

2. http://testingisbelieving.blogspot.com/2013/11/johnny-mnemonic-iceovermad.html

3. https://www.sisense.com/blog/rest-api-testing-strategy-what-exactly-should-you-test/


Practice websites for API testing

1. https://swapi.dev

2. https://dev.to/promode/7-demo-websites-which-you-can-use-to-perform-api-testing-1p6c

3. https://developer.atlassian.com/cloud/trello/rest/api-group-actions/




Comments

Post a Comment

Popular posts from this blog

  What I noticed after starting to blog    “ Reading maketh a full man; conference a ready man; and writing an exact man” –Francis Bacon  In summer 2022, I was on the lookout for ways to improve my testing skills. From LinkedIn, I found various testers talking about getting trained by Ajay Balamurugadas . I reached out to Ajay. After a meeting, he agreed to train me 😀.  The training started, and I was making steady progress. Ajay questioned me after a few sessions if I had ever written a blog and urged me to do so right away. I wasn’t ready for it. Here is why...   Usually, Slack and email are the places where I write (or type 😜). Most of my responses would consist of no more than four words per sentence!!  My status reports and testing notes are the longest documents I produce. Naturally, I wasn't prepared, so when I heard about starting a blog, I found it amusing. One fine day I sat and started, I was just typing and deleting.. Couldn’t move p...
Read more

My first time attending a software launch party

Image
  Postman celebrated the introduction of Postman Flows this week in San Francisco, on August 16th 2023. Following the release of Postman Flows a few months ago, Beth Marshall posted a YouTube video explaining how testers might use it for API testing procedures.   Ever since I started my API testing journey, I've been watching for Postman's announcements, challenges, You Tube Live sessions, and demonstrations. So I made the decision to go to this event as well.    When I arrived , Postman Flow was being used to welcome every registered guest. My name flashed on the welcome board when I clicked Run on their flow they had created after signing in (I forgot to take a picture of it). Greetings flow Two customers demonstrated how they are utilizing Flows to address issues and open up new possibilities. One of them includes a flow designed specifically for integration testing.   I was able to use Flows to design my very own, uniquely branded Postman YETI and ...
Read more
  Observation: How it has helped me as a tester? In one of the chapters of her book, "Explore IT," Elizabeth Hendrickson discusses observation and how it is crucial for exploratory testing. Checking logs for surprises is one technique to observe during testing. I was brought back to my days as a mid-level test engineer while reading it. On the user's side, the product appeared to be relatively straightforward, but it actually had a sophisticated architecture and a lot of moving components. For this product, there were very few user interactions; everything took place in the background, and logs were essential for troubleshooting. When I first discovered a bug, I would gather proof—reproducing steps, error logs—most often grep 'error' log files—and screenshots—and be prepared to report the issue. My manager would ping me with questions like, "Did you try to reproduce the bug in another test combination?" and "Did you check that?" and “Did you tr...
Read more