Postman: The Complete Guide - REST API Testing
What you'll learn
- Create GET, POST, PUT, DELETE request
- Understand GET vs POST request method
- Work with real-world APIs (Github API, Trello API)
- JavaScript basics for tests
- Write API tests in Postman
- Use data from Excel files (CSV) or JSON
- Use Postman variables to create workflows and scenarios
- Run API tests with Newman in Jenkins, GitLab CI or TeamCity
- Use OAuth2, API keys, tokens, JWT, basic auth
- Test file uploads
- Use mock servers
- Collaborate using Team Workspaces
Requirements
- Basic programming and/or JavaScript knowledge is required (needed for writing tests)
- Basic HTTP knowledge required (address, message body, headers, cookies, ...)
- Basic knowledge about RESTful APIs and JSON
- Basic Jenkins experience, if an integration with Jenkins is desired
- Basic NodeJS/NPM experience (needed for test automation)
- Optional - Basic Docker experience (for Jenkins or Newman)
- A computer with Windows, macOS or Linux is required for viewing the lectures and installing Postman. Using a mobile phone/tablet is not recommended.
- Registering to a few reputable public APIs is required for you to be able to follow along with the course
Description
RESTful APIs (or simply REST API) are everywhere nowadays but at the same time they are getting more complex to get started with: different HTTP methods,, headers, cookies, dealing with file uploads or authentication with api keys, tokens, OAuth and so much more.
But before you start investing time writing code to retrieve the data the API is offering, why not test the request first to make sure everything is working as expected?
This is where the Postman App comes in! Postman allows you very quickly create a request with the required HTTP method and parameters, submit the request and easily inspect the results.
Postman can help if you are developing APIs as well! I have created this course for testing engineers and well as for software developers. Postman can help you during the development of your API as well as after the API is completed, by running tests that make sure your API is still working as intended.
In the first part of the course we will start exploring the features of Postman and continue by writing API tests with the intention of integrating them in a CI server where the tests will run on a current basis.
But this is not the normal course you take part in. Because your needs may be different and because I hate leaving you wondering what to do next, the second part of the course will include user questions and answers to problems that were not yet covered in the course or that are more specific and may not interest everybody.
So let’s look at what you are going to learn:
Start with simple requests and advance towards more complex scenarios
Learn to deal with authentication / authorization mechanisms like Basic Auth, API Keys, or OAuth.
Start writing API tests
Organize tests in collections and share them with your team
Run API tests in Jenkins or any other CI server
You ask, I answer
So after this course you will know how to use Postman as a pro.
Excited to learn Postman? Sign-up up today!
Who this course is for:
- This course is targeted towards testing engineers and developers.
Featured review
Instructors
- 4.6 Instructor Rating
- 50,464 Reviews
- 267,991 Students
- 8 Courses
Agile Enterprise software developer with a strong background in computer science. I believe there is a better way of developing software by using Agile and Scrum.
I like being part of different communities and I am a Postman Supernova and AWS Community Builder.
I have been involved in many open-source projects, including being a member of the Joomla! CMS Bug Squad, Joomla! Stack Exchange moderator and TYPO3 CMS Security Team. As you can guess, I am a dedicated software developer and open source lover.
I decided to join Udemy because of my desire to share my know-how in specific areas.
- 4.6 Instructor Rating
- 46,628 Reviews
- 212,459 Students
- 5 Courses
Let's learn Scrum together. I am an Agile Enterprise Software Developer with a strong background in computer science. I believe there is a better way of developing software by using Agile and Scrum.