A Testrail reporter for cypress including TestRail API basic library
npm install cypress-testrail-logs-screenshots
Publishes Cypress runs on TestRail.
Adds screenshots generated by cypress and attaches them to failed scenarios in the test-rail.
Also added logs (takes them from logs folder).
To get log in logs folder use e.g. cypress-failed-log (https://github.com/bahmutov/cypress-failed-log).
``shell`
$ npm install cypress-testrail-logs-screenshots --save-dev
Add reporter to your cypress.json:
`json`
...
"reporter": "cypress-testrail-custom",
"reporterOptions": {
"domain": "yourdomain.testrail.com",
"username": "username",
"password": "password",
"projectId": 1
}
Your Cypress tests should include the ID of your TestRail test case. Make sure your test case IDs are distinct from your test titles:
`Javascript
// Good:
it("C123 C124 Can authenticate a valid user", ...
it("Can authenticate a valid user C321", ...
// Bad:
it("C123Can authenticate a valid user", ...
it("Can authenticate a valid userC123", ...
``
domain: _string_ domain name of your TestRail instance (e.g. for a hosted instance _instance.testrail.com_).
username: _string_ email of the user under which the test run will be created.
password: _string_ password or the API key for the aforementioned user.
projectId: _number_ project with which the tests are associated.
To increase security, the TestRail team suggests using an API key instead of a password. You can see how to generate an API key here.
If you maintain your own TestRail instance on your own server, it is recommended to enable HTTPS for your TestRail installation.
For TestRail hosted accounts maintained by Gurock, all accounts will automatically use HTTPS.
You can read the whole TestRail documentation here.
Kate Yurasova - github
This project is licensed under the MIT license.
* Pierre Awaragi, owner of the mocha-testrail-reporter repository that was forked.
* Valerie Thoma and Aileen Santos for proofreading the README.md file and making it more understandable.