• RSS
  • Facebook
  • Twitter

One Center for all the Testing Need. OneTestingCenter is for all, for all QA, for all Automation. Automation is easy, fun and enriching experience. Happy Learning and Happy Testing!

  • Access to All QA

    At OneTestingCenter, you find lots of books,articles,blogs and detailed guides. Everyone has access to QA. Happy Learning, Happy Testing.

  • Global Trainings

    All the QA/Auotmation trainings are available at OneTestingCenter. QA, Automation, QTP/UFT, Selenium, LoadRunner, QC/ALM, Appium...

  • Automation Learning Fun

    Technology is always evolving. Automation is always challenging. To be frank, Automation is fun, enthusiastic and enrching experience.



    • Keyword Driven Framework Complete Guide

      • GAReddy@OneTestingCenter@QTP@Framework 
      • Keyword Framework Complete Guide 
      • QTP - Keyword Driven Framework - Step by Step Guide 
      • Practical Guide to Keyword Driven Framework



    Keyword Driven Framework 

    What is an Automation Framework 
    • Automation Framework is a well-structured, planned, practiced and supported environment for Automation Testing 
    •  It’s a warehouse where automation testing process begins, executes, accumulates results and ends up.  Automation Framework uses fully established implementation such as initiation, moderation, execution and finalization. 
    • Automation Framework is the complete reference of the Automation Testing Process representing structure, process guidelines, and implementation and so on. 
    • Test automation framework is a set of assumptions, concepts, and practices that provide support for automated software testing. 
    • A comprehensive architecture to drive the complete test automation process. 

     Keyword Driven Framework is the process of driving the tests / actions / test cases based on keywords.
     Keywords could be anything but that should define the purpose, Keywords could give need for re-usability, Keywords could establish bridge between Application and test script. Mostly Keywords are the methods / actions / activities that could relate


     




    Software – Requirements Flow
    Let’s get started


    Requirements Flow:
     
    Everyone is aware that the application is designed for end users based on the customer requirements.
    But, only few people are aware that there is lot of process that draw the customer requirements into different layers before converting / designing into an application.

    Here is the explanation.

    Just have a look at the diagram.
    More information with regards to the Requirements Flow could be added to the table at the later editions.




    Requirement:            
    The basic customer needs are called as Requirements.
    The set of all customer needs put together is called requirements document or marketing requirements document.



    BRS (Business Requirement Specification):
    ·         At Business level, all the customer requirements are documented , designed and approved by customer.
    ·         All these bossiness requirements should exactly map to end user real-time scenarios


    FRS (Function Requirements Specification):
    The BRS are segregated into different Functions / Modules and are described in more detailed and such that more detailed information is provided with respect all the functions / modules of the application.



    SRS (Software Requirement Specification):
    In depth of the requirements, such as the detailed information like windows / dialog boxes information, field level information and Just as clear-cut document for coding and prototypes are called as SRS



    SRS (System Requirement Specification):
    The entire SRS (Software Requirement Specification) are merged together so as to make complete System approach is called System Requirement Specification


    Use Cases 
    Use Case is a document that describes the User actions versus System / Application responses







    QA – Introduction To Testing
    Let’s get started

    You would be able to learn the following, at the end of this chapter

    o   What are the advantages of Testing?
    o   How do we Test?
    o   Who are needed Testing?
    o   What is a Defect / Bug?
    o   Explain in detail about Testing Process

    Introduction to Testing

    o     Testing is the process of executing a program with the intention of finding errors
    o     Testing is the process of verifying an application to check if the application is behaving as per the requirements / specifications.
    o     Testing is the process of executing test cases on the application to differentiate between expected and actual results.
    o     Testing is the process of V and V ( Verification and Validation)
    o     Testing is obviously concerned with finding bugs, defects, errors, faults, failures and incidents with the applications.
    o     Testing is the process of verifying customers’ needs with respect of the designed software/application
    o     Testing is the combined process of Analyzing / Understanding the Reqs, Designing  Test Cases, Executing Test Cases, Reporting Test Status, Supporting Application



    You can learn the following:




    QTP Learning – Part1

    Let’s get started

    You would be able to learn the following, at the end of this chapter

    o   What is QTP?
    o   What is Automation?
    o   Why do we need QTP?
    o   What are the advantages of Automation?
    o   How do we record and playback test scripts in QTP
    o   What is Object
    o   Explain about Object Repository
    o   Explain about Object Properties
    o   Explain about Object Methods
    o   What are the deferent QTP - Script Generation Methods
    o   What are the QTP - Script Recording Modes
    o   Explain about Analog - Screen based and Window based recording mode with examples
    o   How do we code Test Scripts in QTP
    o   What are needed for scripting/coding test scripts in QTP
    o   What are the object types in automation
    o   Explain in detail about Test Object and Run-Time Object
    o   What are the Advantages of QTP
    o   What is low-level recording mode and why it is used for?



    Introduction to QTP

    o     Was  a Mercury Interactive Test tool
    o     Now, HP -  Automation Test Tool
    o     The Latest version of QTP is called as UFT – Unified Functional Testing.
    o     Functional test tool
    o     Regression test tool
    o     Supports Stand alone, Web based and Client Server Apps
    o     Supports One tier / Two tier / Three tier  / N-tier Apps
    o     Designed to provide a robust  application verification
    o     Simple and easy to use and implement
    o     As simple as a Tape recorder
    o     Best at even record and play back
    o     Can be utilized at advanced level (coding, objects creation)
    o     Supports COM /DCOM/DOM/AOM
    o     Different Environments supported (Java, .NET, SAP…)
    o     Add ins available for other environment supports

    o   “Quick Test Professional” popularly called as QTP, originally from a company known as Mercury Interactive, which was acquired by Hewlett Packard (HP) in 2006 and is now HP’s QuickTest Professional
    o   The Latest version of QTP is called as UFT – Unified Functional Testing.
    o   QTP is primarily used for functional and regression automated testing.
    o   QTP can automate user actions on a window; web or client based computer application and tests the same actions for different users, and different data sets on various windows operating systems and on different browsers.
    o   It’s an easy tool to lean and implement automation testing.
    o   Automation using QTP saves lot of time, efforts, resources, and budget.
    o   It is as simple as a Tape recorder to record and playback test scripts
    o   Quick Test Professional can be utilized at advance level coding and object creation and also support COM/DCOM/DOM/AOM.
    o   QTP supports different environments like Java, .Net, SAP, Web, Windows and so on.

    You can learn the following:


    QTP at Glance




    QTP is a UI automation tool designed for Windows and Web-based and enterprise applications testing. It works by identifying the objects in the application UI or a web page and performing the desired operations on them (like mouse clicks or keyboard events); it can also be used to capture object properties like object name or handler ID , height, width etc.
    QTP is also known as UFT(Unified Functional Testing) The latest version of QTP / UFT is 11.51
    • One of the most important topics in QTP is Object Identification. QTP uses VBScript as scripting language to specify the test procedure and to manipulate the objects and controls of the application under test (AUT) Though QTP is usually used for Functional / "UI Based" Test Case Automation, it can easily handle "Non-UI" based Test Cases. (Example: API testing, Database testing, etc.)
    You can learn the following:

    Information Steps 

    QTP - Keyword Driven Framework - Complete Guide



    • Keyword Driven Framework Complete Guide

      • GAReddy@OneTestingCenter@QTP@Framework 
      • Keyword Framework Complete Guide 
      • QTP - Keyword Driven Framework - Step by Step Guide 
      • Practical Guide to Keyword Driven Framework

    QTP - Keyword Driven Framework - Complete Guide - Video



    Keyword Driven Framework 

    What is an Automation Framework 
    • Automation Framework is a well-structured, planned, practiced and supported environment for Automation Testing 
    •  It’s a warehouse where automation testing process begins, executes, accumulates results and ends up.  Automation Framework uses fully established implementation such as initiation, moderation, execution and finalization. 
    • Automation Framework is the complete reference of the Automation Testing Process representing structure, process guidelines, and implementation and so on. 
    • Test automation framework is a set of assumptions, concepts, and practices that provide support for automated software testing. 
    • A comprehensive architecture to drive the complete test automation process. 

     Keyword Driven Framework is the process of driving the tests / actions / test cases based on keywords.
     Keywords could be anything but that should define the purpose, Keywords could give need for re-usability, Keywords could establish bridge between Application and test script. Mostly Keywords are the methods / actions / activities that could relate


     

    Software – Requirements Flow





    Software – Requirements Flow
    Let’s get started


    Requirements Flow:
     
    Everyone is aware that the application is designed for end users based on the customer requirements.
    But, only few people are aware that there is lot of process that draw the customer requirements into different layers before converting / designing into an application.

    Here is the explanation.

    Just have a look at the diagram.
    More information with regards to the Requirements Flow could be added to the table at the later editions.




    Requirement:            
    The basic customer needs are called as Requirements.
    The set of all customer needs put together is called requirements document or marketing requirements document.



    BRS (Business Requirement Specification):
    ·         At Business level, all the customer requirements are documented , designed and approved by customer.
    ·         All these bossiness requirements should exactly map to end user real-time scenarios


    FRS (Function Requirements Specification):
    The BRS are segregated into different Functions / Modules and are described in more detailed and such that more detailed information is provided with respect all the functions / modules of the application.



    SRS (Software Requirement Specification):
    In depth of the requirements, such as the detailed information like windows / dialog boxes information, field level information and Just as clear-cut document for coding and prototypes are called as SRS



    SRS (System Requirement Specification):
    The entire SRS (Software Requirement Specification) are merged together so as to make complete System approach is called System Requirement Specification


    Use Cases 
    Use Case is a document that describes the User actions versus System / Application responses





    QA – Introduction To Testing



    QA – Introduction To Testing
    Let’s get started

    You would be able to learn the following, at the end of this chapter

    o   What are the advantages of Testing?
    o   How do we Test?
    o   Who are needed Testing?
    o   What is a Defect / Bug?
    o   Explain in detail about Testing Process

    Introduction to Testing

    o     Testing is the process of executing a program with the intention of finding errors
    o     Testing is the process of verifying an application to check if the application is behaving as per the requirements / specifications.
    o     Testing is the process of executing test cases on the application to differentiate between expected and actual results.
    o     Testing is the process of V and V ( Verification and Validation)
    o     Testing is obviously concerned with finding bugs, defects, errors, faults, failures and incidents with the applications.
    o     Testing is the process of verifying customers’ needs with respect of the designed software/application
    o     Testing is the combined process of Analyzing / Understanding the Reqs, Designing  Test Cases, Executing Test Cases, Reporting Test Status, Supporting Application



    You can learn the following:

    QTP Learning - Part1




    QTP Learning – Part1

    Let’s get started

    You would be able to learn the following, at the end of this chapter

    o   What is QTP?
    o   What is Automation?
    o   Why do we need QTP?
    o   What are the advantages of Automation?
    o   How do we record and playback test scripts in QTP
    o   What is Object
    o   Explain about Object Repository
    o   Explain about Object Properties
    o   Explain about Object Methods
    o   What are the deferent QTP - Script Generation Methods
    o   What are the QTP - Script Recording Modes
    o   Explain about Analog - Screen based and Window based recording mode with examples
    o   How do we code Test Scripts in QTP
    o   What are needed for scripting/coding test scripts in QTP
    o   What are the object types in automation
    o   Explain in detail about Test Object and Run-Time Object
    o   What are the Advantages of QTP
    o   What is low-level recording mode and why it is used for?



    Introduction to QTP

    o     Was  a Mercury Interactive Test tool
    o     Now, HP -  Automation Test Tool
    o     The Latest version of QTP is called as UFT – Unified Functional Testing.
    o     Functional test tool
    o     Regression test tool
    o     Supports Stand alone, Web based and Client Server Apps
    o     Supports One tier / Two tier / Three tier  / N-tier Apps
    o     Designed to provide a robust  application verification
    o     Simple and easy to use and implement
    o     As simple as a Tape recorder
    o     Best at even record and play back
    o     Can be utilized at advanced level (coding, objects creation)
    o     Supports COM /DCOM/DOM/AOM
    o     Different Environments supported (Java, .NET, SAP…)
    o     Add ins available for other environment supports

    o   “Quick Test Professional” popularly called as QTP, originally from a company known as Mercury Interactive, which was acquired by Hewlett Packard (HP) in 2006 and is now HP’s QuickTest Professional
    o   The Latest version of QTP is called as UFT – Unified Functional Testing.
    o   QTP is primarily used for functional and regression automated testing.
    o   QTP can automate user actions on a window; web or client based computer application and tests the same actions for different users, and different data sets on various windows operating systems and on different browsers.
    o   It’s an easy tool to lean and implement automation testing.
    o   Automation using QTP saves lot of time, efforts, resources, and budget.
    o   It is as simple as a Tape recorder to record and playback test scripts
    o   Quick Test Professional can be utilized at advance level coding and object creation and also support COM/DCOM/DOM/AOM.
    o   QTP supports different environments like Java, .Net, SAP, Web, Windows and so on.

    You can learn the following:

    QTP at Glance



    QTP at Glance




    QTP is a UI automation tool designed for Windows and Web-based and enterprise applications testing. It works by identifying the objects in the application UI or a web page and performing the desired operations on them (like mouse clicks or keyboard events); it can also be used to capture object properties like object name or handler ID , height, width etc.
    QTP is also known as UFT(Unified Functional Testing) The latest version of QTP / UFT is 11.51
    • One of the most important topics in QTP is Object Identification. QTP uses VBScript as scripting language to specify the test procedure and to manipulate the objects and controls of the application under test (AUT) Though QTP is usually used for Functional / "UI Based" Test Case Automation, it can easily handle "Non-UI" based Test Cases. (Example: API testing, Database testing, etc.)
    You can learn the following:

    Information Steps