September 3, 2013
Uncategorized

Failing tests for minor bugs

Scenario Consider a situation where there is a test case with several steps, and one of the steps fails because a bug is present in the product. However, there is a workaround for the issue, and the decision is made not to fix the bug. The test case in which the bug is encountered, however, …

OpTeam Crosslake

August 27, 2013
Uncategorized

Customizing exploratory testing in MTM

When you create a bug or test case during an exploratory testing session with Microsoft Test Manager, only 10 steps are retained by default. Many of our clients complain that this number is too little. There are two ways to override this limitation — one globally (to the workstation), and one per bug. Global customization …

OpTeam Crosslake

June 25, 2013
Architecture

Documenting the architecture

“There is no documentation in Agile!” Documentation is one of those necessary evils in software development, particularly for teams that use remote development centers and need to rely on written communication more. We periodically hear the excuse, “We are doing Agile — we don’t need no stinkin’ documentation!” This is a misinterpretation of the Agile …

OpTeam Crosslake

June 20, 2013
Org and Process

Effective status reports

Status reporting is often a necessary evil in many corporate environments to keep stakeholders up to date on what is happening with a project. In our travels, we see a lot of weak status reports and generally help clear things up. While one could practically write a book on what makes a good status report, …

OpTeam Crosslake

June 7, 2013
Uncategorized

How to rebuild a TFS Analysis database

Although not a problem we see often, some of our clients run into issues with a corrupt TFS Analysis DB, particularly after an environmental failure of some kind. This doesn’t lead to any permanent damage or data loss but needs to be addressed. Here is a set of instructions we developed for this. Note that …

OpTeam Crosslake