-
We want 100% coverage as close to right off the bat as possible. While this isn't _strictly_ necessary for MVP, it makes coding a lot more comfortable. We should focus on unit tests, but if possible c…
-
There is a coverage plugin to display test coverage using a diagram.
Consider to create the report and include it into the JGiven report.
-
This part must be performed on a local workstation IDE
Run unit tests (Junit)
Run integration tests (failsafe)
Run code coverage tests (jacoco)
Run BDD scenarios (jgiven)
Run mutation tests (pite…
-
Imagine, I have a multi-module maven project with several modules containing their JGiven tests.
Now in a CI I want to generate a single report out of them.
Currently, the Maven Plugin supports th…
-
In the html app, there is a condition for showing the duration of a step:
```
({{ ::nanosToReadableUnit(step.durationInNanos) }})
```
Would be nice if we could get rid of this conditi…
-
When using kotlin, all stage classes and functions have to declared `open` to get JGiven working.
The kotlin compiler plugin "all-open" can do this for you, which is very convenient. But it requir…
-
**Current State**
Scenario classes have to extend with many generic types:
```java
extends ApplicationPerMethodWebSessionTest, GoogleVerifications>
```
and additional stages can be added via ann…
-
This part must be performed on a local workstation IDE
Run unit tests (Junit)
Run integration tests (failsafe)
Run code coverage tests (jacoco)
Run BDD scenarios (jgiven)
Run mutation tests (pite…
-
**Description**
`dev.aherscu.qa.jgiven.commons.scenarios.GenericTest` fails sometimes.
**Reproduction**
Multithreading issue with Unitils initialization.
Parallel calls to `Unitils.getInstance…
-
Create a freestyle job called "QUALIFY" which:
Sets the value of PIPELINE_VERSION to internal build number and puts the version information on the application main page
Builds/tests/packages and dep…