Well, This post is the first of a series posts of my daily experience I have in work, But before going through the topic it’s important to mention the sophisticated & risky business that we are working on, E-Banking System ; Web application in contact with core banking system. Basically,E-Banking systems are meant to be secure for users data & transactions, and accomplish transactions in highly effective performance.
Testers, Developers, Implementers & Project Managers are always overwhelmed with a high stress of how to meet the delivery dates with an acceptable quality. In my company we have two types of defects; functional defect which is related to the CR we call it Clear Bug & Base Release Bug which was already existing before coding the CR. At the System test phase testers are asked to detect all the escaped clear bugs & the base release bugs.
Based on
What can’t be measured, can’t be improved !
Today the testing team were having a meeting discussing the Performance Evaluation of the quarter, how it’s gonna be run & based on what criteria the tester should be evaluated, since my team is running System Test here’s the standard points: Mangers Evaluation , Team Evaluation & Task Quality.
The Task Quality Evaluation point is the focus of this post which we decided the following :
- Punctuality & Accuracy .
- Speed, with respect to the estimated time.
- The Ratio of the fetched bugs compared to those detected by the customer.
During my search about how to evaluate a tester, I found some interesting articles:
According to 10th International Software Metrices S mposium, Metrics 2004 paper ; the tester should be evaluated up the reported bugs too; in terms of to what extent the reported bugs were crystal clear for the developers & the testers too, is it to the point with no redundancy nor even any missing steps, also does the description include statements about why this bug would be important to the customer or to someone else? Should it? If it does, are the statements credible?. I guess the last point is very important as it will move us to the second article.
According to World Class Software Testing Organizational Proposal
The Tester should has a Management supporting skill, I find it totally rational since after e.g 5 years of experience the Test Manager will be asked to take a fatal decisions so he/she should get us to the Management & higher decision making as early as much as possible.
Finally the last but not the least referring to Evaluating a Tester’s Effectiveness:
Expectations and assignments differ, depending on the task at hand and the type of tester (i.e., subject matter expert, technical expert, or automator), tester’s experience (i.e., beginner vs. advanced), and the phase of the lifecycle in which the evaluation is taking place (requirements phase vs. system testing). For example, during the requirements phase the tester can be evaluated based on defect-prevention efforts, such as discovery of testability issues or requirement inconsistencies. Evaluate a tester’s understanding of the various testing techniques available and knowledge of which technique is the most effective for the task at hand.
I think it’s really hard to evaluate somebody’s work whose work is to evaluate others’ work, so don’t expect that testers will be easy going with their evaluation report without doubting about it & figure out some bugs :) !
