Quality Assurance and Project Management

Jul 20 2009   10:00AM GMT

Responsibility of a tester – a different perspective



Posted by: Jaideep Khanduja
Tags:
bugs report
code writing
coding
customer requirement
developer
Development
development team
product quality
project management
QC
quality
quality control
software product
Software Project
software quality
test case
test report
tester
testing report

The responsibility of a tester is to ensure the peace of mind of the end users who are going to use the software product. Another target should be to safeguard customer’s investment in the product. In order to discharge this responsibility, the tester should focus all his skills on understanding customer requirements and measures to map it with product built by writing appropriately comprehensive test cases, performing test and preparing a detailed self-explanatory test report. Complex business requirements will require extraordinary level of understanding. Keep in mind the budget and time constraint for performing testing without compromising with the coverage or quality.

The overall impact of testing should be clearly visible on the product built. The bugs reported should bring a sense of belonging with the developers and customer users. Clarity of bugs in testing report should not only help developer to fix defects properly but guide him not to repeat the same type of issues in future releases. This may happen slowly but gradually should help in increasing developer’s performance and quality of code writing. After all the development team should start taking testers as their best friends and well wishers instead of someone who is trying to find out the weakness in code writing.

3  Comments on this Post

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when other members comment.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Sellib
    The role you see the tester playing here, sounds a lot like a business analyst role. How do you differentiate those two roles?
    0 pointsBadges:
    report
  • jaideep
    In a way yes. But let us look at their roles. A business analyst is not a tester. What he does is primarily for the sake of understanding business requirements which need to be translated into the software. A tester if does not do this – will not be justifying his role. In my opinion.
    30 pointsBadges:
    report
  • jaideep
    And moreover business analyst grabs requirements directly from customer whereas rest all understand the business process, rules and requirements either from the analyst or the requirements document that the business analyst has prepared.
    30 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to: