1. Prepare the automation Test plan 2. Identify the scenario 3. Record the scenario 4. Enhance the scripts by inserting check points and Conditional Loops 5. Incorporated Error Hnadler 6. Debug the script 7. Fix the issue 8. Rerun the script and report the result.
This is answer to Test strategy. The testing strategy should define the objectives of all test stages and the techniques that apply. The testing strategy also forms the basis for the creation of a standardised documentation set, and facilitates communication of the test process and its implications outside of the test discipline. Any test support tools introduced should be aligned with, and in support of, the test strategy. Whereas the test plan is the requirements definition and design specifications facilitate in the identification of major test items and these may necessitate the test strategy to be updated. A detailed test plan and schedule is prepared with key test responsibilities being indicated
Test Plan is a document it is created by the test lead or the test manager which contains whole testing activity that we are going to perform on the application. Companies will fallow their own way while dsigning of these documents. Generally test plan is created for every phases in the testing phases that means for Unit testing Unit testplan , for intigration Intigaration test plan, ... system test plan....
Test stratergy is the document which briefly discribes the testing activity.
Test plan is desribed by test lead,in that plan we are going to test the application,testing is started with this planing area,in that what to test ,who to test ,when to test and where to test of the particular application.planing contains
You plan test automation when you are repeat test scenarios over and over in different builds.
Test automation is done in function, regression and also in integration testing.
Depending on the automation scenario you could write your own automation tool or use a market licensed version or a open source one.
eg: In Integration testing of modules on an Unix platform Shell scripts are often used to automate the testing.
Likewise in CRM applications Junit , C etc can be used to build your own tools.
When GUI testing is involved Vendor supplied tools like Silk is often used in functionality testing and regression testing.
Planning of automation is done based on the project needs, timeline , resources available, skill of the resources and the cost involved.
In many product companies that own a dedicated QA department vendor licensed tool is widely used. The Lead hence can plan on usage of this based on the identifcation of scenarios. In small companies writings one's own automation tool is encouraged to help speed the testing process.
