0
votes

We don't have a virtual environment in my workplace, I work for a very small company.

All they have here is TFS 2012, not 2015 or 2017. Though we do have Visual Studio 2015 Enterprise for the developer computers.

I am wondering if TFS 2012 has the neccessary features to run automated tests aftr builds on a physical PC rather than a virtual?

I don't see any options in the build definitions here to select a test target PC. I don't want to use the build agent as the test agent as that is a pointless test (visual studio's installed on the build server).

How on earth can I use TFS 2012 to run automated tests on a different agent than the build agent?

1
You really should upgrade your TFS to 2017 and explore using the cloud for machenes, Azure and AWS provide good features...MrHinsh - Martin Hinshelwood
I have to convince management to spend the money:user5855178
I have to convince management to spend the money. Our app server would need a hardware upgrade, our database server would need hardware and software upgrade. It's a project in itself. I have asked, but was informed it's out of budget right now.user5855178
1) if it runs 2012 it will run 2017 - so no new hardware requirement. 2) fair that you may need to upgrade windows and/or sql server, however the licensing (depending in your configuration) is covered.MrHinsh - Martin Hinshelwood
Convincing corporate to invest in IT is always a challenge, particularly when the decision-makers are business majors not software engineers. They want security, but they have to manage that within their budget. Performance comes a distant second.user5855178

1 Answers

2
votes

You could install test agents on your target PC and run your tests on test agent using LabDefaultTemplate.

  1. Install Test Controller and Test Agent on the target PC. Configure that controller to register to your TFS collection and make your test agent to connect to your test controller.
  2. In MTM, connect to your team project, add a Lab Enviroment and add that test agent to this Lab Environment.
  3. Create a build definition to build your test project.
  4. Create another build definition choosing LabDefaultTemplate. In this build definition, choosing that Lab Environment you created in Step2. Choosing the build definition you create in Step3. Then trigger this build definition, it will run the tests on your test agent(your target machine).