{"id":31315,"date":"2017-05-05T12:12:22","date_gmt":"2017-05-05T20:12:22","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/visualstudioalm\/?p=31315"},"modified":"2019-02-14T15:51:46","modified_gmt":"2019-02-14T23:51:46","slug":"using-visual-studio-agent-deployment-task-on-machines-not-connected-to-the-internet","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/devops\/using-visual-studio-agent-deployment-task-on-machines-not-connected-to-the-internet\/","title":{"rendered":"Using ‘Visual Studio Agent Deployment’ task on machines not connected to the internet"},"content":{"rendered":"

‘Run Functional Tests’ (RFT) task is used for running functional tests using remote machines or to run tests in a distributed manner using multiple machines. With TFS 2017 Update 2 and VSTS, You can use “Run Functional Tests” task to run tests using Visual Studio Test Agent 2017.<\/p>\n

The RFT task needs a companion ‘Deploy Test Agent’ task that deploys and configures test agents against your VSTS account or the TFS server. Using the Deploy Test Agent version 2 task, you can now choose which version of Test Agents you want to deploy.<\/p>\n

\"agentversionsetting\"<\/a><\/p>\n

For machines which are connected to the internet, the process is pretty straightforward.<\/p>\n

The required test agent will be downloaded and installed automatically if it’s not present on the machine.<\/p>\n

For machines that are not connected to the internet, the task supports installing test agents from a shared UNC path. For this, you need to make the test agent installer available on a network share.<\/p>\n

If you are installing Test Agent 2015, use the following steps:<\/p>\n

    \n
  1. Download Test Agent 2015 from <\/span>https:\/\/go.microsoft.com\/fwlink\/?LinkId=827840<\/span><\/a><\/li>\n
  2. Copy the test agent to a machine which is accessible by build agent and test agent machines<\/span><\/li>\n
  3. Share the test agent folder using Windows file sharing<\/span><\/li>\n
  4. Use the shared path location in “Visual Studio Test Agent Deployment” task as shown below<\/span><\/li>\n<\/ol>\n

    \"ta2015\"<\/a><\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

    With the Visual Studio 2017 release, the packaging and installation experience has changed. So you need to first create an offline installer using the bootstrapper. The installer also checks for certificates to verify package authenticity, so some extra prep is required before an offline installer can be used by the ‘Visual Studio Test Agent Deployment’ task.<\/p>\n

    To easily create an offline package of Test Agent 2017 in a single step, we have created a Powershell script.<\/p>\n

    If you are using TFS 2017 Update 2, please use the PS script located here<\/a>.<\/p>\n

    If you are using VSTS, please use the PS script located here<\/a><\/p>\n

    Run the PS script providing language and sharedFolder as optional parameters. If these parameters are not provided, Test Agent English (en-us) package will be downloaded to the folder from where the script runs.<\/p>\n

    If you do not want to run the script, you can perform the following steps instead:<\/p>\n

      \n
    1. Download the bootstrapper vs_testagent.exe from: <\/span>https:\/\/aka.ms\/vs\/15\/release\/vs_TestAgent.exe<\/span><\/a><\/li>\n
    2. Run the following command to create an offline cache (the following example assumes ENU language)<\/span><\/li>\n<\/ol>\n

      vs_testagent.exe –layout C:TA2017Setup –lang en-US<\/p>\n

      This downloads the Test agent packages to C:TA2017Setup folder<\/p>\n

      \"tapackage\"<\/a><\/p>\n

      3.\u00a0Now “Archive\/Zip”\u00a0 all the contents of the folder and name it as “TestAgent.zip”.\u00a0Please make sure you retain the directory information while zipping.<\/p>\n

      \"preservedirectory\"<\/a><\/p>\n

      4.\u00a0Share the folder which contains “TestAgent.zip” using Windows file sharing.<\/p>\n

      5. Use the shared path location in “Visual Studio Test Agent Deployment”\u00a0<\/span><\/p>\n

      \"ta2017\"<\/a><\/p>\n

      Notes:<\/p>\n

        \n
      1. For Test agent 2017, make sure the archive retains the folder structure as shown and name it “TestAgent.zip”<\/span><\/li>\n
      2. If you are using Azure machines, the agent will be downloaded from internet and installed automatically. For creating Azure machines, w<\/span>e recommend creating “VM image with Test Agent preinstalled”. If Test Agent is preinstalled, the ‘Deploy Test Agent’ step skips the installation portion and simply configures the agent, and thus runs faster.<\/li>\n<\/ol>\n
          \n
        1. It is also recommended that you install the latest Windows Management Framework<\/a> on test agent machines <\/span><\/li>\n<\/ol>\n
            \n
          1. A prerequisites checklist is available at <\/span>https:\/\/github.com\/Microsoft\/vsts-tasks\/tree\/master\/Tasks\/DeployVisualStudioTestAgent<\/span><\/a><\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"

            ‘Run Functional Tests’ (RFT) task is used for running functional tests using remote machines or to run tests in a distributed manner using multiple machines. With TFS 2017 Update 2 and VSTS, You can use “Run Functional Tests” task to run tests using Visual Studio Test Agent 2017. The RFT task needs a companion ‘Deploy […]<\/p>\n","protected":false},"author":86,"featured_media":45953,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1,252],"tags":[],"class_list":["post-31315","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devops","category-testing"],"acf":[],"blog_post_summary":"

            ‘Run Functional Tests’ (RFT) task is used for running functional tests using remote machines or to run tests in a distributed manner using multiple machines. With TFS 2017 Update 2 and VSTS, You can use “Run Functional Tests” task to run tests using Visual Studio Test Agent 2017. The RFT task needs a companion ‘Deploy […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/31315","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/users\/86"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/comments?post=31315"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/31315\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media\/45953"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media?parent=31315"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/categories?post=31315"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/tags?post=31315"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}