Parallel Execution in GitHub Actions using Test Plan
You can build multiple test plans, run a repeatable collection of tests per each release cycle, and make global changes to the environment settings, such as browser settings, build number, and build server. Additionally, you can get consolidated reports of your results.
You can parallelly execute your test cases using a test plan with GitHub Actions.
Once you have the build.xml exported using a test plan, you can parameterize the test plan in the build.xml file.
In the example below, we have 2 test plans, i.e., Smoke and Regression. We will provide the test plan to be executed in the yml file.
Using a test plan, you can create different jobs to run in GitHub actions. Given below is an example.
# This is a basic workflow to help you get started with Actions name: WF # Controls when the action will run. Triggers the workflow on push or pull request # events but only for the master branch on: workflow_dispatch: # A workflow run is made up of one or more jobs that can run sequentially or in parallel jobs: # This workflow contains a single job called "build" build_Smoke: # The type of runner that the job will run on runs-on: ubuntu-latest # Steps represent a sequence of tasks that will be executed as part of the job steps: # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it - uses: actions/[email protected] - name: Run build env: PLAN: Smoke run: | mkdir $GITHUB_WORKSPACE/ProvarHome curl -O https://download.provartesting.com/latest/Provar_ANT_latest.zip unzip -o Provar_ANT_latest.zip -d ProvarHome rm Provar_ANT_latest.zip sudo apt-get update && sudo apt-get upgrade wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | sudo apt-key add - sudo echo "deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main" >>sudo tee -a /etc/apt/sources.list.d/google-chrome.list sudo apt-get -y install google-chrome-stable sudo add-apt-repository ppa:mozillateam/firefox-next && sudo apt install firefox echo $PROVAR_HOM cd $GITHUB_WORKSPACE/test/AN xvfb-run ant -f build_testPlan.xml - uses: actions/[email protected] with: name: Execution Report1 path:${{ github.workspace }}/test/ANT/Results/* - uses: actions/[email protected] if: failure() with: name: Execution Report1 path:${{ github.workspace }}/test/ANT/Results/* build_Regression: # The type of runner that the job will run on runs-on: ubuntu-latest # Steps represent a sequence of tasks that will be executed as part of the job steps: # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it - uses: actions/[email protected] - name: Run build env: PLAN: Regression run: | mkdir $GITHUB_WORKSPACE/ProvarHome curl -O https://download.provartesting.com/latest/Provar_ANT_latest.zip unzip -o Provar_ANT_latest.zip -d ProvarHome rm Provar_ANT_latest.zip sudo apt-get update && sudo apt-get upgrade wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | sudo apt-key add - sudo echo "deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main" >>sudo tee -a /etc/apt/sources.list.d/google-chrome.list sudo apt-get -y install google-chrome-stable sudo add-apt-repository ppa:mozillateam/firefox-next && sudo apt install firefox echo $PROVAR_HOM cd $GITHUB_WORKSPACE/test/AN xvfb-run ant -f build_testPlan.xml - uses: actions/[email protected] with: name: Execution Report2 path:${{ github.workspace }}/test/ANT/Results/* - uses: actions/[email protected] if: failure() with: name: Execution Report2 path:${{ github.workspace }}/test/ANT/Results/*
Documentation library
- 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
- 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
- Provar desktop
- Provar Test Builder
- Refresh and Recompile
- 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 Provar Command Line Interface
- Continuous integration
- AutoRABIT Salesforce DevOps in Provar Test
- Azure DevOps
- Running a Provar CI Task in Azure DevOps Pipelines
- 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
- CircleCI
- Copado
- Docker
- Flosum
- Gearset DevOps CI/CD
- GitHub Actions
- Integrating GitHub Actions CI to Run Provar 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
- 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
- Performance Best Practices
- Testing best practices
- Troubleshooting
- Browsers
- Configurations and permissions
- Connections
- DevOps
- Error messages
- Administrator has blocked access to client
- JavascriptException: Javascript error
- macOS Big Sur Upgrade
- Resolving failed to create ChromeDriver error
- Resolving Jenkins license missing error
- Resolving metadata timeout errors
- Test execution fails – Firefox not installed
- Update to Opportunity field validation behaviour
- Licensing, installation and firewalls
- Memory
- Test Builder and test cases
- Release notes
Trying to raise a case with Customer Success?
Other available resources
Looking for something different?
Keep your finger on the pulse with our latest blog posts
Do a Salesforce deep-dive with our webinars
Get inspired by the latest MVP & Trailblazer stories
Read the latest Provar company updates