I’m going to dedicate a couple of posts to the relationships between QA and Development (DEV) organizations. Anyone who’s ever been in either of those organizations knows that sometimes there seems to be a conflict of interest between QA and DEV, which can lead to friction between the groups and the people. Obviously when both …
As I previously hinted in “Building a test case management solution”, I’m personally of the opinion that the holy grail in test case management is in finding the way to manage tests via an issue tracker database. In the time since that post I didn’t find much information about this, and didn’t see tools taking …
Pattern: TrackingIssuesForMultipleReleasesContext: Multiple versions are being actively developed/maintained. New issues are discovered on one version, and their status and progress needs to be tracked on multiple versions, with minimal overhead but maximal accuracy.Active versions – active branches where a build was already issued and documented, and new builds are planned.Problem: When a new issue is discovered, need to …
Following up on my “patterns for issue tracking” post, here is Deeper documentation of some of the Process Flow patterns. I will try to follow up from time to time with documentation of the patterns. Once the knowledge base is more or less complete I will probably consolidate it into an article/whitepaper/wiki format. Pattern: Configuration …
As I mentioned earlier, before we were able to finalize our new development environment we were gobbled up (acquired) by another company, about 4 times the size of our group. In the area of issue tracking, the bigger company was using TestDirector, with some customizations, but actually their processes were quite simplistic, and weren’t enabling …
At some point we understood we must have a robust test automation harness which can at least cover our smoke test and regression. This will help us feel more confident in our releases in less time, and allow meeting the business needs. As we are an appliance based file-system product, in essence an IT infrastructure …
About 8 months ago we chose TD (TestDirector) for Test Case Management as we needed to employ something fast and the Director of QA I brought in had experience with it, while the open source tools we looked at didn’t convince us at that point, and seemed a risk we didn’t want to take, considering …
Sometime before the acquisition, we decided on JIRA as the issue tracker and started evaluating it, including history migration, a bit of customization, and trying to understand what processes need to be in place in order to be effective and deal with the complexities we were seeing regarding real world software development and maintenance.This was …
Long time no post. I’ll try to recap where I stand regarding the issues I started talking about a year ago, at least for a bit of closure regarding the issue tracking and test case management areas.Lets see if I can keep it up this time… In any case, my company was gobbled up by …
I’ve recently been looking at how to build a reasonable test case management solution (good!=word documents) for our company. I quickly learned this is not a very developed field. Mercury TestDirector seems to dominate the commercial field, with the other QA product companies (CompuWare, IBM-Rational) following suite, but not there yet. Test Case Management as …