Testrail

Testrail integration with CodeceptJS is never simple like this. The test run is created automatically after the execution. The screenshots of failed tests are also attached to test results.

Now there is new feature, add the configuration to test run of test plan

Requirement

To use this custom plugin

npm i codeceptjs-testrail --save

Note:

• You should include the test case id to make it works, otherwise, this plugin has no clue which case id to be added to test run on Testrail.
• To avoid creating multiple testruns, add --suites to run-workers command

npx codeceptjs run-workers 3 --suites

An example:

...
  Scenario('Search function is displayed @C12345', ({I, homePage}) => {
    I.seeElement(homePage.searchTextbox);
    I.seeElement(homePage.searchButton);
  });
...

Data driven tests

If you want to have different Data-driven test cases with different IDs in Testrail for each iteration of the test you will need to populate the Data object with your a tag. This works because CodeceptJS extracts tags from test names, and data for Data-driven tests is populated in the test name.

An example:

...
  let accounts = new DataTable(['testRailTag', 'user', 'password']);
  accounts.add(['@C12345', 'davert', '123456']); // add a tag for each user along with their test data
  accounts.add(['@C45678', 'admin', '123456']);
  
  Data(accounts).Scenario('Test Login', ({ I, current }) => {
    I.fillField('Username', current.login); // current is reserved!
    I.fillField('Password', current.password);
    I.click('Sign In');
    I.see('Welcome '+ current.login);
  });
...

A Gherkin example:

  @smoke
  @12345
  Scenario: Search function is displayed
    Given I am on the home page
    Then I see search textbox
    And I see search button

Configuration

Add this plugin to config file:

...
plugins: {
  testrail: {
    require: 'codeceptjs-testrail',
    host: 'https://peternguyentr.testrail.io',
    user: 'username',
    password: 'password or api key',
    suiteId: 1,
    projectId: 1,
    runName: 'Custom run name',
    runId: 123,
    plan: {
      existingPlanId: 484,
      name: 'Custom Plan name',
      description: 'Something about your plan',
    },
    configuration: {
      groupName: 'macos',
      configName: 'leopard'
    },
    enabled: true
  }
}
...

Possible config options:

• suiteId: when your project is not under the single-suite mode, suiteId is needed. When you don't provide the suiteId, the first suiteId will be used as default.
• projectId (Required): The project Id which is from the Testrail. This should be provided to make this plugin works
• runName (Optional): your desired test run name. If you done provide this test run name, default test run name is as This is a new test run on ${dd/mm/yyy H:M} which is current day.
• runId (Optional): provide the existing run Id when you want to update the existing one instead of creating new testrun.
• plan - existingPlanId: if you provide an existing plan ID, the new test run is added to that test plan. Otherwise, new test plan is created and new test run is added to that test plan.
• plan - name: your desired plan name.
• plan - description: your desired description to your test plan.
• configuration: provide the created configuration group name - configuration name that you want to add to the test run. If you don't provide anything or wrong either group name or config name, there will be no configuration added to test run.
• debugLog: show more logs for debugging purposes.