Skip to main content

30 Days of Postman - for Testers!

 


https://www.pexels.com/photo/white-and-brown-cat-lying-beside-a-laptop-and-toys-5468268/

Photo by Karolina Grabowska from Pexels

 

Working with developer- focused tools can be a challenge for some testers: we may know what the words mean, but haven't used those skills recently enough to make the tasks simple. Or we may not have ever used them, other than at a quick glance to make sure that what we are getting matches what it should be sending. And some give results that require us to go find another team member to help interpret the results.

Being a more-independent tester has always been one of my goals - being able to use the tools that are common in the team, and be able to do at least basic tasks that support my tests with them. Our team used Postman for many of the API tasks that we had, so exploring this tool was a natural fit. There are alternatives it there, both graphical and command line, so feel free to explore! The items that you can do, and tools that help you in other ways , such as Swagger,make API testing not only a chance to explore, but for me served a a way to connect with the team on a different level. Most of them enjoyed teaching, so this was good chance to learn.

I admit - some of the terms and activities may not be as familiar to testers as they are to the development team - this is also a chance to make sure we are using the same terms for activities. Unless you have used either Node or some flavor of JavaScript in your learning, this may slow you down. But that's okay- learning this tool at your own pace without needed to be worried about a deadline may help you learn more - and give you time to set up some scripts that will not only help you, but those in the future that may need them, and quickly.

Working with your developers, once you have tried a few times, is a way to build trust and learning in the team. The skills that this exercise brings can include that you are trying to understand what they experience, as well as the fact that you can be even more valuable to the team. Getting these scripts set up will save everyone time in the future, and make it easier for the next person.

You may be lucky enough to have someone on your team that is skilled with Postman - make sure both of you count this time someplace! It may only be a few minutes a week that you will need, but the fact that their is another person that is skilled will leave them a bit more free time - and you can gain experience in where the tool is used in your organization.

And if you happen to be the only one who uses it? Then you can share this at a lunch and learn, or with your manager - and show the benefit of having these skills. They YOU get to teach: there is no faster way to cement your learning that making sure you have correct answers to questions.


Labels:

Popular posts from this blog

Where Is It? Part 1 - Inputs

Photo by Pixabay from Pexels     I am job-searching, and running into some coding challenges. Most of them are simple - some seem to want one-line solutions that require two cups of coffee and a half-hour to figure out what they want. Others are far above where my skills lie, and these I give a try for, and learn. And then there are the ones that offer, seemingly randomly, a challenge - within my skills (or at least my research skills) - that could be used as part of a larger project that I want to work on. This was the case last week, when I tried for a position that was a bit above what I felt I could do comfortably. The challenge was to let someone enter items, and then give back their location. In a language I am just familiar enough to be a danger to myself in. Happily, and thinking forward about how I could use this as a part of a larger program that would  use something like this to interact with the user. And also, this is command line, and thinking of how to set this up to
Read more

Do Your Tests Wobble?

Image by delo from Pixabay “The green reed which bends in the wind is stronger than the mighty oak which breaks in a storm.”  ― Confucius  I was asked to pair Blog with Lena Weiberg - much to my shock and delight. This was the perfect opportunity to hear another point of view on something, and share it with the wider community.  ~ Part of being a good tester, to me, is making sure I stay aware of the trends in development. Knowing  how the team is working can help get comments and questions to them at the proper times, and has  the information that can be acted on. In this quest, I attended a recent online conversation where the  topic was primarily on the size of 'steps' taken in software development: making sure each step takes  a reasonable amount of time, that it leaves the system in a state that isn't worse than it was before the  change, and that could - if needed - be deployed at this point.  The concept of “wobble”  (I'm not sure
Read more