Skip to content

Commit

Permalink
Update config example.
Browse files Browse the repository at this point in the history
  • Loading branch information
ueslialmeida committed Nov 16, 2021
1 parent 2e25447 commit a881720
Showing 1 changed file with 16 additions and 13 deletions.
29 changes: 16 additions & 13 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,28 +1,29 @@
jira-codeception-extension
=============================
# jira-codeception-extension

This package provides an extension for Codeception to create issues in Jira automatically when a test fails.

### How it works?

When you run a test and it fails the extension will connect with your Jira instance through the Jira API and create an issue containing the data generated by Codeception at the moment of the failure. The number of issues created will vary depending on the number of failed tests, if two tests failed then two separated issues will be created.

The issue will contain the following data:
- Test Name
- Failure Message
- Failed Step
- File Name

- Test Name
- Failure Message
- Failed Step
- File Name
- Stack Trace

### Configuration Example

This extension creates a Jira issue after a test failure. To use this extension a valid Jira configuration is required.
This extension creates a Jira issue after a test failure. To use this extension a valid Jira configuration is required.

- host: A Jira instance.
- user: A valid user that has permission to create issues in the specified project.
- token: A valid token for the specified user. The API will not accept the user password so a token is required. You can create a token in the user configuration panel, for more information follow the Jira official documentation [here](https://confluence.atlassian.com/cloud/api-tokens-938839638.html).
- projectKey: A valid Jira project key (e.g. TA, ZTE, ETC).
- issueType: Usually the issue is created as a Bug but you can change it for Task or another valid issue type available in your Jira instance.
- debugMode: In case you are creating tests or debugging tests you may not want to create issues (and I don't recommend it) so setting this config to true the extension will not create issues in production set it back to false.
- host: A Jira instance.
- user: A valid user that has permission to create issues in the specified project.
- token: A valid token for the specified user. The API will not accept the user password so a token is required. You can create a token in the user configuration panel, for more information follow the Jira official documentation [here](https://confluence.atlassian.com/cloud/api-tokens-938839638.html).
- projectKey: A valid Jira project key (e.g. TA, ZTE, ETC).
- issueType: Usually the issue is created as a Bug but you can change it for Task or another valid issue type available in your Jira instance.
- debugMode: In case you are creating tests or debugging tests you may not want to create issues (and I don't recommend it) so setting this config to true the extension will not create issues in production set it back to false.

Configuration 'codeception.yml' example:

Expand All @@ -36,4 +37,6 @@ Configuration 'codeception.yml' example:
token: Tg7womaGGFpn9EC16qD3L7T6
projectKey: JE
issueType: Bug
label:
- autotest_bug
debugMode: false

0 comments on commit a881720

Please sign in to comment.