Showing posts from February, 2008

my testing adventures - effectiveness

If you check the date of recent posts , you will see that this is the third post today. My colleague smiles - it is friday, too difficult to work when you know three days of rest are waiting ahead.

Today is a reading day, so the next thing I found in one blog - testing metrics. The authour lists a few of them. the most interesting for me - "Number of customer reported Bug - As a measure of testing effectiveness".

Ok. The effectiveness of testing.... Let's see - my first project here, small and my independent work as a tester. pilot project :)
Total issues registered for the project - 164;Total bugs - 119;Client reported issues - 27;Client bugs - 21;Some of them seem quite 'strange' for me and I simply can not call them "bug", so will leave - 10 bugs with low priority.So, what we have for my testing effectiveness? 10 of 119? Less than 9 percent.What is the 'normal' and accepted rate? Can not find anything on that topic in the web for a moment.

exploratory testing (ET)

wow, this is a new concept for me and to tell the truth, the topic i find very interesting.
exploratory testing (ET) - simultaneous learning, test design and test execution. The tester thinks, learns, improves his test design, learns, thinks, etc. Previously called ad-hoc testing. Have been working on this for a few years :) Search wikipedia for more, or find some James Bach or Jonathan Kohl articles on the topic.


Thinking about sotfware testing process and improvements, so search the web for some info. The best thing is - developing a testing maturity model. Found out, that at the moment, our company works at level 3, Initial, Phase definition and integration. Still left space for growth - 4 (management and measurement) and 5 (optimization, defect prevention and quality control). While, CMM level 2 supports only up to 3 level of TMM, the wish to go further with the TMM may have obstacles. Anyway, it was interesting to read some articles. CMM and TMM are also parallel to five phase model of an individual tester's maturity growth. not much info on that. Tester's growth and carer .

wikipedia about testware

Testware is a sub-set of software with a special purpose, that is, for software testing, especially for software testing automation. In this sense, automation Testware is designed to be executed on automation frameworks.
It includes artifacts produced during the test process required to plan, design, and execute tests, such as documentation, scripts, inputs, expected results, set-up and clear-up procedures, files, databases, environment, and any additional software or utilities used in testing.

Testware is produced by both verification and validation testing methods. Like software, Testware includes codes and binaries as well as test cases, test plan, test report and etc. Testware should be placed under the control of a configuration management system, saved and faithfully maintained.
Compared to general software, testware is special because it has: a different purpose;
different metrics for quality and different users

The different methods should be adopted when you develop testware wit…