In the previous post, tutorial, I explained the solution of how to add logs for the cucumber JSON report. In the current post, I will try to make an easy explanation that will cover the JUnit cucumber XML report problem where no logs are displayed. At the same time, I will reuse the implementation from
As you may know by default pretty cucumber reports don’t save log messages in the cucumber.json file by default in order to display more information in the generated HTML report. This post will cover this function via declaring a java Appender in order to store log messages in the cucumber.json file. Before starting I would
As software engineer, We all face some errors/exceptions while writing code! So what do we do when we face such a problem? If we are not sure, We google for solutions immediately. Don’t we? We google because we know that we would not be alone and someone would have already found the solution, for the problem we
As you may know by default pretty cucumber reports don’t have informative log messages in the report. In order to achieve this we will use MDC. What is MDC Base on documentation of logback MDC is deciphered as Mapped Diagnostic Context. MDC lets the developer place information in a diagnostic context that can be subsequently retrieved by
First of all, I want to mention that this post continues the previous one where we have added AOP to execute some additional logic on cucumber steps. My recommendation will be to read mentioned post. Let’s start… About Spring Profile From official documentation a profile has the following role:Spring Profiles provide a way to segregate
Hi folks , this post is more a continuation of Cucumber 6 Spring Integration, in case you didn’t read Cucumber integration post, please do for better understanding. In this post we will extend the existing project by adding a useful functional of logging execution time for every cucumber step, without adding making any changes in
As a software engineer, We all face some errors/exceptions while writing code! So what do we do when we face such a problem? If we are not sure, We google for solutions immediately. Don’t we? We google because we know that we would not be alone and someone would have already found the solution, for the problem
Cucumber is a very powerful testing framework written in the Ruby programming language, which follows the BDD (behavior-driven development) methodology. It enables developers to write high-level use cases in plain text that can be verified by non-technical stakeholders, and turn them into executable tests, written in a language called Gherkin. And the Cucumber-Spring Integration is intended to
How to Share Test Context between Cucumber Steps, in this post we will explain it and share our implementation Scenario Context class holds the test data information explicitly. It helps you store values in a key-value pair between the steps. Moreover, it helps in organizing step definitions better rather than using private variables in step definition classes.
Today we are going to jump a little bit in CI/CD with a generic jenkins runner based on cucumber tags. In this post will be detailed explained how to configure the runner and how to create the generic profile on real project, let’s start… Creating maven profile based on failsafe plugin to run CucumberRunner. The
