Flosum Architecture overview

Above: This diagram provides a high-level overview of how each architecture layer is configured.
Application layer
The application layer consists of two major elements:
- A workstation running on macOS or Windows with a full Automation installation. We recommend that you always use the latest version of Automation, especially when running your test cases via continuous integration and continuous delivery (CI/CD).
- A version control system (VCS) setup to contain your Provar test project(s). This can be Git, Subversion(SVN), Team Foundation Server(TFS), etc.
Note: To learn more about integrating Automation with your version control system of choice, please refer to Version Control and Devops.
Once you have made your initial check-in to your VCS, the next phase is implementing the environment layer.
Environment layer
The environment layer consists of two major elements:
- A full package installation of Flosum in your Salesforce org.
- A Jenkins server accessible from the internet.
Note: The installation of Flosum will not be covered in this guide and must be managed/supported by your Flosum representative/consultant.
Once you have this package installed and correct access has been provisioned, you must also setup your Jenkins server to be publicly accessible from the internet. That configuration will be covered in a later section.
Platform layer
The platform layer consists of two major elements:
- Your Salesforce org.
- Amazon Elastic Compute Cloud (EC2) instance or Azure Virtual Machine (VM).
-
- This guide will be configuring the integration using an Amazon EC2 instance.
- Setup for the Azure VM would be similar. More documentation can be found here.
- These instances should have at least 8 GB RAM, 50 GB of storage space, and a high-speed internet connection.
- If you use something other than an AWS EC2 instance or an Azure VM, then just ensure that your server can be accessed from your Salesforce Org. This generally means opening up your server to outside access on all Salesforce IP ranges (which are A LOT).
Note: In both cases we recommend that you use a Linux distribution as your base since these are generally more secure and have a better performance.
- 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