locked
Is it possible to let one server run both build controller and test controller? RRS feed

  • Question

  • At the moment, I am doing my thesis on some work that requires me to set up a test environment for continuous integration on company servers. At the moment, the company does not run any test on a separate servers, they hardly test at all (:S) but they use a server that has a build controller to manage their daily builds and deploys. Before my thesis work, I had little to none experience with TFS, thus a few questions have come up.

    I have access to a server where I can install a TFS test controller, but I'm starting to wonder if it's better to use this server to run test agents on, and if it in that case is possible to configure a test controller on the same server that holds the TFS build server?

    Let's say we have servers A, B, C.

    A = Build server with one build agent.

    B = Server where a project is deployed (SharePoint server).

    C = The server I have access to.

    When someone wants to deploy their site, server A builds it and deploys to B. I want to include in my build definition an additional step where server C runs UI test on the site on server B. This shouldn't be that hard as I have understood.

    So my questions are

    1. Is it possible to have both build controller and test controller on the same machine, or should they be split up? Are there any advantages to the different alternatives?
    2. If I choose to install the test controller on a different server than the build server, can I still run multiple test agents on that very same server?
    3. Must a controller always register to a project collection to be able to be used? I'm asking this for my own "testing" purposes.

    Thanks!



    • Edited by Zyrillium Tuesday, May 6, 2014 7:39 AM
    Tuesday, May 6, 2014 7:23 AM

Answers

    1. Is it possible to have both build controller and test controller on the same machine, or should they be split up? Are there any advantages to the different alternatives?// Reply: Its Ok to have Build Controller and Test Controller on same machine. From Future load perspective even seperate server is also a good choice. Depends on the work load.
    2. If I choose to install the test controller on a different server than the build server, can I still run multiple test agents on that very same server?// Reply:YES
    3. Must a controller always register to a project collection to be able to be used? I'm asking this for my own "testing" purposes.  // Reply: Yes one Controller is created per Collection.
    Tuesday, May 6, 2014 9:15 AM

All replies

    1. Is it possible to have both build controller and test controller on the same machine, or should they be split up? Are there any advantages to the different alternatives?// Reply: Its Ok to have Build Controller and Test Controller on same machine. From Future load perspective even seperate server is also a good choice. Depends on the work load.
    2. If I choose to install the test controller on a different server than the build server, can I still run multiple test agents on that very same server?// Reply:YES
    3. Must a controller always register to a project collection to be able to be used? I'm asking this for my own "testing" purposes.  // Reply: Yes one Controller is created per Collection.
    Tuesday, May 6, 2014 9:15 AM
  • Thank you! This gave me the answer I was looking for! 

    Wednesday, May 7, 2014 8:20 AM