Managing Your Testing Life Cycle
In this section, you will get to know how you can leverage Provar Manager to structure your testing activities and record any relevant piece of information.
Software development teams often use Application Lifecycle Management (ALM) apps to organise and track their work (e.g. JIRA, Azure DevOps, Micro Focus, etc.). This work usually gets broken down into epics, features, and user stories which your QA team needs to understand in order to consider how to test them properly. Provar Manager currently integrates with JIRA and can integrate with your ALM.
Using Provar Manager, you can record your findings and the outcome of your decisions in the following way:
- Create a Test Project record to start organising the information gathered around a central point.
- Create a Test Plan record under the test project to start documenting the objectives, types of tests to be performed, etc. Depending on the size and complexity of the project, you may choose to create multiple test plans under the same project.
- Create Environment and System records to document the different systems that will be involved in the testing endeavour.
After analysing the requirements, your team will have a better idea of what strategy should be used, who should be involved in the project, how much effort will be required, and what risks have been identified.
The Test Plan record created previously will serve as the hub to organise all this information, either by storing your findings and decision outcomes in the record itself or by using any of the other objects related to it:
- Create related Feature records to define high-level items and rough effort estimates.
- Create related Team Member and Person records to specify roles and responsibilities.
- Create related Risk records to capture any identified risk related to the plan.
- Define which Environment records are considered under the plan.
- Use Activities to schedule milestones.
- Use Files to attach diagrams, documents, etc.
Test Case Design
Once your team knows on a high level what needs to be done and how, Provar Manager can also support you and your team with the design of test cases. You can:
- Create Test Case records with their corresponding Test Steps.
- Attach helpful Files to Test Steps (e.g. screenshots, documentation, etc.)
- Link test cases with related Requirements.
- Attach test data that could be used during the test.
- Create Test Suite records to group and organize test cases.
Tip: The easiest way to include test suites in your test plans is by using the Manage button located on the Test Suites card on the test plan record.
Above: Snapshot of Test Suites card on Test Plan record.
Managing Test Steps
You can easily add, remove, and reorder test steps using the Test Steps Manager found on the test case record page.
Above: Snapshot of the right-hand side of Test Steps Manager.
- The Cancel button cancels any changes not saved.
- The Add Step button adds a new step at the bottom of the list.
- The Save button saves any changes made to the list.
- Hovering between steps reveals a Plus button which, when clicked, adds a new step at the same hierarchical level as the step above it.
- The Up and Down arrow buttons can be used to change the order of the step within the same hierarchical level.
Above: Snapshot of the left-hand side of Test Steps Manager.
- The Bin button deletes the step.
- The Clip button shows/hides the section where you can manage the step’s attachments.
- The Down and Right arrow buttons expand/collapse the step’s child steps.
- The Level Down button creates a child step.
Test Environment Setup
Before starting the execution of test suites within a test plan, it is essential to make sure the test environments are ready.
As briefly mentioned in the Requirement Analysis section, Provar Manager allows you to create Environment and System records.
You can use the Status picklist on the environment record to register its availability.
Salesforce System Setup
Provar Manager allows you to set up connections to Salesforce orgs in order to run Apex unit tests present in them and bring the results back into Provar Manager.
Follow these steps to set up a connection to Salesforce:
- Open the System record of System Type equal to “Salesforce”.
- On the right-hand side of the page, you will find the Salesforce Connection Assistant card.
- Select the right Org Type and click Request Authorization.
- Follow the instructions on the screen:
- Open the link, enter the user code, and click Connect.
- Log into the Salesforce org and click Allow.
- Then click Continue.
- Open the link, enter the user code, and click Connect.
- Once you have authorized Provar Manager to access the Salesforce org, the Salesforce Connection Assistant will automatically refresh to indicate that the connection has been established.
- Follow the final steps shown in the assistant to add the Remote Site Setting which will allow Provar Manager to communicate with the other Salesforce org.
API System Setup
With Provar Manager you can define a System record of type API to represent an external API which you may want to call at some point (see Scheduling Tests > Generic API Settings).
When setting up this type of System, it’s essential to specify the following:
- API Endpoint
- Authentication Type
- No Authentication
- Basic Authentication, which requires the fields Username and Password to be filled.
- Named Credential (recommended), which requires the field Named Credential to be filled with the name of a Salesforce Named Credential.
Named Credentials allow you to authenticate using Username/Password, OAuth 2.0, JWT, JWT Token Exchange, and AWS Signature Version 4.
Salesforce documentation on how to define a Named Credential.
- API Paths
Note: remember to add the API Endpoint URL to the Salesforce Remote Site Settings (more info) if you’re not using the Named Credential authentication type.
- Provar Automation
- Installing Provar Automation
- Updating Provar Automation
- Using Provar Automation
- 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
- Override Auto-Retry for Test Step
- Managing Test Steps
- Namespace Org Testing
- Provar Automation
- Provar Test Builder
- Refresh and Recompile
- Reintroduction of CLI License Check
- 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
- Generate Test Case
- List Compare
- Page Object Cleaner
- 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 API Testing
- Webservices Testing
- Provar Manager
- Provar Manager Setup and User Guide
- Installing Provar Manager
- Configuring Provar Manager
- How to Use Provar Manager
- Managing Your Testing Life Cycle
- Provar Manager Test Execution
- Test Executions and Defect Management
- Provar Manager Test Coverage
- How to Integrate Provar Manager
- Setting Up a Connection to Provar Manager
- Object Mapping Between Automation and Manager
- How to Upload Test Plans, Test Plan Folders, Test Plan Instances, and Test Cases
- Provar Manager Filters
- Uploading Callable Test Cases in Provar Manager
- Uploading Test Steps in Provar Manager
- How to Know if a File in Automation is Linked in Test Manager
- Test Execution Reporting
- Provar Manager Plugins
- Uploading Existing Manual Test Cases to Provar Manager with DataLoader.Io
- Provar Grid
- Introduction to Test Scheduling
- Apache Ant
- Configuration for Sending Emails via the Automation Command Line Interface
- Continuous Integration
- AutoRABIT Salesforce DevOps in Provar Test
- Azure DevOps
- Running a Provar CI Task in Azure DevOps Pipelines
- Configuring the Automation 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
- Gearset DevOps CI/CD
- GitHub Actions
- Integrating GitHub Actions CI to Run Automation CI Task
- 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 Continuous Integration
- Travis CI
- Execution Environment Security Configuration
- Provar Jenkins Plugin
- Parallel Execution
- Running Provar on Linux
- Salesforce DX
- Team Foundation Server
- Version Control
- Salesforce Testing
- Adding a Salesforce Connection
- Assert Page Error Messages on Add/Edit Product
- Internationalization Support
- List and Table Testing
- Salesforce Console Testing
- Salesforce Lightning Testing
- Salesforce Lightning Web Component (LWC) Locator Support
- Salesforce Release Updates
- Visualforce Testing
- Best Practices
- Configurations and Permissions
- Error Messages
- Licensing, Installation and Firewalls
- Test Builder and Test Cases
- Release Notes