A Testrail reporter for webdriver.io including TestRail API basic library (fork from mocha-testrail-reporter)
npm install wdio-testrail-reporter#Testrail Reporter for Webdriver.io
Pushes test results into Testrail system.
Fork from mocha testrail reporter
``shell`
$ npm install wdio-testrail-reporter --save-dev
Add reporter to wdio.conf.js:
`Javascript
let WdioTestRailReporter = require('./packages/wdio-testrail-reporter/lib/wdio-testrail-reporter');
...
reporters: ['spec', WdioTestRailReporter],
testRailsOptions: {
domain: "yourdomain.testrail.net",
username: "username",
password: "password",
projectId: 1,
suiteId: 1,
runName: "My test run"
}
`
Mark your mocha test names with ID of Testrail test cases. Ensure that your case ids are well distinct from test descriptions.
`Javascript`
it("C123 C124 Authenticate with invalid user", . . .
it("Authenticate a valid user C321", . . .
Only passed or failed tests will be published. Skipped or pending tests will not be published resulting in a "Pending" status in testrail test run.
domain: string domain name of your Testrail instance (e.g. for a hosted instance instance.testrail.net)
username: string user under which the test run will be created (e.g. jenkins or ci)
password: string password or API token for user
projectId: number projet number with which the tests are associated
suiteId: number suite number with which the tests are associated
assignedToId: number (optional) user id which will be assigned failed tests
shell
node scripts/generate-cases.js {path_to_your_wdio.conf} {path_o_your_mail_test_folders}
`
Example:
You have tests structure:
- node_modules
- test-project
-- wdio.conf.js
-- tests
--- test-group-1
---- test-1.js
--- test-group-2
---- test-sub-group-1
----- test-2.js
----- test-3.js
---- test-sub-groop-2
----- test-4.js
Command:
shell
node node_modules/wdio-testrail-reporter/scripts/generate-cases.js test-project/wdio.conf.js test-project/tests
``also test files (test-1.js - test-4.js) will be updated: id of case will be added to it() function