Testers can apply every input and cover every line of code in test cases and still the software can have very serious bugs. Yes, testers can cover every single line of code by different techniques but the problem we face is related to estimates, budgeting, priortization etc. I never saw anyone considering all of them without making any compromises or trade-offs.
What we need is a way to identify what parts of the product can be tested, a bill of materials if you will, and then map our actual testing back to each part so that we can measure progress against the overall testing goal. James, are you referring to Scope of Testing, Test Coverage and Risk Based Testing? Who should actually define these things, a tester or a product expert (because a tester may not be the correct person initially)?
I am looking forward to attend GTAC at Hyderabad this year and wish to gain more understanding on the subject from you.
Testers can apply every input and cover every line of code in test cases and still the software can have very serious bugs.
ReplyDeleteYes, testers can cover every single line of code by different techniques but the problem we face is related to estimates, budgeting, priortization etc. I never saw anyone considering all of them without making any compromises or trade-offs.
What we need is a way to identify what parts of the product can be tested, a bill of materials if you will, and then map our actual testing back to each part so that we can measure progress against the overall testing goal.
James, are you referring to Scope of Testing, Test Coverage and Risk Based Testing?
Who should actually define these things, a tester or a product expert (because a tester may not be the correct person initially)?
I am looking forward to attend GTAC at Hyderabad this year and wish to gain more understanding on the subject from you.