Austin Agile DevOps

DevOps in the Cloud
posts - 70 , comments - 7 , trackbacks - 0

May 2012 Entries

Copying Files into a TFS Workspace: Which Files Changed?
Team Foundation Server 2010 is a “server-side” version control system. Developers use to Subversion and other “client-side” systems are often frustrated in certain situations where they want to see only the changed items in the Pending Changes window and TFS shows all checked-out items. This may happen with source control support files. For example .vspscc, .vssscc file types. It will happen when an entire directory structure is copied to the workspace and only some of the items have changed. The ......

Posted On Tuesday, May 22, 2012 11:58 AM | Comments (0) |

Microsoft Test Manager–Test Cases Not in a Test Plan
Visual Studio and Team Foundation Server (TFS) 2010 provided support for system testing. Test cases were added as a work item type. But test plans and suites are not work items and this greatly limits the visibility into the management of test artifacts. For example, there is no easy way out-of-the-box to find test cases that don’t belong to a test plan. Here’s the SQL that creates a list of test cases providing the test case: ID Title State Assigned To Area Path Iteration Path Plan and Suite Path ......

Posted On Wednesday, May 16, 2012 8:21 AM | Comments (1) |

Passing in report parameters to TFS 2010 OLAP Web Parts on the Team Portal
There is some helpful information from Ewald Hofman on passing in parameters to the TFS SQL Server Analysis Services OLAP reports. But, the 2010 schema has changed. You can use the SQL Server Mgmgt Studio to access the metadata and query the tables to seee the new schema and record values. As an example of the Task Burndown report on the TFS 2010 Project Portal, here's the URL that worked in a browser: http://{your tfs server}/Reports/Pages/Repor... ......

Posted On Tuesday, May 15, 2012 8:48 AM | Comments (2) | Filed Under [ Agile SCM Talk Blog ]

How I Customized Report Parameters for Team Foundation Server 2010
My goal was to have the burndown chart on the team project portal main page display the current iteration. The default report displays the tasks for the entire team project starting 5 days before the current date and ending 25 days after the current date. FRUSTRATING, to say the least! I mean, what a useless report! Who's Agile book did they get that one from? What I wanted was to see the burndown for the current iteration. That is, tasks for that iteration only and that iteration starting on a fixed ......

Posted On Tuesday, May 15, 2012 8:46 AM | Comments (0) | Filed Under [ Agile SCM Talk Blog ]

Using a TFS 2010 custom bug work item definition with the MTLM Test Runner
We don’t use the term “Bug,” rather we use “Software Action Request” or “SAR.” I renamed the Bug WI definition from Bug to SAR. I added a few custom fields to our SAR WI definition, but all the Microsoft fields are used and unchanged. What I want is for the MTLM client to be configured to open a SAR rather than a Bug. In other words, out-of-the-box when a user is manually executing a test case with the MTLM Test Runner client and one of the steps fail, the user clicks a button to create a Bug or ......

Posted On Tuesday, May 15, 2012 8:44 AM | Comments (0) | Filed Under [ Agile SCM Talk Blog ]

Updating an incorrect reason code after a state transition
When using TFS work items you may find that when you transition from one state to another that you selected the wrong reason code, or you found out shortly afterwards that the reason code you selected is incorrect. Well, you may be surprised to find that reason codes (System.Reason) cannot be updated within the same state. After some looking into, I came to understand the intent of reason code is to document the "reason" the state changed. As opposed to indicate within state changes. However, it ......

Posted On Tuesday, May 15, 2012 8:32 AM | Comments (0) | Filed Under [ Agile SCM Talk Blog ]

Powered by: