Creating a Git repository for Automation Projects
Follow the steps below to create a Repository for your Automation Project. These steps give instructions using Git Desktop, but the same steps could be recreated using Git.
Note: this page assumes you have Git or Git Desktop already installed on your machine. Please ensure this is completed prior to following these steps. If you are new to Git, refer to Salesforce’s Git and Github Basics Trailhead module for help installing Git and performing everyday activities.
Step 1: Launch Github Desktop and click on the + icon.
Step 2: Choose the ‘Create’ option. Enter a Name and Local Path to create the local repository, then click Create Repository:
Step 3: Go to the local path specified above and replace the .gitignore file with this file. Make sure you name the file as .gitignore, removing the *, after downloading it.
The following files should NOT be committed to the repository:
Data | Description | How to recreate |
.metadata and */ProvarANT/* folder | Contains Cached Org Information and Logfiles | Provar will recreate this folder when it does not exist |
bin folder | Contains all compiled Java classes | Provar will re-compile all Java classes contained in the src folder |
*.pdf documents | By default, Provar test reports are added to the project directory; you may not want these added to Version Control | Run the test case again. |
Step 4: Return to Github Desktop and Click the ‘Publish’ button. You may need to provide a Username and Password.
Step 5: Provide a Description and select the repository. Select the Private Repository checkbox if you want to use a private repository. Click Publish at the bottom.
Step 6: Launch Automation and specify your workspace as the local path defined in Step 2. Create a new Project.
Step 7: Go to the Project in Github Desktop. Enter a comment and Commit to Master:
Step 8: Click on Sync:
You can start working on your Automation Project with everything on your GitHub repository. Remember to commit your changes nightly (Steps 7 and 8) to back up your changes.
- 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