Home > IT Blogs > Quality Assurance and Project Management/

Quality Assurance and Project Management:

testing plan

1
September 16, 2009  12:00 PM

Five ways to workout ‘testing effort”



Posted by: Jaideep Khanduja
business rule, business specification, customer requirement, customer specification, development phase, development plan, functional testing, load testing, performance testing, QC, QC head, software development, software product, Software Project, team size, test case, test effort, Test Plan, tester, testing effort, testing effort estimation, testing phase, testing plan

A new project, a new product development – as a QC head how do you estimate your testing effort? Well, some quick steps for this: 1. Customer requirements: Customer specifications or requirements captured at the time of initial study period would be a quick reference guide for estimating...

  Bookmark and Share     0 Comments     RSS Feed     Email a friend

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...

  Bookmark and Share     0 Comments     RSS Feed     Email a friend

1