People often say, “You know you know what you know if you can explain it to somebody else.” Last week, my team had a huge win doing exactly that.

Hi. I’m glad you’re here. The truth is, I don’t do any such thing. I have an AWS Console and I know what AWS Infinidash is. Hint: It’s not really a test framework despite what you may have heard about it. All good things I hope.

For today’s blog post, I’m taking a little break from API testing to convert a live presentation I once gave into written form. If you’re not a developer, the content about version control, or git, won’t be relevant, but you can still follow along without those bits. Having a long career in technology will almost certainly mean continuing education of some sort. To me, the never-ending supply of things to learn is one of the things I love about working in tech.

If you’re following along from your own computer, by the end of Part 2, you should have a working API Request that includes code to test the Request and report the test results to Jira’s Zephyr Scale app. In addition to everything we used in Parts 1 and 2, you should also have an idea of what else you could test to ensure the Quality of the API you’re testing.

If you’re following along from your own computer, by the end of Part 1, you should have a working Postman request that POSTs a test case execution result to a test cycle in Jira’s Zephyr Scale app. If you haven’t caught up from Part 1 yet, start there. In addition to everything we used in Part 1, you should also have an API you can work with.

One of the things I’m known for saying often is, “Don’t put your planes in the air until they have a place to land.” With this in mind, the first thing I did is create a place to record all my results, a landing strip if you’ll follow the metaphor.