...
The fields for projectId , accessKey and secretKey are available from the AssertThat Configuration page - AssertThat Configuration. In addition to using tags to filter the scenarios for execution, the plugin provides 3 optional fields:
...
| Code Block |
|---|
java -jar assertthat-bdd-standalone-1.9.411.jar Required options: a accessKey, secretKey, stoken, iprojectId, [-ffeatures Download features, -r Upload reportfetures] usage: assertthat-bdd-standalone-1.9.4.jar -a,--accessKey <ASSERTTHAT_ACCESS_KEY> Access key -f,--features secretKey <ASSERTTHAT_SECRET_KEY> Secret key -token <ASSERTTHAT_TOKEN> Jira API token (for DataCenter only) as Downloadan featuresalternative -h,--help to basic auth -features Download Display helpfeatures -i,--projectIdhelp <ID> Jira project id -j,--jsonReportFolder <FOLDER PATH> Display help -projectId Cucumber<ID> json files folder -m,--mode <automated|manual|both> Features to download -b,--tags <tags expression> Jira project id -mode <automated|manual|both> Tags expressionFeatures forto scenariosdownload filtering -n,--runName <NAME> tags <tags expression> Tags expression for Test run namescenarios filtering -o,--outputFolder <FOLDER PATH> Features output folder -p,--proxyPassword <PASSWORD> Proxy password -q,--jql <JQL> JQL filter for features download and Jira issues to be updated with test results -r,--report Upload report -s,--secretKey <ASSERTTHAT_SECRET_KEY> Secret key -k,--type <cucumber|karate> Report type -t,--jsonReportIncludePattern <PATTERN> Pattern for json file names -u,--proxyUsername <USERNAME> Proxy username -x,--proxyURI <URI> Proxy URI -l,--jiraServerUrl <URI> Jira Server URL |
...
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.
cmd
| Code Block | ||
|---|---|---|
| ||
java -jar assertthat-bdd-standalone-1.9.411.jar Required options: aaccessKey, ssecretKey, itoken, [-f Download featuresprojectId, [-rreport Upload report] usage: assertthat-bdd-standalone-1.9.4.jar -a,--accessKey <ASSERTTHAT_ACCESS_KEY> Access key -f,--featuressecretKey <ASSERTTHAT_SECRET_KEY> Secret key -token <ASSERTTHAT_TOKEN> Jira API token (for DataCenter only) as an alternative to Downloadbasic featuresauth -h,--help Display help -i,--projectId <ID> Jira project id -j,--jsonReportFolder <FOLDER PATH> Cucumber json files folder -m,--mode <automated|manual|both> Features to download -b,--tags <tags expression> Tags expression for scenarios filtering -n,--runName <NAME> Test run name -o,--outputFolder <FOLDER PATH> Features output folder -p,--proxyPassword <PASSWORD> Proxy password -q,--jql <JQL> JQL filter for features download and Jira issues to be updated with test results -r,--report Upload report -s,--secretKey <ASSERTTHAT_SECRET_KEY> Secret key -k,--type <cucumber|karate> Report type -t,--jsonReportIncludePattern <PATTERN> Pattern for json file names -u,--proxyUsername <USERNAME> Proxy username -x,--proxyURI <URI> Proxy URI -l,--jiraServerUrl <URI> Jira Server URL |
...