IMPORTANT POINTS
2) To download files to your machine, you must log in with administrator privileges. For more information on the minimum permissions required to install client components, refer to the HP Quality Center Installation Guide.
3) If file downloads are prohibited through your browser, you can install these files from the HP Quality Center Client Side Setup Add-in on the HP Quality Center Add-in page. For more information on add-ins, refer to the HP Quality Center Installation Guide.
4) Quality Center
5) Resetting your password is unavailable in either of the following situations:
6) It is deactivated by the PASSWORD_RESET_DISABLE Site Configuration
7) Parameter or LDAP authentication is enabled.
8) Available Quality Center functionality may depend on how your site or project administrator has configured your Quality Center
9) Quality Center Editions: The availability of each module and feature depends on the Quality Center edition you have — Starter, Enterprise
10) You can navigate between the modules using shortcut keys. For a list of shortcut keys, see Appendix B, “Quality Center Keyboard Shortcuts.”
(Lets Read More)
(Lets Read More)
11) You must have the appropriate user permissions to clear history.
12) Quality Center
13) Columns displayed with the 
icon cannot be removed from the Visible Columns list.
icon cannot be removed from the Visible Columns list.14) You can save filter and sort information as a favorite view and then load it as needed. To save as a favorite view, choose Favorites > Add to Favorites.
15) If you select a field with a user name value, the Select Filter Condition dialog box displays a user list that enables you to sort users, search for users, group users by user groups, and select users from the list or from a group tree.
16) In the Requirements module, if you select the Req Parent field, the Select Filter Condition dialog box displays the requirements tree, sorted by requirement name. If you select a requirement from the requirements tree, its full path is displayed in the Condition box. Only requirements which are descendents of this requirement are displayed when you apply the filter.
17) Some items that appear in hierarchical lists contain sublists. These items are preceded by a folder icon. To choose an item from a sublist, doubleclick the folder and click the item.
18) When defining a condition for a user, you can specify the current user (select [CurrentUser]), or an entire user group (for example, [Developer]).
19) If you enter an item with more than one word, it must be enclosed in quotes. For example, to search for the test Login Boundary, in the Condition box, type the following: "login boundary"
20) If you want to enter only part of the item, use an asterisk (*). For example, to search for all tests with the word Login, in the Condition box, type the following: *login*. To search for all tests that begin with the words Insert New in the Condition box, type the following: "insert new*"
21) To specify an empty field, type the following: ""
22) To specify a non-empty field, type the following: not ""
23) Although the cross filter functionality is the same across all Quality Center
24) Quality Center
25) You can save filter and sort information as a favorite view and then load it as needed. To save as a favorite view, choose Favorites > Add to Favorites. For more information, see Chapter 6, “Working with Favorite Views”.
26) Quality Center
27) You cannot select a group header and perform Quality Center
28) If you group records by a field containing multiple values, the information in each value is grouped as its entire value. This value is the category for grouping.
29) The group by list displays only system and user-defined fields associated with a User List or Lookup List type field. For more information on field types, refer to the HP Quality Center Administrator Guide.
30) Quality Center
31) Version Control: Quality Center
32) Text search is only available if it has been enabled for the project. Contact your Quality Center
33) Quality Center
34) In Quality Center
35) You can also view a list of all alerts for a selected module by selecting the Show <entity> with alerts option in the Filter dialog box.
36) A follow up flag is specific to your user login name. Anyone else viewing the record does not see your follow up alert.
37) Working with favorite views is different from the description in this chapter for Document Generator. In the Document Generator, click the Add to Favorites button to add a new view and the Favorites button to organize your views.
38) By default, Quality Center
39) To maintain usability and data integrity, Quality Center
40) Quality Center
41) The dates for the cycles must be contained within the dates for the releases.
42) You can add user-defined fields and change the label of any of the fields in the Releases module.
43) You can use the Script Editor to restrict and dynamically change the fields and values in the Releases module.
44) You can also move a release folder or a release to a new location in the releases tree by dragging it.
45) Deleting a release folder, release, or cycle, also unassigns the associated requirements, test set folders, and defects.
46) Quality Center
47) Quality Center
48) To find a specific requirement by ReqID in the Requirements Tree view, choose Requirements > Go to Requirement, and type the requirement ID. To display the requirement ID, select the ReqID column using the Select Columns dialog box. You can only go to requirements that are in the current filter.
49) To find a specific requirement by ReqID in the Requirements Grid view, choose Requirements > Go to Requirement, and type the requirement ID. To display the requirement ID, select the ReqID column using the Select Columns dialog box.
50) To find a specific requirement by ReqID in the Requirement Details view, choose Requirements > Go to Requirement, and type the requirement ID. To display the requirement ID, select the ReqID column using the Select Columns dialog box. You can only go to requirements that are in the current filter.
51) You can access the Requirements menu bar from the Requirements module by pressing the shortcut key F9. Additionally, you can perform many other Quality Center
52) You can add user-defined fields and change the label of any of the fields in the Requirements module. You can also customize project lists.
53) You can use the Script Editor to restrict and dynamically change the fields and values in the Requirements module.
54) When you select a requirement column with a user name value (including user-defined fields), Quality Center
55) Quality Center
56) In addition to creating requirements directly in Quality Center , you can also import requirement data from Microsoft Word or Microsoft Excel to your Quality Center
57) Assigning a parent requirement to a cycle also assigns its child requirements to the same cycle.
58) If available, Text Search is a more powerful tool that enables you to search for keywords and variations of keywords.
59) By default, Quality Center
60) You can automatically send the email to a specific user type. This can be any requirement column with a user name value, including user-defined fields. Click the Send by Email arrow and choose an option. For example, choose Send by Email to Author to send the email to the user who wrote the requirement.
61) You cannot rename the root folder.
62) Test coverage, defect linkage, and risk-based quality management data for the requirement are not copied.
63) To copy a requirement with traceability, you must also copy its associated traced requirements.
64) The root folder cannot be copied within the same project.
65) You can also move a requirement to a new location in the requirements tree by dragging it.
66) If you stop the conversion process, any requirements already converted are not deleted from the test plan tree. You must delete them manually.
67) You can also add a requirement traceability link by dragging a requirement from the requirements tree to the appropriate grid.
68) Quality Center
69) The missing assessment link displays the requirements for which you did not determine a category or exclude explicitly from the analysis. Verify that there are no requirements that should be assigned a category. If you do not want to include a requirement in the analysis, then exclude it from the analysis explicitly.
70) To find a specific test by Test ID in the test plan tree, choose Tests > Go to Test, and type the test ID. To display the test ID, select the Test ID column using the Select Columns dialog box. You can only go to tests that are in the current filter.
71) You can access the Test Plan menu bar from the Test Plan module by pressing the shortcut key F9. Additionally, you can perform many other Quality Center
72) You can add user-defined fields and change the label of any of the fields in the Test Grid. You can also customize project lists.
73) You can use the Script Editor to restrict and dynamically change the fields and values in the Test Grid.
74) When you select a Test Grid column with a user name value,Quality Center
75) Developing and editing a test plan tree requires appropriate user permissions.
76) In addition to creating a test plan tree directly in Quality Center , you can also import test plan data from Microsoft Word or Microsoft Excel to your Quality Center
77) You can automatically create tests based directly on your requirements in the Requirements module.
78) If you have installed the QuickTest Professional Add-in on your machine, the Create New Test dialog box includes the Template box.
79) To set the QuickTest add-ins that Quality Center associates with a new QuickTest test, choose a template test that lists the appropriate add-ins. Alternatively, use the default template test provided on your Quality Center
80) To set a QuickTest Professional test as a template test, right-click the test in the test plan tree, and choose Mark as Template Test.
81) You can change the label of any of the test detail fields. You can also add user-defined fields to the test details.
82) By default, Quality Center
83) You can automatically send the email to a specific user type. This can be any test column with a user name value, including user-defined fields. Click the Send by Email arrow and choose an option. For example, choose Send Mail to Designer to send the email to the user who designed the test.
84) If Text Search is available, you can use it to search for tests in the test plan tree or Test Grid. Text search provides a more powerful search by allowing you to search for keywords and variations of keywords.
85) To copy tests across projects, both projects must use the same Quality Center
86) You must have project administrator permissions to create a custom sort.
87) You can also create coverage between test instances and requirements. To enable this feature use the ALLOW_REQ_COVERAGE_BY_TEST_INSTANCE parameter in Site Administration.
88) Requirements coverage is created automatically when you convert a requirement to a test. Therefore, even if you have not yet added requirements coverage, it may already exist.
89) You can also define requirements coverage by dragging a requirement in the requirements tree to the coverage grid. The requirement is added to the coverage grid without its child requirements.
90) Test coverage is created automatically when you generate a test from a requirement. Therefore, even if you have not yet added test coverage, it may already exist.
91) You can also define test coverage by dragging a test or a test folder from the Test Plan Tree tab to the coverage grid.
92) By default, coverage is available only for the following requirement types: Functional, Testing, and Undefined.
93) You can include a design step that calls another manual test.
94) You can copy steps from an existing test.
95) If you add an attachment to a design step, a copy of the attachment is made every time the test is run.
96) You can navigate between steps in the Design Step Editor using shortcut keys. Use ALT+HOME to access the first step, ALT+LEFT to access the previous step, ALT+RIGHT to access the next step, and ALT+END to access the last step.
97) If you apply formatting to a parameter name in a design step, you must apply the same formatting to the entire parameter name, including the <<< and >>> characters. For example, if you want to italicize the parameter <<<password>>>, you must italicize the entire string <<<password>>> and not just the word password.
98) The QUICKTEST_TEST test type is only available if you have installed the appropriate add-in from the HP Quality Center Add-ins page.
99) To run a system test, you must install the System Test Remote Agent Add-in and the HP Quality Center Connectivity Add-in on the machine where the test is to be run.
100) If required test fields were defined in Project Customization, the Required Test Fields dialog box opens. Select values for the required fields and click OK.
101) To use the Restart the computer option, you must enable auto login on your machine. Choose Start > Programs > HP Quality Center SystemTest Agent > SystemTest Agent (configuration). The Auto Restart Settings dialog box opens. By default, User Name and Domain are read-only. Type your password and click OK.
102) To select a different user name, reopen the Auto Restart Settings dialog box. User Name and Domain are no longer read-only. Modify the values and click OK.
103) When a Quality Center
104) To view the resource content, you must install the relevant add-in or extension.
105) You can also move a resource to a different location in the test resource tree by dragging it.
106) Fields and functionality related to release management and baselining are not available in the Test Lab module if you are working with the Starter Edition.
107) Right-click a test in the Execution Grid or Execution Flow, and choose Go to Test in Test Plan Tree to open the Test Plan module and highlight the selected test in the test plan tree.
108) You can access the Test Lab menu bar from the Test Lab module by pressing the shortcut key F9. Additionally, you can perform many other Quality Center
109) You can add user-defined fields and change the label of any of the fields in the Execution Grid. You can also customize project lists.
110) You can use the Script Editor to restrict and dynamically change the fields and values in the Execution Grid.
111) When you select an Execution Grid column with a user name value, Quality Center
112) Fields and functionality related to release management and baselining are not available when creating test sets with the Starter Edition.
113) You can also add tests by double-clicking or dragging a folder or test in the test plan tree to the Execution Grid or Execution Flow.
114) Only tests that match the current filter in the Requirements Tree tab are added.
115) You can also use the Run Events view in the Test Instance Properties dialog box to set the On Failure rules for a test in a test set.
116) To copy test sets or test set folders across projects, both projects must use the same Quality Center
117) When copying test sets or test set folders, test run information is not copied.
118) You can also drag the test sets between lists.
119) You can also add a condition directly in the Execution Flow. Click a test icon (not the test name) and drag the arrow to another test. By default, the condition is set to Finished. To change the condition, double-click the condition arrow and select Passed.
120) You can schedule the test run date and time by clicking the Add Time Dependency To Flow button, and linking the arrow from the icon to a test. Double-click the icon to set the time in the Time Dependency dialog box. The default time dependency is the Quality Center
121) You can conveniently read each test step and record the results using the compact view display of this dialog box. To open this display, click the Compact View button. To return to the steps grid, click the Back to Steps Grid button.
122) The Continue Manual Run command continues the last run of the selected test. If you want to resume running a previous run, click the Test Instance Properties button, select All Runs on the sidebar and choose the test run you want to resume. Click the Continue button.
123) You can only view the Execution Log if you selected Enable Log in the Automatic Runner dialog box before you executed the test.
124) If you specify a host group for remote test execution, Quality Center
125) When determining the order for running tests, Quality Center
126) You can also drag the tests up or down.
127) You can change the label of any of the fields in the Details tab. You can also add user-defined fields to the Details view.
128) When defining the WinRunnerCommandLine parameter, you must specify the path within quotes. For example: -ini “C:\program files\wrun.ini”
129) If you change the failure rules in the Run Events view, your changes are implemented in the next test run.
130) You can also set On Failure rules for a test by choosing Test Sets > Automation > On Failure and clicking the Settings per Test button.
131) If coverage between test instances and requirements is enabled with the ALLOW_REQ_COVERAGE_BY_TEST_INSTANCE parameter, click Linkage and Coverage on the sidebar.
132) Fields related to release management are not available in the Defects module if you are working with the Starter Edition.
133) To find a specific defect by Defect ID in the Defects Grid, choose Defects > Go To Defect.
134) You can access the Defects menu bar from the Defects module by pressing the shortcut key F9. Additionally, you can perform many other Quality Center
135) You can add user-defined fields and change the label of any of the fields in the Defects Grid. You can also customize project lists.
136) You can use the Script Editor to restrict and dynamically change the fields and values in the Defects Grid.
137) When you select a defects column with a user name value, Quality Center
138) You can link defects to other Quality Center
139) You can use the Workflow Script Editor to restrict and dynamically change the fields and values in the Defects module. You can also customize the fields for a specific user group.
140) Quality Center Premier Edition: You can share defects across multiple Quality Center
141) In addition to adding defects directly in Quality Center , you can also import defect data from Microsoft Excel to your Quality Center
142) If text search is available, you can use it to search for defects in the Defects Grid. Text search provides a more powerful search by allowing you to search for keywords and variations of keywords.
143) By default, Quality Center
144) You can automatically send the email to a specific user type. This can be any defect column with a user name value, including user-defined fields. Click the Send by Email arrow and choose an option. For example, choose Send Mail to Detected By to send the email to the user who detected the defect.
145) You can only remove direct links. Indirect links are removed automatically when the direct links are removed.
146) Quality Center
147) You can add user-defined fields and change the label of any of the fields in the Details tab. You can also customize project lists.
148) You can use the Script Editor to restrict and dynamically change the fields and values in the Libraries module.
149) The Libraries module functionality described in this chapter is available for Quality Center Enterprise Edition and Quality Center Premier Edition.
150) When the process is complete, view the log before refreshing the display. If you refresh the display after the baseline is created, the View Log button is no longer displayed, and you cannot view the log.
151) Quality Center
152) If coverage or traceability between two entities was deleted and then added again, those entities are considered modified.
153) If you are viewing information for a QuickTest test, clicking the Test Script button opens the test in a QuickTest viewer, enabling you to view the test or open the test in QuickTest.
154) You can also move a library folder or a library to a new location in the libraries tree by dragging it.
155) Changes made to Target Release and Target Cycle fields do not cause the fields to be marked as modified.
156) Version Control: When you compare two versions of an entity, not all sidebar buttons are displayed. The buttons available depend on the information stored under version control.
157) If you are comparing a QuickTest entity, the QTP Comparison button is displayed, enabling you to open the QuickTest Asset Comparison Tool.
158) For traceability and coverage, if a linked entity is marked as both Deleted and Added, or is displayed as Missing on both sides, this can indicate that the link between the entities was deleted and then added again.
159) The Libraries module functionality described in this chapter is only available for Quality Center Premier Edition.
160) You can also share defects across multiple Quality Center
161) When the process is complete, view the log before refreshing the display. If you refresh the display after the library is imported, the View Log button is no longer displayed, and you cannot view the log.
162) Quality Center
163) If coverage or traceability between two entities was deleted and then added again, those entities are considered modified.
164) You can change the maximum number of graphs that Quality Center
165) You cannot include a graph from a private analysis folder in a public dashboard page.
166) You can also move items or folders by dragging them to a different folder.
167) You can also create graphs from the Requirements, Test Plan, Test Lab, and Defects modules using the graph wizard.
168) You can also create a graph using the graph wizard.
169) You can change the maximum number of projects that Quality Center
170) To include all of a domain’s projects in the graph, select a domain in the Projects Tree, and add it to the grid. All the domain’s projects are listed individually in the grid.
171) The Requirements - Coverage Graph is a specific type of summary graph. If you select a different requirement field from the X-Axis list, a regular Requirements - Summary Graph is displayed.
172) You can create Excel reports that extract data by running SQL queries.
173) You can export grid data as a text file, Microsoft Excel spreadsheet, Microsoft Word document, or HTML document. You export data from the Requirements Grid, Test Grid, Execution Grid, or Defects Grid.
174) You can also create standard reports from the Requirements, Test Plan, Test Lab, and Defects modules.
175) The Quality Center Demo Project contains sample Excel reports. You can use the SQL queries and Visual Scripts in those reports as a basis for developing your own queries and scripts.
176) Users who belong to groups that have data-hiding filters, are able to access the restricted data through Excel reports. To overcome this, you can exclude user groups from performing Excel report tasks.
177) The @ and \ characters have a special meaning and are not read literally when running SQL queries on the project database. If you want these characters to be read literally, you should replace @ by \@ and \ by \\. For example, if you want the statement SELECT * FROM BUG WHERE BUG.BG_SUMMARY = ‘@parameter@’ to be run literally on the Quality Center
178) You cannot use parameters for SQL identifiers, such as a table name or a column name.
179) Parameter values cannot include an SQL statement.
180) If you delete a parameter that is in use in a report query, queries containing the parameter will not be valid.
181) For a parameter representing a text value, you must manually add single quotes (') around the parameter in the SQL pane. For example, if the SQL pane contains the phrase WHERE BUG.BG_DETECTED_BY = @name@, you must replace the text @name@ with '@name@'.
182) The Live Analysis graphs that you create are unique for your user login. Each project user can create Live Analysis graphs which will be visible only to that user but will not be visible to other users.
183) Live Analysis graphs only represent tests which are located directly below the selected test subject folder. They do not include tests located at a lower hierarchical level in child folders of the selected test subject folder.
184) The data displayed in the graph reflects the filters that you have set for the test plan tree.
185) Live Analysis graphs only represent test sets which are located directly below the selected test set folder. They do not include test sets located at a lower hierarchical level in child folders of the selected test set folder.
186) The data displayed in the graph reflects the filters that you have set for the test sets tree.
187) The Document Generator can only be run if Microsoft Word has been enabled to run macros. If you receive a security message while using the Document Generator, you must set the security level of Microsoft Word to medium or low. To do this, choose Tools > Macro > Security from the Word menu bar. On the Security Level tab, select the desired level of protection (Medium or Low), and click OK.
188) Microsoft Word is limited to nine header levels in the table of contents. If the requirements tree has more than nine hierarchical levels, these levels will not appear in the table of contents of the generated project document.
189) Microsoft Word is limited to nine header levels in the table of contents. If the test sets tree has more than nine hierarchical levels, these levels will not appear in the table of contents of the generated project document.
190) You can generate a preview project document that enables you to quickly see how the document will look, without all the detail included. To generate a preview project document, click the Preview button. Quality Center
191) You can also convert a manual test to a VAPI-XP test. In the Design Steps tab, click the Generate Script button and select VAPI-XP-TEST. Quality Center
192) If required test fields were defined in the Project Customization window, the Required Test Fields dialog box opens. Select values for the required fields, and click OK.
193) To create a VAPI-XP test script using ActiveState’s ActivePython or ActivePerl scripts, you must install the script language on your machine. From the Help menu in the Test Script tab, select ActivePython Home Page or ActivePerl Home Page, and follow the appropriate installation instructions.
194) Microsoft’s VBScript and JScript are usually installed with Internet Explorer. If they are not installed on your machine, select VBScript Home Page or JScript Home Page from the Help menu in the Test Script tab, and follow the appropriate installation instructions.
195) To run this virtual user in the Controller, you must install the latest version of the HP Quality Center Connectivity Add-in on your LoadRunner client machine. This add-in is available from the HP Quality Center Add-ins page.
196) You can only use a Java class that has a public constructor that does not take arguments.
197) Two SOAP client libraries are supported: Microsoft SOAP SDK and PocketSOAP. Note that even if you choose to work with PocketSOAP, you must install Microsoft SOAP SDK to parse Web services. If Microsoft SOAP SDK is not already installed on your machine, run the SoapToolkit30.exe file located in the Redist directory on your HP Quality Center DVD.
198) You can choose to add details and attachments to the VAPI-XP test you created, or define requirements coverage.
199) You can display the Test Script tab in a separate window by selecting View > Window Screen, or clicking the Window Screen button.
200) To view or edit the properties of the test script you created, choose Test > Properties.
201) For a description of each object definition, method, or property, select View > Output, and click the Help tab.
202) To run VAPI-XP tests remotely, you must install the HP Quality Center Client Side Setup Add-in and the HP Quality Center Connectivity Add-in on the host machine on which the tests are executed.
203) You cannot use the Integrated Debugger to debug PerlScript or PythonScript test scripts.
204) Quality Center Quality Center
205) Quality Center Enterprise Quality Center Quality Center
206) Quality Center Quality Center edition for mature Center of Excellence
207) Dashboard. Enables you to create graphs, reports, and Excel reports. You can also create dashboard pages, which enable you to view multiple graphs sideby- side.
No comments:
Post a Comment