HP Service Test Management

Transcription

1 HP Service Test Management Software Version: User s Guide Document Release Date: May 2010 Software Release Date: May 2010

2 Legal Notices Warranty The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice. Restricted Rights Legend Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR and , Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Third-Party Web Sites HP provides links to external third-party Web sites to help you find supplemental information. Site content and availability may change without notice. HP makes no representations or warranties whatsoever as to site content or availability. Copyright Notices Copyright Hewlett-Packard Development Company, L.P. Trademark Notices Java is a US trademark of Sun Microsystems, Inc. Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. Oracle is a registered US trademark of Oracle Corporation, Redwood City, California. UNIX is a registered trademark of The Open Group. 2

3 Documentation Updates The title page of this document contains the following identifying information: Software Version number, which indicates the software version. Document Release Date, which changes each time the document is updated. Software Release Date, which indicates the release date of this version of the software. To check for recent updates, or to verify that you are using the most recent edition of a document, go to: This site requires that you register for an HP Passport and sign-in. To register for an HP Passport ID, go to: Or click the New users - please register link on the HP Passport login page. You will also receive updated or new editions if you subscribe to the appropriate product support service. Contact your HP sales representative for details. 3

4 Support Visit the HP Software Support web site at: This web site provides contact information and details about the products, services, and support that HP Software offers. HP Software online support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by using the support web site to: Search for knowledge documents of interest Submit and track support cases and enhancement requests Download software patches Manage support contracts Look up HP support contacts Review information about available services Enter into discussions with other software customers Research and register for software training Most of the support areas require that you register as an HP Passport user and sign in. Many also require a support contract. To register for an HP Passport ID, go to: To find more information about access levels, go to: 4

5 Table of Contents Table of Contents Service Test Management User Guide...9 Chapter 1: Introduction to Service Test Management...15 Concepts...15 Service Test Management Overview...15 Chapter 2: Creating Application Components...19 Concepts...19 Creating Application Components Overview...19 Tasks...24 How to Define Components...24 Reference...26 Quality Center Direct Links...26 Application Components Module User Interface...27 Chapter 3: Web Services...55 Concepts...56 Defining Web Services Overview...56 Creating Tests in Service Test...59 Tasks...60 How to Define a Web Service...60 Reference...63 Web Service Specific User Interfaces

6 Table of Contents Chapter 4: Managing Components in Quality Center...77 Concepts...77 Managing Components...77 Tasks...80 How to Manage Components...80 Chapter 5: Groups...83 Concepts...83 Groups Overview...83 Tasks...85 How to Manage Component Groups...85 Reference...87 New Groups User Interface...87 Chapter 6: Generating Requirements and Tests...89 Concepts...89 Generating Requirements and Tests Overview...89 Tasks...94 How to Generate Requirements and Tests...94 Reference...95 Generate Requirements and Tests User Interface...95 Chapter 7: Determining Test Coverage Concepts Coverage Overview Rule Violations Aspect Coverage Requirements Coverage Operations Coverage Tests Coverage Defects Coverage Tasks How to Check the Testing Status

7 Table of Contents Reference Testing Status Tab Chapter 8: Linking Components and Requirements Concepts Linking Components Overview Tasks How to Link Components to Requirements and Tests Reference Linking Component User Interface Chapter 9: Customizing Service Test Management Concepts Customization Overview Tasks How to Customize a Project Reference Project Customization User Interface Chapter 10: Change Analysis Concepts Change Analysis Overview Tasks How to Perform Change Analysis Reference Changes Tab Chapter 11: Reports and Graphs Concepts Service Test Management Reports and Graphs Overview Tasks How to Create and Generate Reports How to Generate Graphs

8 Table of Contents Chapter 12: Custom Script Generators Concepts Creating Custom Script Generator Overview Tasks Implement and Register a Custom Generator Reference Script Generator API Reference Test Generation Flow Index

9 Service Test Management User Guide Welcome to HP Service Test Management, a complete solution for managing the process of testing application components and their changes in serviceoriented architecture (SOA) and other GUI-less systems. Service Test Management integrates with HP Quality Center to provide a Web-based solution for testing the quality and performance of all types of application components throughout the entire application development life cycle. Note: This guide explains how to manage tests in conjunction with Quality Center. For additional information on using Quality Center, refer to the HP Quality Center User s Guide. How This Guide Is Organized This guide contains the following chapters: Chapter 1 Chapter 2 Introduction to Service Test Management Provides an introduction to the Service Test Management model and its integration with Quality Center. Creating Application Components Describes how to create a Components tree and define components and component groups. 9

10 Welcome to This Guide Chapter 3 Chapter 4 Chapter 5 Chapter 6 Chapter 7 Chapter 8 Chapter 9 Chapter 10 Web Services Describes how to work with Web Service type application components and the unique features available for Web Services. Managing Components in Quality Center Describes how to view and modify component details, definitions, and operation data, generate Excel reports, remove and restore components, and define component dependencies. Groups Describes how to create component groups and associate application components to them. Generating Requirements and Tests Describes how to use the Requirement and Test Generation wizard to automatically generate requirements and tests and how to create empty tests. Determining Test Coverage Shows the testing status with graphical displays of test, requirement, and defect coverage. Linking Components and Requirements Describes how to link components to requirements and tests. Customizing Service Test Management Describes how to customize the Application Components module, user group permissions, module access, and project entities for components and groups. Change Analysis Describes how to identify changes in components and analyze their impact on related assets in Quality Center. Also describes how to create and run test sets to test the impact of these changes. 10

11 Welcome to This Guide Chapter 11 Chapter 12 Reports and Graphs Describes how to generate graphs and Excel reports to represent your components and their coverage. Custom Script Generators Extends the capabilities of the Service Test Management Requirement and Test Generation Wizard through an external script generator. Documentation Library The Documentation Library is an online help system that describes how to use the application. When using Service Test Management in the Quality Center application, you can access the Quality Center Documentation Library or the Service Test Management Documentation Library. Quality Center Documentation Library. When working in any module other than the Application Components module, you can access the Quality Center Documentation Library in the following ways: Click Documentation Library in the Help menu to open the Quality Center Documentation Library home page. The home page provides links to the Quality Center guides and references. Click Help on this page in the Help menu to open the Documentation Library to the topic that describes the current page. Service Test Management Documentation Library. When working in the Application Components module, you can access the Service Test Management Documentation Library. Select Help > Help on this page to open the Help window. Click the Search and Navigate button in the top left corner and then go to the Home link. The Service Test Management Documentation Library home page provides links to the Testing guides. The Documentation Library is best viewed from a browser with Java support. If you do not have Java support on your browser, download the Sun Java plug in from the Sun Java Web site ( Note that if Java support is not available, the Documentation Library automatically opens using the JavaScript implementation. The JavaScript implementation provides the same basic functionality as the Java implementation, however does not allow use of the Favorites tab within the navigation pane. 11

12 Welcome to This Guide Service Test Management Documentation Library Guides The Service Test Management Documentation Library consists of the following guides, available online, in PDF format, or both. PDFs can be read and printed using Adobe Reader which can be downloaded from the Adobe Web site ( Readme provides last-minute news and information about Service Test Management. HP Service Test Management User s Guide explains how to use Service Test Management to facilitate the complete application delivery life cycle for application components. (Available online and in PDF format.) HP Service Test Management Installation Guide explains how to install Service Test Management on a server machine as an extension to Quality Center. (Available in PDF format only.) HP Service Test User s Guide explains how to use Service Test to create scripts for SOA environments. (Available in PDF format only.) Quality Center Documentation Library Guides The Quality Center Documentation Library consists of the following guides and references, available online, in PDF format, or both. PDFs can be read and printed using Adobe Reader which can be downloaded from the Adobe Web site ( Getting Started explains how to use the Documentation Library and how it is organized. (Available online.) What s New? describes the newest features in the latest versions of Quality Center. (Available online and in PDF format.) You can also access the What s New? from the Quality Center Help menu. In addition, you can choose Help > Product Feature Movies to view short movies which demonstrate the main product features. Readme provides last-minute news and information about Quality Center. 12

13 Welcome to This Guide Quality Center Guides HP Quality Center User s Guide explains how to use Quality Center to organize and execute all phases of the testing process. It describes how to define requirements, plan tests, run tests, and track defects. (Available online and in PDF format.) HP Quality Center Administrator s Guide explains how to create and maintain projects using Site Administration, and how to customize projects using Project Customization. (Available online and in PDF format.) HP Quality Center Tutorial is a self-paced guide teaching you how to use Quality Center to manage the software testing process. (Available in PDF format.) HP Quality Center Installation Guide explains how to install Quality Center on a server machine in a cluster environment or as a stand-alone application. (Available in PDF format.) Business Process Testing Guides HP Business Process Testing User s Guide explains how to use Business Process Testing to create business process tests. (Available online and in PDF format.) HP Business Process Testing Tutorial provides a self-paced guide that teaches you the basics of Business Process Testing in the Quality Center application. (Available in PDF format.) API References HP Quality Center Database Reference provides a complete online reference for the project database tables and fields. (Available online.) HP Quality Center Open Test Architecture API Reference provides a complete online reference for the Quality Center COM-based API. You can use the Quality Center open test architecture to integrate your own configuration management, defect tracking, and home-grown testing tools with a Quality Center project. (Available online.) 13

14 Welcome to This Guide HP Quality Center Site Administration API Reference provides a complete online reference for the Site Administration COM-based API. You can use the Site Administration API to enable your application to organize, manage, and maintain Quality Center users, projects, domains, connections, and site configuration parameters. (Available online.) HP Quality Center Custom Test Type Guide provides a complete online guide on how to create your own testing tool and integrate it into the Quality Center environment. (Available online.) 14

15 1 Introduction to Service Test Management This chapter includes: Concepts Service Test Management Overview on page 15 Concepts Service Test Management Overview When developing an application comprised of many components, it is essential that you organize the components and keep track of their tested status. Service Test Management, in conjunction with other HP testing tools, enables you to test and organize the application components. You can ensure that they perform their intended function and that they are able to scale to the needs of the applications that use them. Service Test Management s Application Components module in Quality Center, enables you to centrally manage your assets. Using this module, you can define and store application components in Quality Center s repository. After you define components, you can generate a set of requirements and tests to validate the functionality, interoperability, security, boundaries, standards compliance, and performance of the components in your application. You can then run tests and view results in the Test Plan and Test Lab modules. Service Test Management also provides change analysis that highlights changes in the components and evaluates the impact that they may have. Based on these changes, Service Test Management can automatically generate the test sets that are required to validate the component. 15

16 Chapter 1 Introduction to Service Test Management This section also includes: "The Service Test Management Integrated Solution" on page 16 "The Advantages of Service Test Management" on page 16 The Service Test Management Integrated Solution Service Test Management is an integrated solution that allows you to manage the quality of your application components, such as.net, Java, or Web Service applications. It integrates the following HP products: HP Quality Center. Enables you to centrally manage SOA assets from the Application Components module. You can define, import, and store services in Quality Center, and generate the necessary requirements and tests. HP Service Test. Enables you to automatically create scripts for testing your SOA environment. You can edit tests generated using Service Test Management, run tests, view results, reuse components and services, and create an emulation of a Web service for testing purposes. HP LoadRunner/HP Performance Center. Enable you to perform load testing on services, and monitor and predict their performance under load. HP LoadRunner Analysis allows you to drill down to determine the specific source of bottlenecks and generate actionable reports. HP Systinet Registry. Enables you to import Web services from the HP Systinet Registry (supports Systinet 2 with Service Pack 1 or later). The Advantages of Service Test Management Service Test Management provides the following features: A complete testing process that includes functional testing and performance testing. Automatically generated requirements and tests that validate the functionality (positive and negative), interoperability, standards compliance, security, and performance of an application component or service. Reusable tests that can be combined and extended across teams, providing easier transfer of knowledge and test data. 16

17 Chapter 1 Introduction to Service Test Management Change management and change impact testing that highlights changes in application components and environments, and evaluates the impact that changes may have on different applications. 17

18 Chapter 1 Introduction to Service Test Management 18

19 2 Creating Application Components This chapter includes: Concepts Creating Application Components Overview on page 19 Tasks How to Define Components on page 24 Reference Quality Center Direct Links on page 26 Application Components Module User Interface on page 27 Concepts Creating Application Components Overview You add entities to the Application Components tree by manually adding a new components. After you add a component, you can describe it through a contract. Once you define application components, you can link them to requirements. This linkage allows you to connect the component to other Quality Center entities, such as tests, test sets, and defects. 19

20 Chapter 2 Creating Application Components This section also includes: "The Application Component Tree Hierarchy" on page 23 Application Component Design Stage 1 - Prepare to collaborate The QA (Quality Assurance) and Dev (Software Development) managers prepare to collaborate in describing the components or the AUT (Application Under Test). QA will use that information to track changes, execute tests, and report on the quality of the product. Stage 2 - Set a methodology Set a methodology to describe the application: What are the application areas in the AUT, to be translated into folders in the component hierarchy? What will constitute a component. For example, only high-level interfaces may be considered components, or its centrality or importance in the application? What component types to define? This could be based on technology, usage, and so forth. What fields (and possibly UDF) to associate with the component types? Stage 3 - Quality policies Determine quality policies to be implemented through rules and testing aspects. These policies are necessary to insure that components are tested based with the correct data. Stage 4 - Create a project and customize it Create an Service Test Management project or enable the extension on an existing Quality Center project. Open Customization and define component types and their fields, as well as UDFs for component and changes. Define the necessary rules and testing aspects. 20

21 Chapter 2 Creating Application Components Stage 5 - Create the application components Open the Application Components module and create a folder structure to represent the application areas decided on above. Create component groups for cross-area functionality or deployment. If possible, define high-level components based on the planned strategy. If not possible, the developers can define them at a later time. The project is ready for the QA and the software development teams may begin using it. Stage 6 - Report changes to QA Developers use the IDE add-on to report changes back to QA. Developers implement requirements and fix defects. They can create new components or application areas as required. These actions will be reported to Service Test Management and assigned to an existing or new application component. They can also be linked to the work item such as a requirement or defect, if one exists. When making changes, developers describe their risk to QA, to assist them in their testing. Developers may report a change while still in the process of enacting the change. This allows QA to prepare for testing the change. Optionally, the developers can wait until the change has been completed before reporting it to QA. Stage 7 - QA processes changes Before changes are gathered, QA can begin reviewing the application components and assign requirements and tests. QA engineers can create new component groups to facilitate the management of the components. After changes are generated, Service Test Management marks the changed components with alert icons and lists them in the Changes tab. QA uses the information in the Interaction tab to create tests for the changed components, using the change description to verify the coverage. During this process, QA can set the following fields: 21

22 Chapter 2 Creating Application Components Change status to In test. Assigned to developer to determine the developer regarding an aspect of the component s functionality. Created by in the Change tab, to determine the developer who is responsible for updating the component s functionality. QA can see the changes for one or more components: Select a component to view the changes specific to that component, and review its Changes tab, Select a group or folder to view an aggregated list of changes in the Changes tab. The Changes grid provides the context of the change which can assist QA in understanding the issue. Stage 8 - Run tests QA executes tests on the AUT in the testing environment. Based on the test results, they can set the status to verified or keep the In test status. if a change was tested it is considered verified, even if causes defects in the component. Stage 9 - Reporting QA uses the graphs and reporting capabilities to summarize the status of the components of the AUT and the changes. They send this report back to the development team. The developers can decide how to act upon QA s recommendations. The on-going reporting should show a trend of more changes being verified in less time, and a downward trend in the number of defects on the components. In conclusion, the Application Components module allows QA and the developers to verify the quality of the AUT in a comprehensive fashion. 22

23 Chapter 2 Creating Application Components The Application Component Tree Hierarchy Service Test Management provides you with tools to define components and modify their details. You organize your application components in a graphical hierarchy. At the top level of the tree is the Application Components root folder, which contains sub folders. You can create custom folders that represent the structure of components in your application. For example, you might create separate folders to represent different types of users. You can reorganize related entities in folders and subfolders, and drag and drop folders or subfolders to other locations in the tree. The Obsolete folder contains components that were removed, but are still being used by tests stored in Quality Center. For details about the Obsolete folder, see "Remove and restore components - optional" on page 82. You cannot rename, move, or delete the Application Components folder or the Obsolete folder. Component Dependencies Component dependency defines a relationship between two or more components. As the operations of these linked components change, you can detect changes and track their impact on the linked components. You can define the dependencies using Service Test Management s Modeling tab. The Modeling tab displays a diagram of the component dependencies. An arrow indicates a dependency: An arrowhead pointing to the base component, indicates a Dependency From another component the added component impacts the base component. An arrowhead pointing away from the base component indicates a Dependency To another component -the added component is impacted by the base component. 23

24 Chapter 2 Creating Application Components You select components and add them to a modeling diagram. In the following example, the LoginService component is dependent on AddrBook and DataType. The Echo and Calc components are dependent on LoginService. Although you drag in the dependent components, the dependencies are actually per operation. For details, see "Define dependencies - optional" on page 25. Tasks How to Define Components This task describes how to set up your components in Service Test Managements. After you set them up, you can test them and check their functionality and compliance. "Create a folder - optional" on page 25 "Create a new component" on page 25 "Specify a contract" on page 25 24

25 Chapter 2 Creating Application Components Create a folder - optional Open the New Folder dialog box and add new folders and subfolders to create a tree hierarchy for your components. For details, see the "New Folder Dialog Box" on page 43. You can create folders at any time and drag or copy components from folder to folder. Create a new component Select Components > New > New Component to create an new component and provide whatever details are available to you. For details, see the "New Application Component Dialog Box" on page 43. Specify a contract In the New Application Component Dialog Box, click the Interaction link in the left pane. Click Browse to locate a contract file. For details, see the "New Application Component Dialog Box" on page 43. Define dependencies - optional 1 Select the Modeling tab. For a description, see the "Modeling Tab" on page Click the Select Entities button to open the Components list in the right pane. Expand the folders and select a component. 3 Click the arrow to open the transfer menu. a To add a component that is dependent on the base component, click Add Component Dependency (Dependency To). b To add a component upon which the base component is dependent, click Add Component Dependency (Dependency From). The Dependency Details dialog box opens. Select the operation that affects the dependency. If you do not know which operation to select, specify all of them. For details, see the "Dependency Details Dialog Box" on page 42 25

26 Chapter 2 Creating Application Components Reference Quality Center Direct Links You can use direct links to access specific views and components. You enter the direct link into your browser to access the desired view. You can save these links for future reference, or send them to others by so that they may access a specific view or component. When working with Systinet, you can use a direct link to access the import screen, enabling you to locate services quickly. The direct links use the following format: td://<project_name>.<domain>.<server:port>/qcbin/ The following table describes the shortcut syntax to be added to the above string. Italic text indicates optional parameters. View Systinet Import 100?Action=ImportSystinet&SystinetID= [SYSTINET_KEY]&Environment=<ENVIRONMENT>&Uui d=<uuid> 26

27 Chapter 2 Creating Application Components View Component Component Group StmModule ? EntityType=IStmService&EntityID=<component id>&view=<service tab type> <component tab type> values: Changes Modeling TestingStatus AspectStatus OperationStatus StatusDashboard StmModule ? EntityType=IStmGroup&EntityID=<group id>&view=<group tab type> <group tab type> values: Modeling TestingStatus AspectStatus StatusDashboard Application Components Module User Interface Service Test Management provides a user interface to organize your application components and customize the Quality Center project hosting them. This section includes (in alphabetical order): Alerts Dialog Box on page 28 Details Tab on page 29 Interaction Tab on page 32 Find Dialog Box on page 35 Modeling Tab on page 36 27

28 Chapter 2 Creating Application Components Dependency Details Dialog Box on page 42 New Folder Dialog Box on page 43 New Application Component Dialog Box on page 43 Application Components Module Icons on page 47 Application Components Module Window on page 48 Application Components Module Menus and Buttons on page 50 Alerts Dialog Box Displays all alerts and rule violations associated with the selected component and enables you to resolve or disregard them. To access Click the red exclamation point,adjacent to the component name in the Application Components tree. Relevant tasks "Evaluate the tests" on page 160 See also "Change Analysis" on page 155 The following elements are included (unlabeled GUI elements are shown in angle brackets): UI Elements (A-Z) Removes the current rule violation in the Rule Violations pane: Note: When removing a rule violation, Service Test Management disregards it it does not delete it. Removes all rule violations in the Rule Violations pane: Note: When removing a rule violations, Service Test Management disregards it it does not delete it. 28

29 Chapter 2 Creating Application Components UI Elements (A-Z) For change alerts, this button opens the Changes tab listing all of the changes. Use the Create Test Set utility to resolve the changes. For details, see the "Create Change Impact Test Set Wizard" on page 167 For rule violations, this button opens the Create Requirements Test wizard in order to resolve the violation. For details, see the "Generate Requirements and Tests Wizard" on page 97. Alerts for <component name> Changes Rule Violations A link to the component in the Application Components tree. An expandable/collapsible list of all change alerts specific to the selected component. Indicates a change to the component file since its last import or update. An expandable/collapsible list of all rule violations for the selected component. A common rule violation is missing coverage for a testing aspect. Details Tab Displays and enables you to edit a component s details. To access Important information Select Application Components module, highlight a folder, component, or group, and click the Details tab. The Details tab fields differ, depending on the entity you select: folder, component, or group, and the component type. Relevant tasks "Manage component details - optional" on page 80 See also "Application Component Details Pane" on page 39 29

30 Chapter 2 Creating Application Components Details Tab for Components The following elements are displayed when you select a component in the Component tree. GUI Element (A-Z) <user-defined> Assigned to Dev Assigned to QA Component ID Component Name Component Type Created By Creation Date Development Status Keep up to date Last updated Visibility User-defined fields defined in customization. The name of the developer to whom the component implementation is assigned. The name of the QA engineer responsible for validating the component. A read-only ID assigned to the component. The native component name as provided by the user. The type of component. The built-in components are General, Web Service, and JMS. If you defined a new component type, it will be displayed. The name with which you logged in. You can edit this field and specify a different name. This is useful for sorting the components in reports. The date the component was created in the Component tree. The development status of the component: Development, Maintenance, QA ready, or Stable. Keep the component up to date: Y or N. When enabled, instructs Service Test Management to update the component from its source each time you select it in the Application Component s tree. The last time the component was updated. The component s visibility level Internal or External. 30

31 Chapter 2 Creating Application Components Details Tab for Groups The following elements are displayed when you select a group in the Components tree. UI Elements (A-Z) Assigned To Created By Creation Date Name The name of the user to whom the group implementation is assigned. The name with which you logged in. You can edit this field and specify a different name. This is useful for sorting the groups in reports. The date the group was created in the Components tree. A description of the group. The name of the group. Details Tab for Folders The following elements are displayed when you select a folder in the Components tree: UI Elements (A-Z) Folder ID Name A read-only ID assigned to the folder. The folder name in the Components tree. A meaningful description of the folder. 31

32 Chapter 2 Creating Application Components Interaction Tab Displays and enables you to edit a component s contract information. To access Important information Select Application Components module, highlight a component, and click the Interaction tab. Only available when selecting a component in the tree. The information differs depending on the component type: Relevant tasks "Manage component details - optional" on page 80 See also "Application Component Details Pane" on page

33 Chapter 2 Creating Application Components The Interaction tab contains the following information: UI Elements (A-Z) Contract Details Contract File. The location of the contract file defining the application component.. Opens the Open File or Import Service dialog box visible for new components whose contracts have not yet been defined.. Opens the Open File dialog box. For Web Services, it opens the or Import Service dialog box visible for components whose contracts have already been defined. For more details, see the relevant section: "Import Service Dialog Box" on page 68. "Select Service from Systinet Dialog Box" on page 63 "Select Service from UDDI Dialog Box" on page 64 Contract Details - Web Services Import type. Contract import method: File, URL, Systinet, and UDDI. Toolkit. The toolkit associated with the Web service. You set this in the Customization settings, and it is read-only. Service Address. The service deployment location, to which service requests are sent. By default, Quality Center displays the endpoint address specified in the WSDL file. Override Address. Enables you to enter an alternate endpoint for the service in the Service Address box. 33

34 Chapter 2 Creating Application Components UI Elements (A-Z) Contract Details - JMS Interaction Fields JMS connection factory. The JNDI name of the JMS connection factory. This setting is unique per test. JMS destination. The name of the JMS destination either the queue or topic name. JMS provider. The JMS service provider: Apache ActiveMQ, JBoss Messaging from JBoss, Open Message Queue, Websphere MQ from IBM, and so forth. JNDI initial context factory. A The fully qualified class name of the factory class that will create an initial context. Provides a list of context factories and allows manual entries. JNDI provider URL. The URL of the service provider. For example: Websphere - iiop://myserver:myport Messaging Model. The type of JMS message Point to point, or Publish and subscribe. The fields you designated in the Customization for the component type. For details, see "Component Types Tab" on page 147. The common fields are: JMS Request Queue JMS Response Queue JMS Transport (Y or N) WSDL Native Name Operations. Refresh. Reloads the list of operations.. Web Service Call. Opens the Run <operation-name> dialog box to send a test request to the server. For details, see the "Manual Runner Service Testing Tab" on page 71. Note: This option is only available if Service Test or the Service Test add-in is installed on the machine. <Operation list>. A list of the available operations for the application component. Parameters A list of the parameters for the selected operation. The list provides the parameter name, data type, and an indication of whether it is an input or output parameter. 34

35 Chapter 2 Creating Application Components Interaction Tab for UDDI and Systinet Services For services imported through UDDI or Systinet servers, the Interaction tab shows several additional read-only fields: UI Elements (A-Z) Systinet Server UDDI Server UDDI/Systinet Key The URL address and port of the Systinet server from which the service definition is imported. The URL address and version of the UDDI server from which the service definition is imported A unique identifier of the service on the UDDI or Systinet server, used to locate the service definition when updating the service Find Dialog Box Enables you to search for a component, group, or folder within the Components tree. To access Edit > Find Relevant tasks "Find folders and components - optional" on page 81 See also "Manage component details - optional" on page 80 The following elements are included (unlabeled GUI elements are shown in angle brackets): UI Elements (A-Z) Searches for the next occurrence of the text, based on the previously used settings. Expands the Find dialog box to show the match criteria. Collapses the Find dialog box to hide the match criteria. 35

36 Chapter 2 Creating Application Components UI Elements (A-Z) Entity Type Find In Field Match Criteria Value to Find Type of entity in which to perform the search: Folder, Component, or Group. The field within the Details tab upon which to perform the search. The available fields differ for a folder, group, or component. For information about the fields in the Details tab, see "Details Tab" on page 29. Advanced match criteria: Case Sensitive. Performs a case sensitive search. Exact Match. Looks for the exact string not a partial string. Use Wildcard- Applies wildcard rules to the search text. The text to find in the component, group, or folder. Modeling Tab This tab displays component dependencies or component/group relationships in a visual representation. If you select a folder, it shows all associations and dependencies in groups and components beneath that folder. This tab enables you to associate components with one another and assign them to component groups. To access Important information Choose the Application Components module, select a component or group, and click the Modeling tab. If you select a component, the visual design shows the component dependencies. Relevant tasks "Define dependencies - optional" on page 25 "Add a component to a group" on page 86 See also "Component Dependencies" on page 23 36

37 Chapter 2 Creating Application Components User interface elements are described below (unlabeled GUI elements are shown in angle brackets): UI Elements (A-Z) Opens the Components tree in the right pane to add more component or groups to the modeling window. For information about the tree hierarchy, see the "Components Tree" on page 38. Delete. Removes the selected entity from the visual area. You cannot delete the base component or group that is selected in the left pane s Component tree. Refresh. Redraws the visual diagram in the visual area. Arrange layout. Arranges the layout of all entities in the current modeling window, in a symmetric fashion. Zoom in. Enlarges the entities in the current drawing. Zoom out. Reduces the size of the entities in the current drawing. <modeling window> Application Component/Group Details A visual area showing component dependencies or component/group relationships in a graphical representation. Details of the component or group selected in the modeling window. For component details, see "Application Component Details Pane" on page 39 For group details, see "Group Details" on page 41 37

38 Chapter 2 Creating Application Components Components Tree The following elements are included (unlabeled GUI elements are shown in angle brackets): UI Elements (A-Z) Add. Opens a dropdown list with the following options: Associate. Associates the selected component with a group. Add Dependency (Dependency To) Add Dependency (Dependency From) Note: The Associate option is enabled when you select a group in the right pane. The Add Dependency options are enabled when you select a component in the right pane. For details about dependencies, see the "Dependency Details Dialog Box" on page 42 Refresh. Refreshes the Components list. Set/Clear Filter. Opens a dropdown list with the following options: Set Filter / Sort. Opens the Set Filter/Sort dialog box allowing you to filter and sort the components. Clear Filter / Sort. Clears all filters and sorting settings and displays all components and groups. Exit. Closes the Components tree pane To reopen this view, click the Select the Modeling tab button in <Components List> An expandable list of all components by folder and group. Tip: If a filter is active, there could be hidden components. To see all components, click Clear Filter. 38

39 Chapter 2 Creating Application Components Application Component Details Pane The following elements are displayed in the bottom pane of the Modeling tab, when you select a component in the modeling drawing. UI Elements (A-Z) <user-defined> Assigned to Dev Assigned to QA Component Folder Path Component ID Component Name Component Type Contract file Created By Creation Date Deleted On Development Status Has Changed Import type User-defined fields defined in customization. The name of the developer to whom the component implementation is assigned. The name of the QA engineer responsible for validating the component. The folder path of the component in the main Components tree. A read-only ID assigned to the component. The native component name in the definition files. The type of component: General, Web Service, and JMS. If you defined a new component type in Customization, it will be displayed. The path or URL of the component s contract file. The name with which you logged in. You can edit this field and specify a different name. This is useful for sorting the components in reports. The date the entity was created in the Application Components tree. The date the component was deleted. This applies primarily to components in the Obsolete folder. The development status of the component: Development, Maintenance, QA ready, or Stable. Y or N. Yes indicates that the definition files (for example, WSDL), changed since the last update. Contract import method: File, URL, Systinet, or UDDI. 39

40 Chapter 2 Creating Application Components UI Elements (A-Z) Keep up to date Last Updated Location Original Location Override Address Port Type Service Address Systinet ID Systinet Key Systinet Server Systinet Server Port Systinet Version Toolkit UDDI Server UDDI Service Key Y or N. When enabled, updates the contract from its source each time you select the component in the Application Component s tree. The last time the WSDL was updated. The location of the component s source file (such as WSDL) that is displayed by default when defining the component. To override the default, select Override Address. The original location of the WSDL This is relevant when you choose Override address and change the endpoint. Enables you to enter an alternate endpoint for the service in the Service Address box (Web Services only). The port type of the proxy server. The service deployment location, to which requests are sent. By default, Quality Center displays the endpoint address specified in the WSDL file. (For Web Service type components only) The Systinet ID for the imported Web services. The Systinet key for the imported Web services. The URL address of the Systinet server from which the service definition is imported. The port of the Systinet server machine. The version of the Systinet server hosting the service. The toolkit associated with a Web service. You set this in the Customization settings, and it is read-only. The URL address and version of the UDDI server from which the service definition is imported. A unique identifier of the service on the UDDI server, used to locate the service definition when updating the service. UDDI Version The version of the UDDI registry: 2 or 3. 40

41 Chapter 2 Creating Application Components UI Elements (A-Z) Update Time Visibility WSDL native name The time the WSDL was updated. The visibility of the application component: Internal or External. The name of the Web Service as determined from the WSDL file. (For Web Service type components only) Group Details The following elements are displayed in the bottom pane of the Modeling tab, when you select a group in the modeling drawing. UI Elements (A-Z) Assigned To Created By Creation Date Name The name of the user to whom the group implementation is assigned. The name with which you logged in. You can edit this field and specify a different name. This is useful for sorting the groups in reports. The date the group was created in the Components tree. The name of the group. 41

42 Chapter 2 Creating Application Components Dependency Details Dialog Box Enables you to set the dependencies between components or modify existing ones. To access Important information In Modeling tab For a new dependency: Click Select to open the list of components in the right pane. Select a component and click the Add button to create a new dependency. The dialog box opens automatically. For an existing dependency: Click in the Component Dependency Details grid, select a dependency and click the Edit button. An arrow indicates a dependency: An arrow pointing to the base component indicates a Dependency From another component the added component impacts the base component. An arrow pointing away from the base component indicates a Dependency To another component -the added component is impacted by the base component. Relevant tasks "Define dependencies - optional" on page 25 The following elements are included (unlabeled GUI elements are shown in angle brackets): UI Elements (A-Z) <component_name> Operation Calls to <component_name> Operation An operation with which to create a dependency, or All if you are unsure. The operation through which to create the dependency. Use Any if you are unsure. 42

43 Chapter 2 Creating Application Components New Folder Dialog Box This dialog box page enables you to create a new folder in the Components tree. To access Important information Use one of the following: Click the New Folder button. Select Components > New > New Folder. A folder name cannot include any of the following characters: \ / * Relevant tasks "Create a folder - optional" on page 25 User interface elements are described below: UI Elements (A-Z) Folder Name OK A name for the new folder, beneath the folder selected in the Components tree. You can create several levels of sub-folders. Tip: Add a description to the folder in the Details tab. Adds the new folder to the Components tree. New Application Component Dialog Box Enables you to create a new component. To access Use one of the following: Select Components > New > New Component Select New > New Component from the shortcut menu Relevant tasks "Create a new component" on page 25 43

44 Chapter 2 Creating Application Components The following elements are included: UI Elements (A-Z) Clear All. Clears all the fields so that you can redefine the component. Details pane. The component s properties. The displayed fields differ based on the component type and the fields enabled in the customization section. For details, see the "Component Types Tab" on page 147. Some common fields are: Assigned to Dev Assigned to QA Created by Development Status: Development, Maintenance, QA ready, or Stable. Last Updated Visibly: External or Internal tab. An editable area for a description of the component. Comments tab. An editable area for adding remarks. 44

45 Chapter 2 Creating Application Components UI Elements (A-Z) Interaction pane. Contract information. The displayed fields differ based on the component type and the fields enabled in the customization section. To display a field in this section, select it in the customization s Interaction Field column. For details, see the "Component Types Tab" on page 147. Contract File. The location of the contract. For non-web Service components, opens the Open File dialog box. For Web Services, opens the Import Service dialog box. For details, see "Import Service Dialog Box" on page 68. Operations. A list of the component s operations. Parameters. The component s parameters sorted by the following columns: In/Out, Parameter Name, and Type (data type). for JMS types JMS connection factory. The JNDI name of the JMS connection factory. This setting is unique per test. JMS Destination. The name of the JMS destination either the queue or topic name. JMS Provider. The JMS service provider: Apache ActiveMQ, JBoss Messaging from JBoss, Open Message Queue, Websphere MQ from IBM, and so forth. JJNDI initial context factory. The fully qualified class name of the factory class that will create an initial context. Provides a list of context factories and allows manual entries. JNDI provider URL. The URL of the service provider. For example: Websphere - iiop://myserver:myport Messaging Model. The type of JMS message Point to point, or Publish and subscribe. Attachments pane. Allows you to attach a file to the component. For details, see the Quality Center User Guide. 45

46 Chapter 2 Creating Application Components UI Elements (A-Z) Submit. Creates the component whose details you specified. Close. Closes the dialog box and cancels any changes you made to the existing screen. Component Name Component Type A name for the component. The type of component to create: General, Web Service, or JMS. If you created a custom type component in Customization, it also appears in the dropdown list. 46