
Clarify the rest API definition and its architectural constraints using concrete examples like Spotify, Jira, and Swagger Pet Store, including http post requests and json bodies.
Explore representational state transfer and its six constraints for web APIs. Learn how client-server architecture, statelessness, cacheability, layered systems, code on demand, and a uniform interface enable restful services.
Explore client-server architecture and how rest APIs enable services, detailing server and client roles, request-response flow, and examples like maps using geo data.
Learn the anatomy of an HTTP request by mastering URL structure, domain names, IP addresses, and path, with request methods like GET, POST, PUT, and DELETE to test REST APIs.
Identify the http response structure by focusing on the status code and response body, including the three-digit code, its class (like 2xx), and how 200 signals success.
Learn Postman fundamentals by sending requests, viewing responses, and saving them into a collection; explore import, cURL data, endpoints, and basic request methods (get, post, put, delete).
Solicit feedback to improve the course and motivate the team for future videos; leave ratings via the header or hamburger menu, using five-star praise or three-star feedback.
Explore API testing fundamentals with exploratory testing in Postman, designing and executing tests from theoretical knowledge, creating a happy path and a negative test, and saving responses for future references.
Explore a get endpoint through exploratory testing in Postman, validating happy path and negative cases against Swagger, documenting required data setup and team discussions for future data-driven tests.
Discover how to use Postman to turn manual exploratory testing of post, get, put, and delete API endpoints into automated happy-path tests with validation of status, structure, and data.
API testing is a very contradictory topic. And it happens that you worked for years as a Manual tester and never faced the APIs or had a need to test those. But it can change at any moment.
Let's imagine the scenario. You passed an interview at a new company. You are a good person and they are good people. They liked you and they liked you. Even more, they offered good money.
During the interview, they said that the project is very cool and that you already know everything to start work. That the project has excellent documentation and a cool team, and all SCRUM processes are perfectly implied.
Two weeks have passed. And it's your first working day at your new job. You receive a letter from the manager. He congratulated you and says that you were expected and advertised a lot. That you are a testing expert. And in the email, he sends the user story. He says that she should be tested tomorrow. But since you are an expert, it will not cause difficulties.
You are the expert. That is true. So you check the story.
And you do not understand a single word there. In the story, a lot of things have been mentioned some endpoints, base URLs, JSON body, HTTP response code, and CURL. And all of this is new to you. You have never worked on the API level. But do you need to finish testing by tomorrow? What are you going to do?
You are the expert!
You will test the story with the help of this course!
Even more, you will have time for a cup of coffee!