Qasim Mahmood’s Post

View profile for Qasim Mahmood, graphic

SDET | QA Automation Engineer | Playwright, Cypress, Maestro, Appium | Python, TypeScript, JavaScript, Java | ISTQB CTAL-TA | MEng Imperial College London

I have not one, not two, not even three, but 𝐟𝐨𝐮𝐫 new automation frameworks that I've recently added to my GitHub portfolio 🙃 It might be cheating because they're all API testing frameworks testing the same site, RESTful Booker (look it up if you want an API to test, it's great!) But nonetheless, here are the four frameworks: - Postman, integrated with GitHub Actions - Playwright with TypeScript - Cypress with JavaScript - Python, using Pytest and Requests I'll be posting about one of them each day this week, just to spread it out a bit First up is Postman, check it out here: https://lnkd.in/e3Y_afYB Postman is generally the de facto API testing tool for most. I've heard there's a bit of animosity building up for it recently, so I'll be trying out Bruno, an open-source alternative, very soon (watch this space!) But essentially, I built a collection with all my API tests in Postman, including validation using scripts and environment variables to store thing like the baseUrl and bearer tokens, then I used Postman's GitHub integration to sync everything across I also added a GitHub Actions workflow file to run all the tests on every push, and you can see a badge with the workflow status on the README Things left to do: - Add a proper README - Add a separate file with test cases - Try out Bruno as an alternative to Postman - Try some more complex API testing sites

GitHub - qasimmahmood95/postman-api-automation

GitHub - qasimmahmood95/postman-api-automation

github.com

To view or add a comment, sign in

Explore topics