Creating and importing projects
The Test Project collects all your test-related data, including test cases and Connections.
You must have a Test Project set up before creating or running any test cases in Automation. To do this, you can either create a new test project or import an existing test project. Refer to the sections below for more information.
Creating a new test project
The workspace welcome screen will appear when you open Automation for the first time.
On the welcome screen, if you wish to create a new Test Project, choose Create a New Test Project, and you will be presented with the screen below.
Click Next to continue, supply a name for your Test Project, and click Next again.
If you wish to choose a location for your project that is not within the workspace, uncheck the Use Default Location checkbox and specify your location. Leaving this ticked is recommended.
To create one or more Connections immediately, you can tick checkboxes Create a Salesforce connection, Create a Database connection, and Create a Messaging connection. To create these later, leave these options unticked.
Finally, click Next to create your new test project.
Importing a Test Project
You do not need to create a new test project if you have been provided with a ready-made test project. Instead, you can import your test project as follows:
From the welcome screen, select Import from File.
You will be presented with the screen below:
Select root directory if you have an unzipped project folder, or Select archive file if you have a zipped file. Enter your project location, then click the Finish button. Provar will automatically create the project and add its connections.
Next, Automation will start downloading the metadata for any Salesforce connections and validate the Test Cases against this downloaded metadata. It is recommended to let these operations complete before use.
- 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