API Testing journey

 

API Testing journey


  I've been working on learning API testing for quite some time. I was only aware of the acronym API, which stands for application programming interface, until 2022. I started my search on Google because I wanted to learn more than that.


 I Completed the following courses on various education platforms:


1. Coursera — Postman - Intro to APIs (without coding)

2. Coursera — Start Your API Testing Journey With Postman Tool

3. Udemy —  REST APIs with Postman for Absolute Beginners

4.  MOT -https://github.com/g33klady/TodoApiSample/tree/main/Resources. https://github.com/g33klady/TodoApiSample

5. LinkedIn Learning — API Testing Foundations

6. Test Automation university: https://testautomationu.applitools.com/exploring-service-apis-through-test-automation/

7. Test Automation university: https://testautomationu.applitools.com/python-api-testing/



   Postman was discussed as a tool for API testing in the first three courses. In order to test an API endpoint, I needed to know what to test. For a complete beginner like me, the LinkedIn course "API Testing Foundations" provided a fantastic introduction.


  I found yet another guide for what and how to test an API when I attended a session led by the Ministry of Testing. Resources can be found at https://github.com/g33klady/TodoApiSample/tree/main/Resources.


   At this point, I was stuck at testing APIs which requires authentication and authorization.I learned about authentication and authorization from the following books:


  The book "Automating and Testing a REST API" by Alan Richardson was the next thing I read and practiced. I attempted it with Python even though the book contains examples in JAVA.


  After that, I was reading Kristin Jacky's "The Complete Software Tester." She has a dedicated section for API testing in her book. With Postman and Python, I practiced the application from that book. Here, at API testing with Bearer token, I've documented my testing this time.



  From there, there was no turning back. During the holiday break, I had automated a user testing flow using concepts from API chaining, a collection runner, environment variables, etc. I'll choose a test flow soon and create a new blog post.


  Where am I now, then? Anticipating my “15 Days of Postman” badge.  I tried to finish all of the challenges in the 15-day Postman test challenge for API testing experts over the weekend. It was an excellent opportunity to learn and gauge my proficiency. 

Comments

Post a Comment

Popular posts from this blog

API testing with Bearer token

Image
  API testing with Bearer token  HTTP Authentication Schemes:   HTTP Authentication verifies the user's eligibility to access the web resource. It involves HTTP header-based communication between the client and the server, with the server requesting the user's credentials for authentication. I'll start by writing about bearer tokens because I recently learnt about them.   When a user logs in, the authentication server generates a token known as a bearer token. This token should be sent in the header of the client's subsequent calls .This token will shortly expire; in such circumstances, a new token must be generated. Application using Bearer token: The Contact List App is a small program that Kristin Jackvony created for testing. The APIs for this application authenticate users using bearer tokens. API documentation can be found https://documenter.getpostman.com/view/4012288/TzK2bEa8 I started by exploring the app's functionality , making a list of prospective te
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