Skip to main content

Improve your Postman skills using the in-app Postman lessons

Did you know that Postman had in interactive in-app learning center? You can opt-in to any lesson to improve or practice your Postman skills.

From the announcement:

When you enter the learning center in the app, you’ll see a library of interactive lessons that range from beginner to expert level. We designed the learning center to track your progress, so your lessons will always be geared to your skillset. In addition, we are consistently adding new lessons. Your learning center will automatically populate with new and relevant material for you to master. 

Here are some things you can learn right now on Postman’s in-app learning center

  • Designing and mocking APIs (2 lessons) – Designing and mocking your APIs before you build them helps you define dependencies, create contracts, and identify expected functionality as well as potential problems.
  • Debugging and manual testing (4 lessons) – Manually testing and debugging your APIs is a great skill, and it’s the first step on the way to automation!
  • Automated testing (4 lessons) – Save time by using Postman’s powerful test scripts to automate your tests.
  • API documentation (1 lesson) – Postman allows you to automatically create beautiful, web-viewable documentation right from your collection.
  • Monitoring (1 lesson) – Monitoring allows you to create automated tests that monitor your APIs on a custom schedule. You can monitor for uptime, responsiveness, and correctness.
  • Collaboration (1 lesson) – This lesson will show you how to use Postman’s tools to strengthen your team’s collaboration efficiency.

To get started you only have to click on the Learn button in the right bottom corner of your Postman app:

After logging in, you’ll see a list of all available lessons:

Choose a lesson from the list and click Learn to get started:

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...