Integrating with Jira (via REST API)
During test case executions, it is very useful if the results are updated to a project management tool like Jira. Jira integration is primarily used to raise a bug if any of the test cases fails while executing in Provar. This automation removes manual tasks as much as possible.
In short, Provar’s integration with Jira allows you to capture and track the results of Provar test cases easily and to submit the incident tickets directly in Jira. Provar integrates with Jira using the Jira REST endpoints. This is done by using the web services available in Provar.
Steps for integrating Jira (via REST API) in Provar
Step 1: Add a Jira connection.
Select Generic Web Service from the Connection Type drop-down menu to add a Jira connection.
Above: Adding a Jira connection in Provar.
Step 2: Add an authentication.
In the URL field, enter the Jira base URL. Select Authentication Type from the drop-down menu.
Above: Adding the authentication.
Step 3: Test the connection.
Click Test Connection to check if the connection is successful.
Above: View of the Test Connection dialog box.
Step 4: Use the Jira connection in your test case.
To use the Jira connection in your test case, use Web Connect and Web Request (REST) test step types from the Test Palette.
Above: Using a Jira connection in the test case.
Step 5: Pass the Jira connection in the Web Connect step.
Above: Pass the Jira connection.
Step 6: Configure the Web Request (REST) test step.
In this example, we are creating a ticket in Jira when a Provar test case fails during execution. Please refer to the Atlassian documentation for more information.
Above: Configuring a Web Request.
If the integration is successful, the following screenshot provides an example of a Jira response in Provar.
Above: An example of a Jira response in Provar.
Note: You can make use of a Jira plugin in Provar to monitor, add and update Jira from Provar. For more information about using a Jira plugin, please refer to Jira Plugin in Provar.
- General information
- Licensing Provar
- Provar trial guide and extensions
- Using Provar
- API testing
- Behavior-driven development
- Creating and importing projects
- Creating test cases
- Custom table mapping
- Debugging tests
- Defining a namespace prefix on a connection
- Defining proxy settings
- Environment management
- Exporting test cases into a PDF
- Exporting test projects
- Managing test steps
- Namespace org testing
- Provar desktop
- Provar Test Builder
- Refresh and Recompile
- Reload Org Cache
- Running tests
- Searching Provar with find usages
- Secrets management and encryption
- Setup and teardown test cases
- Tags and Service Level Agreements (SLAs)
- Test cycles
- Test plans
- Testing browser options
- Tooltip testing
- Using the Test Palette
- Test Palette introduction
- Control test steps
- List compare
- Read test step
- String test steps
- UI Test Steps
- Using custom APIs
- Callable tests
- Data-driven testing
- Page objects
- Block locator strategies
- Introduction to XPaths
- Creating an XPath
- Label locator strategies
- Maintaining page objects
- Mapping non-Salesforce fields
- Page object operations
- Refresh and reselect field locators in Test Builder
- Using Java method annotations for custom objects
- Applications testing
- Database testing
- Document testing
- Email testing
- Mobile testing
- OrchestraCMS Testing
- Salesforce CPQ testing
- ServiceMax testing
- Skuid testing
- Vlocity testing
- Webservices testing
- Introduction to test scheduling
- Apache Ant
- Configuration for sending emails via the Provar Command Line Interface (CLI)
- Continuous integration
- Azure DevOps
- Running a Provar CI task in Azure DevOps
- Configuring the Provar secrets password in Microsoft Azure Pipelines
- Parallel execution in Microsoft Azure Pipelines using multiple build.xml files
- Parallel execution in Microsoft Azure Pipelines using targets
- Parallel execution in Microsoft Azure Pipelines using Test Plans
- Bitbucket Pipelines
- Circle CI
- GitHub Actions
- Running a Provar CI task in GitHub Actions
- Remote Trigger in GitHub Actions
- Parameterization using Environment Variables in GitHub Actions
- Parallel Execution in GitHub Actions using multiple build.xml files
- Parallel Execution in GitHub Actions using Targets
- Parallel Execution in GitHub Actions using Test Plan
- Parallel Execution in GitHub Actions using Job Matrix
- GitLab CI
- Travis CI
- Parallel Execution
- Running Provar on Linux
- Salesforce DX
- Team foundation server
- Version control
- Zephyr Cloud and Server
- Salesforce testing
- Adding a Salesforce connection
- Assert Page Error Messages on Add/Edit Product
- Dynamic Forms
- Internationalization support
- List and table testing
- Salesforce Release Updates
- Salesforce Lightning Testing
- Salesforce Lightning Web Component (LWC) locator support
- Salesforce console testing
- Visualforce Testing
- Testing best practices
- Configurations and permissions
- Error messages
- Licensing, installation and firewalls
- Test Builder and test cases
- Release notes