Happy Republic Day

जन  गण   मन   अधिनायक  जाया  हे

भारत  भाग्य  विधाता
पुनजब  सिंध  गुजरात  मराठा
द्रविदा  उत्कल  बंग
विन्ध्य  हिमाचल  यमुना  गंगा
उच्चाला  जलधि  तरंगा
तुभ  शुबहा  नामे  जगे
तुभ   शुबहा  आशीष  मांगे
गए    तुभ  जाया  गाथा
जन   गन  मंगलदायक  जय  हे
भारत  भाग्य  विधाता
जाये  हे  ! जाये  हे  ! जाये  हे  !
जाये ,जाये ,जाये ,जाये  हे  "

Test object model in QTP

The test object model is a large set of object types or classes that QuickTest uses to represent the objects in your application. Each test object class has a list of properties that can uniquely identify objects of that class and a set of relevant methods that QuickTest can record for it.

A test object is an object that QuickTest creates in the test or component to represent the actual object in your application. QuickTest stores information about the object that will help it identify and check the object during the run session.

A run-time object is the actual object in your Web site or application on which methods are performed during the run session. When you perform an operation on your application while recording,

QuickTest:

➤ identifies the QuickTest test object class that represents the object on which you performed the operation and creates the appropriate test object

➤ reads the current value of the object's properties in your application and stores the list of properties and values with the test object

➤ chooses a unique name for the object, generally using the value of one of its prominent properties

➤ records the operation that you performed on the object using the appropriate QuickTest test object method

For example, suppose you click on a Find button with the following HTML

source code:

< type="submit" name="Find" value="Find">

QuickTest identifies the object that you clicked as a WebButton test object. It creates a WebButton object with the name Find, and records the following properties and values for the Find WebButton. It also records that you performed a Click method on the WebButton.

QuickTest displays your step in the Expert View like this:

Browser("Mercury Interactive").Page("Mercury Interactive").

WebButton("Find").Click

Steps to develop and run software tests

The following are some of the steps to consider:

•  Obtain requirements, functional design, and internal design specifications, user stories, and other available/necessary information
• Obtain budget and schedule requirements
• Determine project-related personnel and their responsibilities, reporting requirements, required standards and processes (such as release processes, change processes, etc.)
• Determine project context, relative to the existing quality culture of the product/organization/business, and how it might impact testing scope, aproaches, and methods.
• Identify application's higher-risk and mor important aspects, set priorities, and determine scope and limitations of tests.
• Determine test approaches and methods - unit, integration, functional, system, security, load, usability tests, etc.
• Determine test environment requirements (hardware, software, configuration, versions, communications, etc.)
•  Determine testware requirements (automation tools, coverage analyzers, test tracking, problem/bug tracking, etc.)
•  Determine test input data requirements
•   Identify tasks, those responsible for tasks, and labor requirements
•   Set schedule estimates, timelines, milestones
• Determine, where apprapriate, input equivalence classes, boundary value analyses, error classes
• Prepare test plan document(s) and have needed reviews/approvals
• Write test cases
• Have needed reviews/inspections/approvals of test cases
• Prepare test environment and testware, obtain needed user manuals/reference documents/configuration guides/installation guides, set up test tracking processes, set up logging and archiving processes, set up or obtain test input data
• Obtain and install software releases
• Perform tests
• Evaluate and report results
• Track problems/bugs and fixes
•  Retest as needed
• Maintain and update test plans, test cases, test environment, and testware through life cycle