🚨 Shai-Hulud Strikes Again:834 Packages Compromised.Technical Analysis →
Socket
Book a DemoInstallSign in
Socket

@madlan145/wdio-5-testrail-reporter

Package Overview
Dependencies
Maintainers
32
Versions
1
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@madlan145/wdio-5-testrail-reporter

A WebdriverIO plugin to report testrail service

latest
Source
npmnpm
Version
0.0.3
Version published
Maintainers
32
Created
Source

#Testrail Reporter adaptation for Webdriver.io 5

Pushes test results into Testrail system. Fork from mocha testrail reporter

Installation

$ npm install wdio-5-testrail-reporter --save-dev

Usage

Ensure that your testrail installation API is enabled and generate your API keys. See http://docs.gurock.com/

Add reporter to wdio.conf.js:

let WdioTestRailReporter = require('wdio-5-testrail-reporter');

...

    reporters: [[WdioTestRailReporter, {
      domain: "yourdomain.testrail.net",
      username: "username",
      password: "password",
      projectId: 1,
      suiteId: 1,
      runName: "My test run"
    }]]

Mark your mocha suite names with ID of Testrail test suites. Ensure that your suite ids are well distinct from descriptions.

describe("S23 S24 Authenticate with invalid user", . . .
describe("Authenticate a valid user S21", . . .

Mark your mocha test names with ID of Testrail test cases. Ensure that your case ids are well distinct from test descriptions.

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.

Options

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

Automatic creation of sections and cases

You can use next command to generate sections/cases based on your tests in test real:

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:

node node_modules/wdio-5-testrail-reporter/scripts/generate-cases.js test-project/wdio.conf.js test-project/tests

will create in test rail:

  • section 'test-group-1'
  • cases that are described in test-1.js inside section 'test-group-1'
  • section 'test-group-2'
  • subsection 'test-sub-group-1' inside section 'test-group-2'
  • cases that are described in test-2.js inside subsection 'test-sub-group-1
  • cases that are described in test-3.js inside subsection 'test-sub-group-1
  • subsection 'test-sub-group-2' inside section 'test-group-2'
  • cases that are described in test-4.js inside subsection 'test-sub-group-2

also test files (test-1.js - test-4.js) will be updated: id of case will be added to it() function

References

Keywords

webdriver

FAQs

Package last updated on 15 Apr 2019

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts