Test cycles
A Test Cycle is a defined collection of test case executions that are reported on collectively. This feature is helpful for getting a clean report from a test suite execution wherein some test cases may fail in the first few attempts but will pass after minor tweaks.
A Test Cycle can be used:
- To automatically pick up only failed test cases and execute them
- To create a consolidated report against the latest version of a Test Cycle execution in which all test cases have passed
Follow the steps below to configure a Test Cycle.
Adding a new Test Cycle
Locate the Test Cycle tab in the Test Settings view. This tab allows Test Cycles to be added, edited, removed and reported on.
Select the + symbol to add a new Test Cycle.
Enter the Test Cycle Name and the Folder Name in which the reports and test case artifacts should be stored:
Selecting a Test Cycle during execution
In the Menubar, select the Test Cycle you would like to register your test executions against:
Once this is chosen, Provar will export the results of an execution in the Test Cycle Folder.
Note that it will preserve the folder structure of the tests.
Creating ANT task for Test Cycle
From the Navigator view, right-click on any test case and select Run under ANT.
A dialog box will open with Test Cycle tab. Select the Test Cycle that you have created and times it should be rerun:
Click Run to start execution through ANT.
Creating a PDF report
From the Test Cycle tab in Test Settings, select the PDF icon.
Choose the Test Cycle you would like to report against:
Skipped test cases Included in Test Cycle report
Skipped test cases are also displayed in test cycle reports. In earlier versions, test cases were removed from Test cycle PDF and HTML reports if they were skipped due to the failure of an earlier test case (by the Stop Test Run on Error feature). These skipped test cases will now be included in the reports by default.
Note: Disabled test cases are not included and will still not be shown in test cycle reports.
Re-running failed and skipped test cases
Test Cycles also have a Run Type option for running failed and skipped test cases.
This can be selected from the Test Cycle tab:
- 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
- Functions
- 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
- NitroX
- Provar desktop
- Provar Test Builder
- Refresh and Recompile
- Reintroduction of CLI license Check
- Reload Org Cache
- Reporting
- 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
- Using custom APIs
- Callable tests
- Data-driven testing
- Page objects
- Block locator strategies
- Introduction to XPaths
- Creating an XPath
- JavaScript locator support
- Label locator strategies
- Maintaining page objects
- Mapping non-Salesforce fields
- Page object operations
- ProvarX™
- Refresh and reselect field locators in Test Builder
- Using Java method annotations for custom objects
- Applications testing
- DevOps
- 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
- CircleCI
- Copado
- Docker
- Flosum
- 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
- Jenkins
- Execution Environment Security Configuration
- Provar Jenkins Plugin
- Parallel Execution
- Running Provar on Linux
- Reporting
- Salesforce DX
- Git
- Team Foundation Server
- Version control
- Provar Automation trial guide and extensions
- Salesforce Testing
- Provar Manager
- Best Practices
- Troubleshooting
- Release Notes