Experiencing the Keploy API Fellowship: A summary
From the POV of a code geek!
2 min read
Hey everyone, long time no see!
2022 had been an eventful year for me, full of enriching experiences that I would love to share about (someday :P), and the start of 2023 seems no less - getting selected for the Keploy API Fellowship in the first month itself!
For those who might not be familiar, Keploy is a company that is behind the E2E (End to End) software testing framework of the same name. According to the Keploy Official Documentation:
Keploy is an open source e2e testing toolkit for Developers that creates test-cases and data mocks from API calls, making releases faster and highly-reliable.
Now that the training period is almost over, I write this blog as a summary about my experience!
The total program structure
The training program spanned a total of six sessions, each session building on the previous ones - so you have to be attentive! This was the flow of our sessions:
Session 1: About HTTP, HTTPS and APIs
Session 2: A deep dive into APIs and API Requests
Session 4: Using ExpressJS to make APIs
Session 5: API Testing using POSTMan and introduction to Keploy
Session 6: Keploy's workflow for handling E2E testing using the Record and Replay Mechanism.
Each session had a pertaining task to it, either technical (creating a GitHub Repo) or content-based (create a blog/article on a platform). Attendance was taken towards the end of each session.
As a RAD/RAF full-stack developer who had heard about Keploy before, the first 4 sessions were not that hard to understand. The concepts were pretty nicely explained by the DevRel who were pretty proficient at what they do - special mention to Animesh Pathak, Hardik Kumar and Ankit Kumar!
Then came the fifth and sixth sessions, where I learnt about Keploy. I was awestruck by the simple and elegant design that the product entails. I also was curious about how their testing mechanism scales in Cloud-based deployments, and pestered Animesh with questions :-P.
After the six sessions were over, I understood Behaviour Driven Development (BDD), the significance of Stateful End-to-End testing that ensures that requests of the same type elicit same responses for deterministic results! More than that, I actually picked up on the neat little tricks and productivity hacks that they did to get their demos up and running.
It was an insightful training period indeed!
Did you find this article valuable?
Support Anuran Roy by becoming a sponsor. Any amount is appreciated!