Team Foundation Server
Team Foundation Server (commonly abbreviated to TFS) is a Microsoft product that provides source code management (either with Team Foundation Version Control or Git), reporting, requirements management, project management (for both agile software development and waterfall teams), automated builds, lab management, testing and release management capabilities.
Team Foundation Server (TFS) is the on-premise version of the cloud service VSTS. Just like VSTS, TFS provides an integrated set of features that you access through your web browser or a supported IDE, including:
- Git repositories for source control of your code
- Build and release management to support continuous integration and delivery of your apps
- Agile tools to support planning and tracking your work, code defects, and issues using Kanban and Scrum methods
- A variety of tools to test your apps, including manual/exploratory testing, load testing, and continuous testing
- Highly customizable dashboards for sharing progress and trends
To provide support of these feature of TFS we have added plug-in in Provar. We can import/export Project from and to TFS and commit our work to TFS once work is completed.
Enabling the TFS plugin
When using the TFS plugin for the first time, or after updating to a new version of Provar, the plugin must be enabled in your Provar instance.
First ensure you are running Provar as an administrator.
In Windows this is done by right-clicking on provar.exe and selecting Run as administrator:
On a Mac this is done by opening the Terminal, running sudo /Applications/Provar.app/Contents/MacOS/provar then entering the Admin password:
Then go to the toolbar in Provar and click Help > Add/Remove Features:
Tick the checkbox against the TEE plugin:
Then click the Install button.
The following dialog box will appear:
Click OK. The plugin options will become available for use after a restart.
Importing a test project from TFS
To import a Test Project from your TFS Repository, from the Provar welcome screen, click on the link Import from Source Control:
Then choose the option Import from TFS:
You then will be asked to read and accept the TFS license agreement:
Once you have done this, tick the checkbox and click Next.
The following Server Selection screen will appear:
Select Connect to a Team foundation Server or Team Services account then click the Servers button:
Add your server details inthe dialog which appears:
You will be asked to authenticate:
Confirm that the details have been added correctly and then click the Close button:
Then on the Server Selection screen, click Next:
On the next screen, you will be asked to select your project:
Select this and click Next.
On the next screen, select your project and click Next:
Confirm the details on the next screen and click Next again:
Review the confirmation on the next screen and then click Finish:
You will then be prompted to enter your secure storage password. If you have one, enter it and click OK, otherwise click Cancel:
The Project will now be loaded into Provar and visible through Navigator:
You can also access it through the Team Explorer view:
If you do not have the Team Explorer view open already, you can open it and the Builds view by navigating to Show Views > TEE > Team Explorer:
Exporting a test project to TFS
To export your test Project to the TFS Server, navigate to the Team Explorer view (see immediately above for instructions).
Once this is open, select the option Connect to Team Services or a Team Foundation Server:
On Server Selection, select Connect to a Team Foundation Server or Team Services account, then provide the TFS server details:
Then click Next.
On the next screen, select your project. Then click the Finish button:
Once the TFS Server is connected it will appear as follows:
To export your project to the TFS Server, go to the Navigator and right-click on the project:
Select Team > Share Project…
Then select your project and click Next:
Select your project path folder and click Next:
Then review the confirmation and click Finish:
The successfully imported project will be shown with a tick in the Navigator:
Checking in and checking out
You can check in project changes from the Team Explorer view or from the Navigator.
To check in changes from the Team Explorer view, click the Check In button:
Or to check in changes from the Navigator, right-click on the project, then select Team > Check In Pending Changes…
You will be asked to confirm what files you want to check in:
Then add any comments and click the Check In button to confirm.
You can perform many other operations from the Navigator in a similar way, such as Check Out, Get Latest Version and Undo Pending Changes:
Searching and creating work items
From the Team Explorer view, you can also search Work Items or create new ones:
- 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 Automation
- 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
- 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
- Team Foundation Server
- Version Control
- Masking Provar Credentials on CI
- Salesforce Testing
- Best Practices
- Salesforce Connection Best Practices
- Improve Your Metadata Performance
- 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
- 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