Karate Labs Reviews

Intuitive syntax and built in performance testing capabilities.

Enhancement in default reporting with customisation.

Parallel execution and built in performance testing capabilities accelerate test cycle.

The strong focus on assertions makes large responses easy to validate. The human-readable BDD syntax allows testers new to automation to start contributing without having to know programming. The interop for Javascript syntax makes it easy to code very powerful functions into a single line, directly in the test.

As with any framework that is not pure code, the Karate DSL can feel restrictive at times. Although I believe if you leverage Karate's Java API you can get closer to pure code.

Quickly providing feedback to development teams on code changes. Providing an easier way for developers to test their code. Teaching automation testers skills such as Git, pull request reviews, how to easily run and debug tests using an IDE. Allowing easier onboarding of manual testers to the automation side, and making it easier to pull developers into contributing to test automation.

Karate DSL is recently became the 'Go to solution' for any test automation needs, especially when it comes to API testing.

120+ API services automated with Karate for my first project in a short time and after that, Karate became essential tool in my further assignments up until now.

Karate is incredibly simple to learn and use. It's well documented, and its creator, Peter Thomas, is readily accessible via Stackoverflow.

Karate DSL does not currently support writing Gatling performance tests in Java -- Scala is still required. Adding a Java option would be a significant enhancement.

Quality assurance engineers often lack the technical background of their development partners, and if they're asked to use tools such as Selenium, Cucumber, JGiven or JBehave to write automated tests for their APIs and UIs, this poses a significant challenge. Karate solves this problem by allowing QA folks to focus on what they do best-- ensuring quality in the applications they support -- and forget about struggling to become a developer to help their team from a testing standpoint.

.It's open source and easier to use for non programmers

Compatibility issue while UI and performance testing

Tagging built in tools and we can run multiple test in parallel

How the environment is almost ready to run the tests, as user you have reports, good logs messages and a quick execution

The price, it can be kind of expensive and this can influence that other users prefer choosing cheaper options or free options (Ex. Playwright)

The readability of the tests, they are easy to understand and allows me to quickly implement other tests