If you want to seriously improve your bug reporting skills, read up, or take, the BBST Bug Advocacy course. If you want to start by improving bug report title/subject/summary; read Lessons Learned in Software Testing, no, 83, or this blog post. Many people will only read the title, so it is important to make it […]
While sifting and sorting the ISTQB Glossary 2.1 I finally found a couple of terms which definitions were both correct and useful: 1. deliverable – Any (work) product that must be delivered to someone other than the (work) product’s author. Good, because it puts focus on the fact that you are creating the deliverable so it […]
Download! It is often stated, with right, that you should use many, different information sources in order to come up with good test ideas. Rob Sabourin uses 10 categories, HICCUPPS(F) can be used not only as oracles, and Cem Kaner has many examples in various presentations and tutorials. We decided to make our own list […]
Generic test report: DateTime ID Author Time for writing report Time maintaining scripts for generating report Application Under Test Areas tested For each area: Blockers Testers Tester mood Tests planned Tests executed Tests passed Tests failed Tests remaining (untested+fail) Bugs found, per priority Old bugs status (priority, severity, tester, assignee, days active) Bug resolution aggregation […]
A year has passed since we released version 1.0 of our quality model without metrics. It is time for a new version, with additions and corrections we have learned over the year (and a Swedish translation!) 1.1 English 1.1 Swedish 1.0 English Feedback is always welcome! /Rikard, Henrik, Martin
There are some discussions about current certification schemes, but there is not so much attacks and defense of the actual content. This is from ISTQB Glossary 2.1: black box test design technique: Procedure to derive and/or select test cases based on an analysis of the specification, either functional or non-functional, of a component or system […]
I believe there is too much focus on test coverage , there is even an axiom about the need of it. My reason is that no coverage model captures what is important. Cem Kaner lists 101 possible coverage models (Software Negligence and Testing Coverage), and none of them are super-good to me (my favorite is […]
With all due respect, this is the announcement of the perhaps most powerful public two-page document in the history of software testing. It is an extended re-write of James Bach’s Quality Criteria Categories, and has been developed to 12 categories (CRUCSPIC STMP) and 93 sub-categories for software quality characteristics/attributes/factors/dimensions/properties/criteria/aspects. This list is not objectively true, […]
This is a follow-up on a previous post about Rapid Test Preparation. Some of the commenter’s asked for an example; I’ve tried to go half-way at least. Added some new sections based on some good feedback from Henrik Emilsson. Test Proposal – <area> See the test proposal as a work in progress document to enhance […]
I saw an interesting interview with Rob Sabourin today http://www.youtube.com/watch?v=HZRXdaN7gkY (Thanks for the tip, Jon Bach!) One thing he says in this video is: “… There are a lot of template junkies out there. [Testers are] filling out templates and not actually testing. That frustrates testers…” Hey, isn’t this the same thing that happens in strictly scripted testing […]