When transforming your test cases into automation scripts, some general rules should be followed: code compiled and build, tests successfully passed, understandable flows, and smooth test structure. Many of today’s concepts, design patterns, and libraries help in achieving a stable automation test suite. Specifically, API automation testing at all testing levels is always relying on some of the popular libraries that can ease the process of writing scripts and understand the test flows. In this post, we are going to…
Posts published in “Tutorials”
Since it’s creation, the JUnit inspired framework is constantly used across multiple projects and organizations. TestNG is a part of many automation testing strategies where different approaches and patterns are used. The open-source framework is not an extension of JUnit, since it is designed to be better than JUnit by eliminating limitations and adding the already existing features from JUnit plus much more features that allow more flexibility when writing a structured test automation framework. To list some of the…
What is assertion? An assertion is a form of validation statement in the programming language which verifies if the given result or outcome is correct and valid. The purpose of using assertions in test automation is to identify if the given outcome of a particular scenario is equal to the actual outcome. In other words, checking the expected vs actual result for a test. If they are not the same then the test would fail with the failure message shown…
What is Cucumber? Cucumber is a test framework that is used for writing BDD tests for web applications in a simple English language text called Gherkin. Tests written in Cucumber can be easily read by everyone within the team whether technical or non-technical individuals. It provides some form of live test documentation that is updated regularly but in the background, there are methods that are mapped and executed with each Gherkin sentence. When BDD comes into the picture, Cucumber is…
When it comes to writing functional API tests with JUnit, we strive to have a more structured and cleaner code that’s easy to understand, flexible to change and having reusable methods. If we can achieve the ones above, then we’re good to go right? Well, that is questionable, depending on the complexity and the scale of what needs to be covered in our automated tests as well as how many steps do we need to perform in order to have…