Quality Assurance and Project Management:

bug report


January 31, 2011  10:45 AM

Quality Control Of Bug Report

Posted by: Jaideep Khanduja
bug report, developer, project management, Software Project, tester

A good writer is one who pays equal weightage to proof reading or editing of his work besides being focussed on content quality and writing style. For every new work that a good writer produces, he doesn’t mind spending some more time on it and getting some different opinion on...

March 22, 2010  11:20 AM

Dilemma of a Tester

Posted by: Jaideep Khanduja
Bug, bug report, developer, project management, software development, software testing, tester

A tester’s prime task after testing a product is to describe the bug. The development team while receiving a test report of a product from tester expects a detailed bug report. The report should be presented in such a way that is easily understood by developers. The point of...

October 19, 2009  10:00 AM

How to predict the number of bugs in the next code of a programmer

Posted by: Jaideep Khanduja
Bug, bug report, code, coding, programmer, programming, Project, project management, Software Project, tester, testing

You have a programmer who is writing codes for years that comes to you for testing. The programmer might be coding for a number of projects simultaneously or sequentially. Similar would be the case with you. You would be testing a number of projects simultaneously or one after the other. By now...

October 14, 2009  10:00 AM

20 gems for project managers

Posted by: Jaideep Khanduja
Bug, bug report, coder, coding, developer, Development, programmer, programming, project manager, quality, quality control, software, Software Project, technical knowledge, tester, testing

1. A project manager is always right 2. Quality is seriously maintained by developers while developing software 3. A separate set of people (quality control or testers) is not required to take care of the software produced or developed 4. Testers don’t do any substantial value addition in...

March 6, 2009  9:42 AM

Why software testing effort estimation is important after functional specifications finalization phase?

Posted by: Jaideep Khanduja
bug report, bug-proofing, bugs report, business process, business rule, developer, development team, functional coverage, functional specifications, functional specifications finalization, quality standards, sizing of software testing effort, software development, software testing, software testing effort estimation, test case, test estimation guidelines, Test Plan, test plan guidelines, test report, test result, testcase, tester, testing, testing effort, testing guidelines, testing knowledge, testing plan, testing time-line, testing timeline

If we go by quality standards the sizing of software testing effort has to be done before the tester(s) start writing the test cases for the purpose. The estimate will clearly draw out of the functional specifications signed off between the customer and vendor. Without sizing the Testing manager...


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: