Here is a first round of my favourite resources. As those who read my posts probably noticed already, I’m quite a heavy user of del.icio.us. I won’t go into what it is, am sure those interested can go there or google it to see whether they like it or not.I’m playing around with Google Notebook …
David V. Lorenzo posts favorite interviewing questions of people on his Career Intensity Blog Here is his post about mine… At the risk of hinting the people who I interview in the future, also check out my interviewing tag on del.icio.us for a lot of resources on the matter. Why am I open about this?One …
I intend to post some reference to resources I’m fond of in the area of R&D;, QA, methodology and the like. In the meantime, anyone who’s interested in what I have to say will probably see some value in looking at FogBugz Online Documentation. I was referred there by Zeljko Filipin’s blog which is aggregated …
In another post in the series about QA/DEV protocols, I’ll talk about opening high quality bugs, why its important, what are the forces operating on each side of the trench here, and try to describe an approach that might improve the state of affairs a bit. First – a definition. What is a high quality …
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 …