Quality Center Tips

What in your view is the best Automation framework with QC Implementation - BTP or Actions or anything else??

I would prefer the Bussiness Processing Test is the best process in QC.
:)

Hi Vannu
Thats right.... But dont you think that initializing the Business Components takes a lot of time. Whereas calling the Reusable Actions in a driver script is comparitively much faster. Therefore the execution time is much less.

Thats right debleena but if you dont initialize the component as well as common components then it will be a mess.The updated components will not be reflected in your test bed....what you can do ....delete all the previous cookies files and used initialization files through coding ...that can make the system fast

But again we can think of new framework......Test anywhere will be one of the best option

The test script modularity framework the test script modularity framework requires the creation of small, independent scripts that represent modules, sections, and functions of the application-under-test. These small scripts are then used in a hierarchical fashion to construct larger tests, realizing a particular test case. Of all the frameworks i'll review, this one should be the simplest to grasp and master. It's a well-known programming strategy to build an abstraction layer in front of a component to hide the component from the rest of the application. This insulates the application from modifications in the component and provides modularity in the application design. The test script modularity framework applies this principle of abstraction or encapsulation in order to improve the maintainability and scalability of automated test suites.

The test library architecture framework the test library architecture framework is very similar to the test script modularity framework and offers the same advantages, but it divides the application-under-test into procedures and functions instead of scripts. This framework requires the creation of library files (sqabasic libraries, apis, dlls, and such) that represent modules, sections, and functions of the application-under-test. These library files are then called directly from the test case script.

The Keyword-Driven or Table-Driven Testing Framework

Keyword-driven testing and table-driven testing are interchangeable terms that refer to an application-independent automation framework. This framework requires the development of data tables and keywords, independent of the test automation tool used to execute them and the test script code that "drives" the application-under-test and the data. Keyword-driven tests look very similar to manual test cases. In a keyword-driven test, the functionality of the application-under-test is documented in a table as well as in step-by-step instructions for each test.

The Data-Driven Testing Framework

Data-driven testing is a framework where test input and output values are read from data files (datapools, ODBC sources, cvs files, Excel files, DAO objects, ADO objects, and such) and are loaded into variables in captured or manually coded scripts. In this framework, variables are used for both input values and output verification values. Navigation through the program, reading of the data files, and logging of test status and information are all coded in the test script.

This is similar to table-driven testing in that the test case is contained in the data file and not in the script; the script is just a "driver," or delivery mechanism, for the data. Unlike in table-driven testing, though, the navigation data isn't contained in the table structure. In data-driven testing, only test data is contained in the data files.

The hybrid test automation framework


The hybrid test automation framework the most commonly implemented framework is a combination of all of the above techniques, pulling from their strengths and trying to mitigate their weaknesses. This hybrid test automation framework is what most frameworks evolve into over time and multiple projects.

I hope the above written discussion will give you all a little bit of idea regarding automation framework...
detailed discussion will be given in the next posts