Flosum Integration Introduction
This support article will guide you through setting up your Flosum Pipeline integration to integrate with a Jenkins Server. Although Jenkins is recommended and will be used in this guide, you can replace Jenkins with any other CI/CD tool that supports external webhook triggers on jobs where Provar can be executed.
In summary, the integration will include a pipeline in Flosum that executes a webhook callout to a Jenkins server job that runs a suite of Provar tests.
Prerequisites in Flosum Integration
A valid Flosum license.
- A Salesforce org with the Flosum managed package installed. The user that initializes the integration with Flosum will need to be added as a licensed user to the installed Flosum package. (Flosum Support can assist with this step).
Note: The setup of Flosum Integration for your Salesforce org is beyond the scope of this guide.
- A Provar project with at least one test case.
- An (optional) version control system (VCS) is already set up. This is optional. However, we will be integrating with a VCS in this guide.
- Jenkins Server that can be accessed from your Salesforce org.
Other Support Articles for Reference
To learn more, refer to the Amazon Web Service (AWS) & Jenkins Configuration and Running Provar tests on Jenkins support articles, including information about the suggested AWS and Jenkins configuration instructions.
- General Information
- About Provar
- Browser and driver recommendations
- Granting org permissions to Provar
- Installing Provar Automation
- Provar Success Portal
- Recent support article improvements
- Reintroduction of CLI license Check
- System requirements
- Updating Provar Automation
- Using hash functions to verify the security of Provar files
- 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
- NitroX
- 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
- Connection Best Practices
- 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
- Provar AArch64 Mac Installer
- Release notes