In the world of agile development, automation-first mindset helps in reducing repetitive task and enables testers to focus on exploring areas that would not have been explored given the time crunch. But, hey, we have so many libraries/tools/frameworks which claims to provide faster feedback. Typically, most of the projects falls into low automation ROI because automation is happening at wrong layer.
Karate DSL (Domain Specific Language) stands out from rest of the tools because of the below points.
- Makes use of easy-to-understand Gherkins language.
- It requires relatively less technical programming knowledge like Java.
- It is based on the popular Cucumber standard
- Unlike cucumber-JVM , in Karate , one can call scenarios from other features
- Easy to create a framework.
- Parallel testing is the core functionality that is provided by the Karate itself, hence we need not depend on Maven, Gradle, etc.
- UI for debugging the Test.
- Calling a feature file from another file.
- Provides supports for the Data Driver Testing that is built in-house, hence no need to depend on external frameworks.
- Built-in Native Rest Reports. Plus, it can be integrated with the Cucumber for better UI Reports and more clarity.
- Provides in-house support for switching configuration across different testing environments (QA, Stage, Prod, Pre-Prod).
- Seamless support for CI/CD integration that can be useful.
- Capable of handling various HTTP calls
In this session, we will cover
Set Up
Basics of API automation in Karate covering
- GET Request
- Url and Path
- Simple Assertions
- POST Request
- DELETE Request
- Calling another feature
- Assertions
- Fuzzy matching
- Advanced Features
- Usage of Hooks
- Parallel executions
- Cucumber reporting
- JSON transformation
- Schema validation
Event url will be published on 27th Feb 2021
Time: 2:00 PM to 4:00 PM IST