...
JIRA JQL - JQL filters can be developed using the JIRA's advanced searching functionality e.g. “Sprint = 5”.
mode - This field is set for each scenario in AssertThat and is set as default to Automated - Automated and Manual tests /wiki/spaces/ABTM/pages/725090428.
tags - tag expression filter for scenarios e.g. tags = "(@smoke or @ui) and (not @slow)". More on tag expressions https://cucumber.io/docs/cucumber/api/#tag-expressions
...
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 /wiki/spaces/ABTM/pages/728203292. 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.
...
| Code Block | ||
|---|---|---|
| ||
require 'assertthat-bdd'
task :download_features do
AssertThatBDD::Features.download(
#Optional can be supplied as environment variable ASSERTTHAT_ACCESS_KEY
accessKey:'ASSERTTHAT_ACCESS_KEY',
#Optional can be supplied as environment variable ASSERTTHAT_SECRET_KEY
secretKey:'ASSERTTHAT_SECRET_KEY',
#Required for Jira Server only. Omit if using Jira Cloud version
jiraServerUrl: 'https://mycompanyjira.com'
#Required Jira project id e.g. 10001
projectId: 'PROJECT_ID',
#Optional - default ./features
outputFolder: './features/',
#Optional proxy url to connect to Jira
proxy: 'PROXY_URL',
#Optional - default automated (can be one of: manual/automated/both)
mode: 'automated',
#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)',
#Optional - all features downloaded by default - should be a valid JQL
jql: 'project = XX AND key in (\'XXX-1\')'
)
end
task :upload_report do
AssertThatBDD::Report.upload(
#Optional can be supplied as environment variable ASSERTTHAT_ACCESS_KEY
accessKey:'ASSERTTHAT_ACCESS_KEY',
#Optional can be supplied as environment variable ASSERTTHAT_SECRET_KEY
secretKey:'ASSERTTHAT_SECRET_KEY',
#Required for Jira Server only. Omit if using Jira Cloud version
jiraServerUrl: 'https://mycompanyjira.com'
#Jira project id e.g. 10001
projectId: 'PROJECT_ID',
#The name of the run - default 'Test run dd MMM yyyy HH:mm:ss'
runName: "Dry Tests Run",
#Json report folder - default ./reports
jsonReportFolder: "reports",
#Regex to search for cucumber reports - default .*.json
jsonReportIncludePattern: ".*/cucumber.json"
)
end |
Usage - Command line
...
| Code Block |
|---|
assertthat-bdd-report -h
Usage: assertthat-bdd-report [options]
-a, --accessKey ACCESS_KEY Access key same as env variable ASSERTTHAT_ACCESS_KEY
-s, --secretKey SECRET_KEY Secret key same as env variable ASSERTTHAT_SECRET_KEY
-u, --jiraServerUrl SERVER_URL Jira Server URL (Only for jira server integration) e.g. https://mycompanyjira.com
-p, --projectId PROJECT_ID Jira project id
-n, --runName RUN_NAME The name of the run - default 'Test run dd MMM yyyy HH:mm:ss'
-f JSON_FOLDER_PATH, Json report folder - default ./reports
--jsonReportFolder
-i INCLUDE_REGEX, Regex to search for cucumber reports - default .*.json
--jsonReportIncludePattern
-x, --proxy PROXY_URL proxy url to connect to Jira
-h, --help Show help
-v, --version Show version
-q, --jql [JQL] JQL filter for Jira issues to update with test results |
Example project
Refer to example project for running using Rake assertthat-bdd-ruby-example