Menu

3 Integration

JIRA Integration with qTest Pulse

To communicate with Jira for resources such as projects, sprints, stories, bugs and tasks and so on, Pulse offers a very friendly feature for users to config the interaction. You have two ways to build an integration with Jira:

  • Clicking on a project name in a team then navigating to [ALM Software] tab
  • Accessing to Activity tab then clicking on Setting icon and selecting "Project Settings" option then navigatitngg to [ALM Software] tab

You need to have a Jira account and this account has administrator role so that it is authorized to access System page to config a webhook on Jira.

The Jira integration page on Pulse has following fields:

  • Jira Project URL: The Jira link that you want to Pulse to connect to such as https://agile.qasymphony.com
  • Jira Project User Username & Password: The credential can be accessed to the provided Jira URL
  • Webhook: This link is automatically generated by Pulse. It is to get changes from Jira and update corresponding resources on Pulse
  • Project: The dropdown contains the list of projects available for the account on Jira. It is automatically filled up right after the account provided to Username and Password field
  • Save button: It is used to save the integration as well as synchronize resources from the selected project in Project dropdown on Jira to the project you are standing on in Pulse

Here are detailed steps to build an integration with Jira:

Step 1: Select Jira option in [ALM Type] field

Step 2: Provide Jira URL as well as your account information to log in to the provided Jira URL

Right after step 1 & 2, projects from Jira will be synchronized to Pulse and shown in Project field

Step 3: Select a project in Project field

If you click Save button after step 3, resources belonging to the selected project will be synced to Pulse. However, whenever a resource gets change, the change will not be updated to the corresponding resource in Pulse. In case of making resources updated paralelly, please proceed step 4 - setting up a webhook

Step 4: Access to Jira at another tab, for example https://qasymphony.atlassian.net, then navigate to Administration -> System -> Webhook and create a new one. Provide Webhook URL field with the one generataed by Pulse

Step 5: Click 'Save" button to save the integration as well as to triger sunchronizing resources from Jira to Pulse

GitHub Integration with qTest Pulse

When qTest Pulse is integrated with GitHub, all of your test cases will be stored and versioned in GitHub. If your CI tool is integrated with GitHub, test run results will be outputted in a test runner output and trigger new builds. Failed test cases will show as automated testing results and be reported in your build report. For configuring GitHub integration:

  • Clicking on a project name in a team then navigating to [Version Control] tab
  • Accessing to Activity tab then clicking on Setting icon and selecting "Project Settings" option then navigating to [Version Control] tab

 

  • Github Host: The Github server URL
  • Github Organization: The working organization of your Github account
  • Github Project User Username/Password: your Github account
  • Git Working Project Name: your working project repository
  • Unit Testing Framework: we have 3 options: mocha, jasmine or junit 4+
  • Project Path for Generated Test Cases: git directory of generated test cases
  • Generated Test Case File Extension: default extension name of generated test cases
  • Generated Test Case Branch: git branch of generated test cases
  • Git Test Case Library Project Name: repository for test cases
  • Project Branch for Test Case Library Templates : git branch of test cases library templates
  • Webhook URL: use as a Github webhook URL for receiving events from Github server

GitHub Integration Setup 

To setup the integration between Pulse and GitHub, open your Project Settings page and select the tab Version Control.

projectSettings.png

vcsconfig.png

 You will need to input into 3 sections as following:

  • Your GitHub Host and credentials
  • Repository for generated Test case files. Pulse will use this information to commit source file into GitHub whenever a test case is executed in Pulse.
  • Repository for Test case Template. Pulse will use this information to commit test case into GitHub whenever it is created in Pulse.

Then, configure Webhook in your GitHub Repository in order for it to push events in your repository back to your Pulse project. Check this article for the detailed explanation.

1. GitHub Host and Credentials.

- Select github from the VCS Type dropdown

- Type in your GitHub Host, Organization, and credentials. They are all required fields in order for Pulse to connect to GitHub.

githubhost_credentials.png

2. Repository for generated Source File

- Git Working Project Name: Your repository

- Unit Testing Framework: Select your testing framework. There are currently 4 supported options: mocha, jasmine, junit 4+, cucumber

- Project Path for Generated Test Cases: Location in your Repository where you want the generated Test Case files stored. You will not need to create this path in GitHub beforehand, the system will automatically create the path if it is not existing.

- Generated Test Case File Extension: Test Case file extension (e.g ".spec.ts" for typescript)

- Generated Test Case Branch: Branch to which generated Test case files will be committed

- Generated Src Template: Input your template for Test case file.

Use the syntax ${testcase.<propertyname>in your template to specify test case's properties.

Example: ${testcase.name} for test case's name, ${testcase.preCondition} for test case's pre-condition.

You can refer to this link for all available Test case properties.

repoforGeneratedTC1.png

3. Repository for Test case Library Template

- Git Test Case Library Project Name: Your repository. It can be the same or different with Repository of Test Case File (in step 2 above)

- Project Path for Test Case Library Templates: Location in your Repository where you want your template stored. You will not need to create this path in GitHub beforehand, the system will automatically create the path if it is not existing.

- File Extension for Test Case Templates: e.g "md" for markdown

- Project Branch for Test Case Library Templates: Branch to which generated Test case Template will be committed.

- Test Case Library Templates: If you don’t put a template, the default is Gauge markdown.

Use the syntax ${testcase.<propertyname>in your template to specify test case's properties.

Example: ${testcase.name} for test case's name, ${testcase.preCondition} for test case's pre-condition.

You can refer to this link for all available Test case properties.

repoforTCLibraryTemplate1.png

After finishing to fill all needed information. Click Save button.

From now, when you create a Test case in your project in Pulse, a test case template will be committed to GitHub. When you execute a Test case, a test case source file will be committed to GitHub.

If you are still not able to configure the integration properly, check here for a real example.

GitHub Configuration - Example

This example tries to demonstrate a typical flow from setting up a CVS configuration in Pulse project to generating and committing test case template/files into GitHub.

1. Set up GitHub Host and Credentials

setup1.png

2. Repository for generated Source File

setup2.png

 3. Repository for Test case Library Template

setup3.png

4. Create Test Case in Pulse

  • In Pulse, create a Test Case named "login successfully"
  • A file name "login successfully.md" has been generated and committed to according repository in GitHub. Its content generated following the format that you setup in the field "Test Case Library Templates" of section 3.

testcase.png

ex1.png

5. Execute the test case

  • In Pulse, execute and fail the test case
  • A test case source file named "login successfully.spec.ts" will be commited to GitHub. Its contents is generated following the format you define in the field "Generated Src Template" of section 2.

execute.png

 ex3.png

 Configure Webhook in GitHub Repository

This article demonstrates how to configure webhook in your GitHub repository in order for Pulse to be notified when certain events happen within your repository.

1. Access Version Control tab from Project Settings page

projectSettings.png

vsconfig.png

 2. Scroll down to the bottom of the page and copy the system-generated URL.

copywebhookurl.png

3. Open Webhooks setting in your Repository in GitHub

webhook1.png

4. Add webhook

  • Paste the copied URL into Payload URL field.
  • Select option "application/json" in Content Type drop down 
  • Select option "Just thepushevent" as events you would like to trigger the webhook
  • Click button Add Webhook

webhook2.png

done.png

 

 

Subscribe To Our Blog
Powered by Zendesk