Testing Skills » Manual Testing » Manual Testing Using BPT
Application areas contain all of the resources and settings required to create the content of keyword-driven business components for a particular application or part of an application.
These include representations of the objects from your application, which are stored in a shared object repository, user-defined operations stored in function libraries, associated add-ins, recovery scenarios, and so on.
The state of the application before the first step in a business component, and the state of the application after the last step in a business component. For example, the pre-condition for a component may state that all applications should be closed, or a specific application should be open to a specific screen or with a specific dialog box displayed. A post-condition may state that an application should be open to a particular screen, or be closed.
If you want the business component to allow iterations, the post-conditions
should specify that the application’s end state must match its state at the
beginning of the component. The pre-conditions and post-conditions
provide a guide when implementing the steps for the business component.
Manual Testing Using BPT
Posted 15-04-2009Reply
Can any one explain how to perform Manual testing using BPT.
It should cover all activities of testing process such as RTM and Defect tracking.
should not use QTP for this.
Business Component (or Component).
An easily-maintained, reusable unit comprising one or more steps that perform a specific task. A business component can be defined as a manual or automated component. Business components may require input values from an external source or from other components, and they can return output values to other components.
An easily-maintained, reusable unit comprising one or more steps that perform a specific task. A business component can be defined as a manual or automated component. Business components may require input values from an external source or from other components, and they can return output values to other components.
The Business Process Testing model is role-based, allowing non-technical
Subject Matter Experts to work on tests with Automation Engineers, both
together and in parallel. These roles are flexible, and depend on the abilities
and time resources of the personnel using Business Process Testing. There
are no limitations or product-specific rules controlling which roles must be
defined in a particular organization, or which types of users can do which
Business Process Testing tasks (provided that the users have the correct
permissions).
The Business Process Testing model also follows a workflow that is
supported by the user interface design. By following the roles and workflow
that Business Process Testing offers, you can maximize the quality and
efficiency of the testing process in your organization.
Subject Matter Experts to work on tests with Automation Engineers, both
together and in parallel. These roles are flexible, and depend on the abilities
and time resources of the personnel using Business Process Testing. There
are no limitations or product-specific rules controlling which roles must be
defined in a particular organization, or which types of users can do which
Business Process Testing tasks (provided that the users have the correct
permissions).
The Business Process Testing model also follows a workflow that is
supported by the user interface design. By following the roles and workflow
that Business Process Testing offers, you can maximize the quality and
efficiency of the testing process in your organization.
About Business Process Testing
Business Process Testing enables Subject Matter Experts to design quality
assurance tests early in the development cycle and in a script-free
environment.
Business Process Testing is based on the creation, implementation, and
running of business components in business process tests using the Quality
Center Business Components, Test Plan, and Test Lab modules.
1) The Business Components module enables you to create, manage, and
automate reusable business components, comprising steps that perform
specific tasks in a business process.
2) The Test Plan module enables you to drag and drop the components into
business process tests, and debug the components.
3) The Test Lab module enables you to run business process tests and view the results.
Business Process Testing enables Subject Matter Experts to design quality
assurance tests early in the development cycle and in a script-free
environment.
Business Process Testing is based on the creation, implementation, and
running of business components in business process tests using the Quality
Center Business Components, Test Plan, and Test Lab modules.
1) The Business Components module enables you to create, manage, and
automate reusable business components, comprising steps that perform
specific tasks in a business process.
2) The Test Plan module enables you to drag and drop the components into
business process tests, and debug the components.
3) The Test Lab module enables you to run business process tests and view the results.
Business Component (or Component).
An easi... See Yuvraj's complete reply
About Application Area:An easi... See Yuvraj's complete reply
Application areas contain all of the resources and settings required to create the content of keyword-driven business components for a particular application or part of an application.
These include representations of the objects from your application, which are stored in a shared object repository, user-defined operations stored in function libraries, associated add-ins, recovery scenarios, and so on.
Business Process Test.
A scenario comprising a serial flow of business components, designed to test a specific business process of an application.
Business Process Test Run-Time Parameters.
Variable values that a business process test can receive and then pass to business components for use as input component values.
Business Process Test Status.
A status value that is automatically generated
based on the status values of all the business components in a business
process test.
Component Input Parameters.
Variable values that a business component can receive and use as the values for specific, parametrized steps in the component.
Component Output Parameters.
Values that a business component can return. These values can be viewed in the business process test results and can also be used as input for a component that is used later in the test.
Component Request.
A request for the creation of a new business component, when no existing component answers the needs of a business process test.
A scenario comprising a serial flow of business components, designed to test a specific business process of an application.
Business Process Test Run-Time Parameters.
Variable values that a business process test can receive and then pass to business components for use as input component values.
Business Process Test Status.
A status value that is automatically generated
based on the status values of all the business components in a business
process test.
Component Input Parameters.
Variable values that a business component can receive and use as the values for specific, parametrized steps in the component.
Component Output Parameters.
Values that a business component can return. These values can be viewed in the business process test results and can also be used as input for a component that is used later in the test.
Component Request.
A request for the creation of a new business component, when no existing component answers the needs of a business process test.
Business Component (or Component).
An easi... See Yuvraj's complete reply
Pre-Condition and Post-Condition. An easi... See Yuvraj's complete reply
The state of the application before the first step in a business component, and the state of the application after the last step in a business component. For example, the pre-condition for a component may state that all applications should be closed, or a specific application should be open to a specific screen or with a specific dialog box displayed. A post-condition may state that an application should be open to a particular screen, or be closed.
If you want the business component to allow iterations, the post-conditions
should specify that the application’s end state must match its state at the
beginning of the component. The pre-conditions and post-conditions
provide a guide when implementing the steps for the business component.











