...
The AssertThat - BDD Test Automation in Jira will parse the results of the cucumber json file and load them so that the results can be viewed in Jira alongside the user stories - Test Execution status for User Stories. The automated test results will automatically be linked to existing defects and the results loaded into the reporting tool. The failed tests can then be easily reviewed and assigned for further analysis - Automated Test Report Analysis.
Mandatory fields
The only mandatory field required is the projectId. The following parameters are also required however can be passed as environment variables - ASSERTTHAT_ACCESS_KEY and the ASSERTTHAT_SECRET_KEY. All 3 parameters are available from the AssertThat Configuration page - AssertThat Configuration.
Usage
We recommend running cucumber tests on integration-test phase as
...
| Code Block | ||
|---|---|---|
| ||
<plugin>
<groupId>com.assertthat.plugins</groupId>
<artifactId>assertthat-bdd-maven-plugin</artifactId>
<version>1.7.0<3</version>
<configuration>
<projectId>
<!--Jira project id e.g. 10001-->
</projectId>
<!--Optional can be supplied as environment variable ASSERTTHAT_ACCESS_KEY -->
<accessKey>
<!-- ASSERTTHAT_ACCESS_KEY -->
</accessKey>
<!--Optional can be supplied as environment variable ASSERTTHAT_SECRET_KEY -->
<secretKey>
<!-- ASSERTTHAT_SECRET_KEY -->
</secretKey>
<!--Optional can be supplied as environment variable ASSERTTHAT_TOKEN -->
<!-- Jira API token (for DataCenter only) as an alternative to accessKey/secretKey basic auth -->
<token>
<!-- ASSERTTHAT_TOKEN -->
</token>
<!-- Used for jira server integration only. If using cloud remove this option-->
<jiraServerUrl>https://mycompanyjira.com</jiraServerUrl>
</configuration>
<executions>
<execution>
<configuration>
<!--Optional - default ./features-->
<outputFolder>src/test/resources/com/assertthat/features</outputFolder>
<!--Optional - all features downloaded by default - should be a valid JQL-->
<jql>project = XX AND key in ('XXX-1')</jql>
<!--Optional - default automated (can be one of: manual/automated/both)-->
<mode>automated</mode>
<!--Optional - tag expression filter for scenarios. More on tag expressions https://cucumber.io/docs/cucumber/api/#tag-expressions-->
<tags>(@smoke or @ui) and (not @slow)</tags>
<!--Optional - default cucumber (can be one of: cucumber/karate)-->
<type>cucumber</type>
<!--Optional - whether the phase is enabled (default is true)-->
<enabled>true</enabled>
<!--Optional - prepend ordinal to feature file name on download (default is true)-->
<numbered>true</numbered>
</configuration>
<id>features</id>
<goals>
<goal>features</goal>
</goals>
<phase>pre-integration-test</phase>
</execution>
<execution>
<id>report</id>
<goals>
<goal>report</goal>
</goals>
<phase>post-integration-test</phase>
<configuration>
<!--Optional - default ./report-->
<jsonReportFolder>target/report/surefire-reports/cucumber/</jsonReportFolder>
<!--Optional - default - **/*.json -->
<jsonReportIncludePattern>**/cucumber.json</jsonReportIncludePattern>
<!--Optional - default cucumber (can be one of: cucumber/karate)-->
<type>cucumber</type>
<!--Optional - all Jira tickets will be updated with test results by default; when JQL is provided only filtered tickets will be updated -->
<jql>project = XX AND key in ('XXX-1')</jql>
<!--Optional - whether the phase is enabled (default is true)-->
<enabled>true</enabled>
</configuration>
</execution>
</executions>
</plugin> |