Test Approach is the Strategy which decsribes the test
team's approch to test the software both Overall & also in
each phase.It gives better idea for the team to plan and
execute the testing phase with perfection.
Deciding on the strategy is a complex task—one that needs
to be made by very experienced testers because it can
determine the success or failure of the test effort.
Test Approach is nothing but your approach to test a particular functionality. It is mostly a part of test plan but having said that in some specific project or domain you may be asked to document the test approach separately.
Lets take an example:
You are asked to test a shopping kart of an e-commerce application.
You first list down the scope of testing and then you document how you plan to test this functionality. This becomes your test approach.
You define what type of testing you want to do like feature testing, GUI testing and then you need to define how you plan to do this testing;
EX: Feature Testing->Data validation will be done in UI. QA would develop short SQL queries to validate the data displayed in the system matches with the data in the DB
Check following parameters for user interface:
Check visual aspects
Check for edit style
Check for appropriate format mask
Check the field width at user interface level with that at the data base level
Check for the data-type mismatch and truncation
Check for filter condition & sort order for query
Perform string testing
Check for cursor position after data entry
Check for the next navigable field
Hope this clears your doubt.
Happy hunting for bugs [img]/images/graemlins/smile.gif[/img]