Commit a Local Test Project to Source Control
Last Modified:
To link a local Test Project to Git, you must first have created a Test Project in Automation.
You can read more about starting a local Test Project by creating a new project or importing a test project file for more information on how to do this.
If you are starting from a local repository or remote repository with a project already in source control, please follow those instructions.
Note: Repository markers must match in order for them to be in sync. Be careful to choose the right option to avoid conflicts.
Once you have a Project ready to be linked, right-click on the Project Name in the Navigator, then select Team > Share Project.
The Share Project screen will display, prompting the creation of a local repository.
Selecting the top checkbox labeled “Use of create repository in parent folder of project” will place the .git folder in the test project folder and is not recommended. Leaving it unchecked will prompt you for a location.
Note: The .git folder holds all the information necessary for version control and is hidden by default.
Click the Create… Button to create a new repository location on your local machine.
In the new window, click the Browse… button to search for a location for your repository. Chose a default branch name and click Finish to close the Create a Git Repository window.
Click Finish to continue.
Check the project(s) to be included in your repository to enable the Finish button and click to close to complete the creation of the local repository.
The next step is filling that new repository with your files. Right click on the top level of the test project in the navigator again and select Team -> Commit.
The Git Staging window will open in the bottom right corner by default. You can use the icon in the corner to expand this window to fill the screen or resize the window as necessary.
All files that have been changed since the last commit will appear in the top box labeled Unstaged Changes. Changes must be staged before they can be committed.
Note: Staging allows changes made for different reasons to be split into different commits.
Select one or more files and click the single plus sign (➕) to stage selected files. To stage all unstaged files at once, use the stacked plus signs.
Add a clear and concise commit message that describes the changes made and Commit and Push.
After committing and pushing, there will be a prompt for the Destination Git Repository.
Pasting in the URI will fill in the host, repository path, and protocol.
- If you are using HTTPS you will need a Personal Access Token instead of your password.
- If you’re using SSH, you’ll need an SSH key.
Store in the secret store to prevent the need to reenter on each commit/push/pull/sync/etc.
NOTE: When creating GitHub Repository it must NOT be initialized or merging will not work. For Repositories with anything in them, you must pull down from the repo first before creating your test projects or merge files manually to continue!
Click the Preview > button to continue.
Verify the settings and make any changes based on your branching process. Check the box for “Configure upstream for push and pull”. Click the Preview > button to continue.
Confirm your settings are as expected for the push and when ready click the Push button to proceed.
The confirmation box can be closed by hitting the Close button in the bottom right corner.
If you maximized the Git staging window, minimize it back to the corner to continue working.
- Provar Automation
- System Requirements
- Browser and Driver Recommendations
- Installing Provar Automation
- Updating Provar Automation
- Licensing Provar
- Granting Org Permissions to Provar Automation
- Optimizing Org and Connection Metadata Processing in Provar
- Using Provar Automation
- Provar Automation
- Creating a New Test Project
- Import Test Project from a File
- Import Test Project from a Remote Repository
- Import Test Project from Local Repository
- Commit a Local Test Project to Source Control
- API Testing
- Behavior-Driven Development
- Consolidating Multiple Test Execution Reports
- 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
- Japanese Language Support
- Override Auto-Retry for Test Step
- Mapping and Executing the Lightning Article Editor in Provar
- Managing Test Steps
- Namespace Org Testing
- NitroX
- Provar Test Builder
- ProvarDX
- 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 Data Generation
- 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
- Provar Manager
- How to Use Provar Manager
- Provar Manager Setup
- Provar Manager Integrations
- Release Management
- Test Management
- Test Operations
- Provar Manager and Provar Automation
- Setting Up a Connection to Provar Manager
- Object Mapping Between Automation and Manager
- How to Upload Test Plans, Test Plan Folders, Test Plan Instances, and Test Cases
- Provar Manager Filters
- Uploading Callable Test Cases in Provar Manager
- Uploading Test Steps in Provar Manager
- How to Know if a File in Automation is Linked in Test Manager
- Test Execution Reporting
- Metadata Coverage with Manager
- Provar Grid
- DevOps
- Introduction to Provar 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
- 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
- Version Control
- Salesforce Testing
- Recommended Practices
- Salesforce Connection Best Practices
- Improve Your Metadata Performance
- Java 21 Upgrade
- Testing Best Practices
- Automation Planning
- Supported Testing Phases
- Provar Naming Standards
- Test Case Design
- Create records via API
- Avoid using static values
- Abort Unused Test Sessions/Runs
- Avoid Metadata performance issues
- Increase auto-retry waits for steps using a global variable
- Create different page objects for different pages
- The Best Ways to Change Callable Test Case Locations
- Working with the .testProject file and .secrets file
- Best practices for the .provarCaches folder
- Best practices for .pageObject files
- Troubleshooting
- How to Use Keytool Command for Importing Certificates
- Installing Provar After Upgrading to macOS Catalina
- Browsers
- Configurations and Permissions
- Connections
- DevOps
- Error Messages
- Provar Manager 3.0 Install Error Resolution
- Provar Manager Test Case Upload Resolution
- 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
- Selenium 4 Upgrade
- Licensing, Installation and Firewalls
- Memory
- Test Builder and Test Cases
- Release Notes