The advantages of Keyword driven testing using QTP are:

1. In QTP, test-driven keyword lets you design your tests at the company level rather than at the object. For example, QTP may recognize a unique selection option in your application as several steps: clicking a button object, a mouse operation on an object list, then a keyboard operation on a sub-list-item. You can create one based on an appropriate name to represent all of these lower-level operations into one company by keyword.

2. By integrating the technical operations, as a declaration of synchronization waiting communications client-server to the end, keyword level, tests are easy to read and easier for application testers less technical to maintain when the application rates.

3. Keyword-driven testing naturally leads to a more effective separation between the maintenance and servicing of test assets. This allows automation experts to focus on maintaining the objects and functions, while application testers focused on maintaining the test structure and design.

4. When testing for registration, you may not notice that new items are added to the local object repository. This may lead to many testers managing local object repositories with copies of the same objects. When you use a keyword-based methodology, you select items for your steps from the existing object repository. When you need a new object, you can add it to your local object repository temporarily, but you are also aware that you must add the shared object repository for future use.

5. When you save a test, QTP between good objects, methods and values of arguments for you. Therefore, it is possible to create a test with little preparation or planning. While this makes it easier to create tests quickly, these tests are more difficult to maintain when the application changes and often require re-registration of large parts of the test.

6. When you use a keyword-based methodology, you select from existing objects and operation keywords. Therefore, you must be familiar with the two object repositories and libraries of functions that are available. You must also have a good idea of what you want your test to look like before starting the integration steps. This usually results in well planned and structured tests, which also leads to easier maintenance long term.

7. Automation experts can add objects and functions based on detailed product specifications before the feature was added to a product. Using test-driven keyword, you can begin to develop tests for a new product or function earlier in the development cycle.