Explore topic-wise InterviewSolutions in .

An Application MAP Provides NAMED References for GUI COMPONENTS. Application Maps are NOTHING but "Object Repositry"

An Application Map Provides Named References for GUI Components. Application Maps are nothing but "Object Repositry"

Keyword is an ACTION that can be PERFORMED on a GUI Component. Ex . For GUI Component TEXTBOX some Keywords ( Action) would be InputText, VerifyValue, VerifyProperty and so on.

Keyword is an Action that can be performed on a GUI Component. Ex . For GUI Component Textbox some Keywords ( Action) would be InputText, VerifyValue, VerifyProperty and so on.

FOLDER STRUCTURE:

1. ObjectRepository
2. Environment
3. FunctionLibrary

• Company
• ProjectSpecific

4. TestData
5. TestResult
6. RecoveryScenarios
7. Organizer
8. Drivers
9. Miscellaneous

Folder Structure:

1. ObjectRepository
2. Environment
3. FunctionLibrary

4. TestData
5. TestResult
6. RecoveryScenarios
7. Organizer
8. Drivers
9. Miscellaneous

In order to create, store, organize and manage files, a WELL defined folder structure is required. Folder structure is a MANDATORY element of any framework, but folder names MAY vary from one framework to another and company to another.

In order to create, store, organize and manage files, a well defined folder structure is required. Folder structure is a mandatory element of any framework, but folder names may vary from one framework to another and company to another.

• Well DEFINED folder structure
• INITIALIZATION script
• Driver script
• Organizer spreadsheet
• PROCESS GUIDELINES document

• TEST Objects (EX: Browser, page, webEdit, WinButton---etc)
• Functions (Built-In and USER DEFINED)
• Methods (Ex: Set, Select, Activate, Navigate---etc)
• Statements (EX:Dim ,If, For, EXIT, wait, option explicit ---etc)
• Operators (EX: +,/,*,and, or, not---etc

Any word used as the KEY to a CODE A reserved word used to identify a SPECIFIC COMMAND or function or method or statement or OPERATOR or object etc.

Any word used as the key to a code A reserved word used to identify a specific command or function or method or statement or operator or object etc.

In this APPROACH KEYWORDS can be USED for creating and EXECUTING tests.

In this approach keywords can be used for creating and executing tests.

Tasks to be performed:

a) Analyzing the application in terms of Object Identification:

we have to analyze the AUT in terms of Object Identification.

Basically, QTP is an Object based test tool, here first we have to confirm 

if the QTP is recognizing all the objects in our application or not.

To do this, we can follow one or more below given methods...

• Record and playback some End to End Scenarios.
• Using Object SPY
• Using Object Repository Manager

 We can segregate Software Objects in 3 categories...

• Static Objects(Properties information is constant)
• Dynamic Objects(Properties info changes dynamically)
• Duplicate Objects(Having Similar property info.)

Note: We can handle dynamic Objects using Regular expressions and handle duplicate

Objects using "Index" property. 

b) Selecting Areas/Test Cases for Automation 

Overview: 

100% test automation is not possible, we can go for MAXIMUM automation.

Generally we select below type of Tests for Automation:

• Tests that we have to execute on every build (EX: Sanity Tests)
• Tests that we have to execute on every modified build (Ex: Regression Tests)
• Tests that we have to execute with multiple SETS of test data.(Ex: Data Driven Tests) 
• Tests having complex FUNCTIONALITY 

c) Planning (Effort estimation, Schedule, Work allocation and Automation Framework implementation)

Overview: 

After selecting some areas for Automation, we have to estimate the efforts

in terms of Scope of the Project, time and resources(Environmental and Human)

To estimate efforts, we can follow an one of the below given methods:

• Using Expert based techniques.
• Experienced based techniques.
• Function point analysis.

1. Identifying End to End Scenarios.
2. Identifying verification points.
3. Identifying General and Alternate Flows.
4. Identifying the modularity.
5. Identifying the complex functionality. 

d) Creating Generic and project specific functions.

e) Creating required Automation resources(Functions, Object repository Files, Environment variable files---etc)

f) Creating Tests(Using Object Repository or Descriptive Programming)

g) Enhancing Tests(Inserting Checkpoints, Output Values, Transaction points, Flow Control Statements, Synchronization, Parametrization---etc )

h) Debugging and running tests(Individual test execution, Test Batch execution --etc)

i) Defining and exporting test results

j) Analyzing results

k) Defect Reporting using Our Company defect management system.

l) Modifying resources and tests (if required)

m) Performing Re and regression testing 

n) Maintaining Automation Resources 

Tasks to be performed:

a) Analyzing the application in terms of Object Identification:

we have to analyze the AUT in terms of Object Identification.

Basically, QTP is an Object based test tool, here first we have to confirm 

if the QTP is recognizing all the objects in our application or not.

To do this, we can follow one or more below given methods...

 We can segregate Software Objects in 3 categories...

Note: We can handle dynamic Objects using Regular expressions and handle duplicate

Objects using "Index" property. 

b) Selecting Areas/Test Cases for Automation 

Overview: 

100% test automation is not possible, we can go for maximum automation.

Generally we select below type of Tests for Automation:

c) Planning (Effort estimation, Schedule, Work allocation and Automation Framework implementation)

Overview: 

After selecting some areas for Automation, we have to estimate the efforts

in terms of Scope of the Project, time and resources(Environmental and Human)

To estimate efforts, we can follow an one of the below given methods:

d) Creating Generic and project specific functions.

e) Creating required Automation resources(Functions, Object repository Files, Environment variable files---etc)

f) Creating Tests(Using Object Repository or Descriptive Programming)

g) Enhancing Tests(Inserting Checkpoints, Output Values, Transaction points, Flow Control Statements, Synchronization, Parametrization---etc )

h) Debugging and running tests(Individual test execution, Test Batch execution --etc)

i) Defining and exporting test results

j) Analyzing results

k) Defect Reporting using Our Company defect management system.

l) Modifying resources and tests (if required)

m) Performing Re and regression testing 

n) Maintaining Automation Resources 

It is a COMBINATION of 2 or more approaches

Ex:

Modular framework and Data driven framework

ADVANTAGES: 

• SCOPE is very HIGH as we MIX different approaches.
• Flexible for performing all types of tasks.

Drawbacks:

• Organizing and managing resources are difficult
• Complex architecture.
• Low in performance.

It is a combination of 2 or more approaches

Ex:

Modular framework and Data driven framework

Advantages: 

Drawbacks:

In this APPROACH tests can be CREATED and EXECUTED USING KEYWORDS

In this approach tests can be created and executed using keywords

Description:

In this APPROACH tests can be executed using multiple sets of test data

ADVANTAGES: 

• POSITIVE and negative testing can be performed
• Checking the reliability of system (AUT)

Disadvantages:

• Maintaining resources is DIFFICULT
• Less or no concentration on complex FUNCTIONALITY testing

Description:

In this approach tests can be executed using multiple sets of test data

Advantages: 

Disadvantages:

Description: 

In this approach tests can be created and EXECUTED using reusable components.

Advantages:

• CENTRALIZED MAINTENANCE of resources 
• High in performance
• Modifications are EASY
• Concentration on complex functionality testing

Disadvantages:

• SCRIPTING knowledge is mandatory
• Less or no concentration on data driven testing
• Takes more time to create

Description: 

In this approach tests can be created and executed using reusable components.

Advantages:

Disadvantages:

Description: 

In this approach tests can be created and executed using RECORDING feature.

Advantages:

• Easy to CREATE and takes less time
• Scripting KNOWLEDGE is optional
• Recommended for small scale projects 
• Recommended for dynamically changing requirements

Disadvantages:

• No centralized maintenance of test objects
• Low in performance due to duplicate objects
• Less or no CONCENTRATION on complex functionality testing
• Less or no concentration on data driven testing
• No centralized maintenance of RESOURCES

Description: 

In this approach tests can be created and executed using recording feature.

Advantages:

Disadvantages:

AUTOMATION Framework is not a QTP Tool feature, it’s a 3rd party concept. And this is purely local concept.(framework may vary from one company to another and One PROJECT to another)

• Record/Playback or Linear Framework (1st generation framework).
• MODULAR Framework.
• DATA DRIVEN Framework
• Keyword Driven framework
• Hybrid Framework Etc..

Automation Framework is not a QTP Tool feature, it’s a 3rd party concept. And this is purely local concept.(framework may vary from one company to another and One project to another)

Files to be used:

• Flat files (.txt),
• Excel files (.XLS)
• Object repository files (.tsr)
• XML files (.xml)
• Library files (.vbs/.qfl)
• Test Scripts (.mts)
• Test Batch Files (.MTB) 
• Recovery scenario files (.qrs)
• Test RESULT FILE (.XML) Etc...

Files to be used:

In one project test automation we CREATE and use DIFFERENT types of files and we perform different types of tasks, in order to ORGANIZE and manage them all, a systematic approach (Automation FRAMEWORK) is REQUIRED.

In one project test automation we create and use different types of files and we perform different types of tasks, in order to organize and manage them all, a systematic approach (Automation Framework) is required.

A SET of guidelines, ASSUMPTIONS and process developed by experts in ORDER to PERFORM a TASK(s) in an effective, efficient and optimized way.

A set of guidelines, assumptions and process developed by experts in order to perform a task(s) in an effective, efficient and optimized way.