alm

On how to get the collections from TFS refer here Please refer here for more details. This is one of the best resources on TFS stuff. The collection guid is passed in and the list returns the name of all projects in that particular collection. public IList<string> GetProjectsFormCollection(Guid collectionId) { ICommonStructureService structureService = null; try { TfsTeamProjectCollection teamProjectCollection = _configurationServer.GetTeamProjectCollection(collectionId); teamProjectCollection.Authenticate(); structureService = (ICommonStructureService)teamProjectCollection.GetService(typeof

I have on my project many PBIs and each PBI has tasks with remaining work filled in. I have finished some of my tasks, others are not started and others are in progress. However, the burndown chart is not showing anything. Not sure exactly what I am missing to configure! My iterations are like this: This has to do with the fact that the burn down needs at least 2 days of data to show something. So basically it won't show any data the first day of the sprint but everything works 'surprisingly' on the second day. This is a longer existing issue as can seen for example on https://connect

I am using TFS to execute a nightly build that includes several steps that use the TFS Test Agent . I am running the latest version of TFS/Test Agent(2015 - Update 3) and there are no other builds being run at this time. Often(maybe half the time), when the nightly job is run the step "Visual Studio Test Agent Deployment" fails with the following error: The job has been abandoned because agent Agent-XXX did not renew the lock. Ensure agent is running, not sleeping, and has not lost communication with the service. This is due to the error found in the Test Agent's log file(under _diag): The

To clarify the question : I am looking for established best-practices or a pro/con analysis of known practices by project lifecycle I mean : deploy to pre-integration, integration, QA, preprod and prod environment. For some context: Our project deploys to integration and QA every week, currenlty we create a new release for each integration deployment, but this doesn't feel right. It leads to updating all the poms every week breaking dev level dependencies, forcing every dev to do a refresh of their eclipse configurations. We have large workspaces and eclipse doesn't handle the refreshes so

I am following the guidance here: http://alm-help.saas.hp.com/en/12.50/api_refs/REST_TECH_PREVIEW/Content/General/Session_Management.html I send the following request to alm12.test.com/qcbin/authentication-point/alm-authenticate Headers: Content-Type: application/xml Accept: application/xml Request <?xml version='1.0' encoding='utf-8'?><alm-authentication><user>userxy</user><password>yyy</password></alm-authentication> Which results in the following repsonse (LWSSO_COOKIE_KEY): Content-Length: 0 Date: Mon, 02 May 2016 13:28:00 GMT Set-Cookie: LWSSO_COOKIE_KEY

Currently I am using the below code to close all the browsers except the ALM browser from where I run the test suite from. However When I run the suite from ALM, the below code identifies 2 browsers - ALM browser and the test case browser. It first closes the test case browser and when it executes the iteration for the ALM browser, it says the browser is not identified when it tries to find the name of the browser. I am not sure why it counts it as a browser if it cant identify it later. Any thoughts on how to resolve this? Dim oBrDes Dim oBrObjList Dim objIndex Set oBrDes=Description.Create