Currently, qTrace provides built-in support to submit defects directly to many defect trackers. The word “built-in” is not only about the fact that integration adapters to defect trackers are included out of the box with qTrace, but also indicates that the whole defect submission workflow can happen exclusively inside qTrace. Not only does this improve [...]
One of the little-known secrets of qTrace is its Tracker API which allows developers to extend qTrace and have its defect reports submitted to a custom defect tracker. It’s worth noticing that while the API documentation refers to these outlets as “defect trackers”, it doesn’t necessarily require that these have to be exactly some defect [...]
This is a question I often hear testers ask. In this post, I will share 2 rules for testers to consider when determining the amount of details their test scripts should have. Rule 1: The level of detail of test scripts depends on the context of the project Some might be disappointed that I call [...]
There is an interesting discussion on LinkedIn about the use of brain-teaser questions in interviewing testers. To those who aren’t members of that group and can’t view the content, here’s the excerpt of the question and my response. Do brain teaser questions in a QA interview tell the interviewer how good a job a QA [...]
In the last two posts, I discussed about how the qTrace team adopts exploratory testing and how that technique/mindset shines in projects where changes and unknowns are inevitable (which is a characteristic that all my projects in the past and probably in the future). This post describes how qTrace improves productivity of exploratory testers. As a [...]
COMPANY
COMMUNITY
