Getting Started with Code Coverage/Eclipse

Transcription

1 Getting Started with Code Coverage/Eclipse Code Coverage/Eclipse is the modernized GUI for Compuware s Xpediter/Code Coverage product. With it, users can create reports detailing testing efficiency and risk metrics for mainframe COBOL, PL/I, and High Level Assembler programs. Related Topics Features and Capabilities of Code Coverage/Eclipse Using the Code Coverage Perspective Creating a Code Coverage Report

2 Features and Capabilities of Code Coverage/Eclipse Code Coverage/Eclipse collects run-time execution data from the Xpediter/TSO, Xpediter/CICS, and Xpediter/IMS debuggers, then allows you to view code coverage results online. The graphical interface allows you to do the following: Identify what percentage of an application's code was executed and how often. Determine what percentage of modified code in a program has not been executed. Document testing efforts and create a report of program test execution. The benefit of using Code Coverage/Eclipse is that it identifies the programs that have a high risk of failure related to untested code, and simplifies creating additional tests. For example, using Code Coverage/Eclipse you could identify the 10 programs within a payroll system that have the greatest risk of failure. The Code Coverage repository stores the results of code coverage test sessions. From the repository, you can generate reports that document the thoroughness of testing. Filters enable you to get data that meets specific reporting criteria. These filters can be used to report coverage results on specific sections of the source code, such as date or currency fields, to help ensure that changed code has been tested. Code Coverage/Eclipse also relates relative risk and the percent of unexecuted code to the program s complexity. For example, an aggregate of regression tests may indicate that 60% of an application has been executed. Based on this, you can determine whether this is an acceptable level of testing. It may be acceptable if all sections of code that have been changed have been tested; it may not be if modified code remains unexecuted. This is where the use of filtering and the patented Relative Risk metric come in. They allow you to determine the percentage of changes that have been tested. Relative risk gives you an idea of where the risk lies in the testing of a program. It ranks each program based on a combination of the following factors, which contribute to risk: Complexity (based on the number of unique paths through a procedure, and therefore the minimum number of test cases that should be executed) Filter information Execution counts, if available Verb types Measure of percentage of code still unexecuted Program risk measurements are listed in the report view. While it is always risky to not test to 100%, there often is not enough time to do so. Code Coverage helps you determine the level of risk to take in terms of testing or not testing code as a deadline approaches. This allows testing efforts to focus on the right parts of the program.

3 The Code Coverage Perspective The Code Coverage perspective contains four views: The Code Coverage view The Report view The Annotated Listing The Annotations view To open the Code Coverage perspective Do one of the following: From the Compuware menu, select Code Coverage. From the Window menu, select Open Perspective>Other select Code Coverage and click OK.. From the Open Perspective dialog box, The Code Coverage perspective opens.

4 Create a Code Coverage Repository Follow the procedure below to create a Code Coverage repository from Topaz Workbench. This repository is used to store Code Coverage data collected during testing. Refer to the Xpediter/Code Coverage Mainframe User/Reference Guide for more information about repositories and how to create a repository using Xpediter/Code Coverage. To create a Code Coverage repository Do one of the following: In the Code Coverage view, right-click the Repositories node and select New Repository. In the Code Coverage view, right-click a host under the Repositories node and select New Repository. From the File menu, select New>Xpediter/Code Coverage Repository. From the File menu, select New>Other. The New dialog box appears. Select Compuware>Xpediter/Code Coverage Repository. In the Host Explorer view, right-click the z/os Dataset node and select Allocate>Xpediter/Code Coverage Repository. The Allocate Xpediter/Code Coverage Repository wizard page appears. Note: The Select Host page appears if the user is not logged onto a host or if more than one HCI connection exists. Select or configure a host, then click Next. Specify the information to allocate the repository: Repository dataset name field: Specify a fully qualified name of the dataset to be created. Ensure the site s Code Coverage users have write access to the specified dataset. Space units: Specify the primary space units for the dataset. A value must be entered when any repository dataset is created. Valid values are Cylinders, Tracks, Records, and Megabytes. This field is required. Primary quantity: Specify the number of primary space units to be allocated for the repository dataset. This field is required. A valid space unit value must be entered when any repository dataset is created. The default size is 10 cylinders, which provides enough space for one or more systems totaling approximately 1000 programs of 800 executable statements each. For estimating purposes, the size of each record is (8 * number of executable verbs) Volume: Specify the volume serial number on which to allocate the repository dataset. Only use this optional field when creating a non-sms dataset.. SMS Parameters: Use these fields only when creating an SMS-managed dataset. Management class: Specify the desired SMS management class. Storage class: Specify the desired SMS storage class. Data class: Specify the desired SMS data class. Note: Click Restore Defaults to restore the fields to their defaults values. Click Finish. A message appears confirming creation of the Code Coverage repository or showing the reason for failure. The new repository is added to the Code Coverage view under the Repositories node.

5 Configure a Repository The first step in creating Code Coverage reports is to configure a repository to be used when creating the reports. The repository is where code coverage results of Xpediter/TSO, Xpediter/CICS, and Xpediter/IMS test sessions are stored. To configure a repository Ensure that a host connection is configured. Refer to the Topaz Workbench Host Explorer User Guide for information on Host Explorer connections. Ensure that the Code Coverage library has been added to the CSS TP. In the Code Coverage view, do one of the following: Right-click the Repositories node and select Add. Right-click the desired host and select Add. The Repository Selection dialog box appears so the user can begin specifying the repositories to be used when creating Code Coverage reports. 4. From the Host list, select the host that contains the repositories. 5. In the Name field, enter the full or partial name of the repository (an asterisk is the valid wildcard), then click List. The box populates with repositories that match the name entered. 6. Select the desired repositories and click OK. The repositories are added to the Code Coverage view under the selected host and will be used when creating Code Coverage reports. 7. Next, override the DDIO file associated with repository if necessary, create a code coverage report, or set code coverage preferences. To remove a repository In the Code Coverage view, right-click one or more repositories and select Remove. A confirmation dialog box appears. Select Yes to remove the repository from the Code Coverage view. To view the properties of a repository Right-click the repository in the Code Coverage view and select Properties. The Properties view appears showing the properties that apply to the chosen repository. Related topics Create a Code Coverage repository

6 Overriding the DDIO file associated with a repository During data collection, the programs DDIO location is written to the repository. If this DDIO file is subsequently moved or renamed, the new location can be specified so the source can be located when creating a Code Coverage report. To override the DDIO file associated with a repository Ensure that a host connection is configured. Refer to the Topaz Workbench Host Explorer User Guide for information on Host Explorer connections. Do one of the following: From the Window menu, select Preferences. Toggle open the Compuware node and select Code Coverage. In the Code Coverage view, click. In the Code Coverage view, from the View menu ( ), select Configure Code Coverage. The Preferences dialog box's Code Coverage pane appears. In the Additional DDIO section, select from the Host list the host to connect to. Note: If a host has not been configured, click Configure to do so. Refer to the Topaz Workbench Host Explorer User Guide for information on Host Explorer connections. 4. From the DDIO list, select the check boxes that correspond to the desired DDIO files. If the desired files are not in the list, go to the next step to add them to the list. 5. Click Add to begin specifying additional DDIO files in which program source is located. The Add Datasets dialog box appears. 6. Type one DDIO file name per line in the box. Note: Alternatively, click Browse to navigate to the DDIO files using the Dataset Selection dialog box. From the Host list, select the host that contains the DDIO files. In the Name field, enter the full or partial name of the DDIO file (an asterisk is the valid wildcard), then click List. The box populates with DDIO files that match the name entered. Select the desired DDIO files and click OK. The file names are entered in the Add Datasets dialog box. 7. Click OK. The DDIO files are added to the DDIO list. 8. Click OK to exit the Preferences dialog box. The selected DDIO files will be used to locate program source. 9. Next, create a code coverage report. To edit a DDIO file name In the DDIO list, select the DDIO file name (not the check box) and click Edit. The Edit Dataset dialog box appears. Edit the name, then click OK. The revised name appears in the DDIO list.

7 To remove a DDIO override In the DDIO list, select the DDIO file name (not the check box) and click Remove. The file is removed from the DDIO list.

8 Create a Code Coverage Report After populating the repository on the host with code coverage data collected using Xpediter/TSO, Xpediter/CICS, or Xpediter/IMS, this data can be displayed in a Code Coverage report. A Code Coverage report is created by entering report criteria, applying any desired filters, and then running the report. To create a Code Coverage report Ensure that a repository to be used when creating the reports has been configured. Ensure that code coverage data has been collected. Refer to the Topaz Workbench Xpediter/Eclipse User Guide for information on creating launch configurations. From the Compuware menu, select Code Coverage. The Code Coverage perspective appears. 4. In the Code Coverage view, do one of the following: Click. Right-click Report Requests and select New. The Code Coverage Report Request dialog box appears. 5. In the Report request name field, enter a name for the report. 6. From the Host list, select a host or configure a host. 7. From the Repository list, select or browse to the repository to be used when creating Code Coverage reports. 8. From the Summary level list, select how data in the repository should be summarized: Select Systems to see summary information about all systems contained in the repository. Results are merged for headers with the same system name, load module, and program name, regardless of test ID or user ID. Select Test IDs to see the effectiveness of individual tests within a system and see how completely each system has been tested by all tests. The Test IDs level gives the system name, test ID, and program of all programs in the repository. Load module and user ID are ignored. Each system can have multiple test IDs, and each test ID can have multiple programs. Programs with the same test ID and system name are merged. Select Users to quickly see the amount of testing done by each user. It gives the system name, user ID, and program for all programs in the repositories. Load module and test ID are ignored. Programs with the same user ID and system name are merged. Select Load Modules to display code coverage results for all load modules in the repositories. Code coverage results are merged for all programs in load modules with the same name regardless of the system, test ID, or user ID. This is helpful when the same load module is used by several systems and the user wants to know the code coverage results regardless of the system that executed it. Select Programs to display code coverage results for all programs contained in the repositories. It merges code coverage results for runs of a program that have the same compile data and time, regardless of the systems, load modules, test IDs, and user IDs from which they were executed. 9. Select the Criteria tab, then select one of the following buttons: Select Specify names and enter any system, test ID, user ID, load module, and program names to retrieve only the data that matches the criteria. It is not necessary to complete all of the fields. Wildcards may be used as a suffix. Leaving all fields blank retrieves all data.

9 Select Specify a list, choose a type from the Type list, then select items from the list showing all items of the selected type that are in the chosen repository. 10. Select the Filters tab, then do one of the following: To apply existing filters to the report, select the check boxes for the applicable filter(s). Create new filters and apply them to the report. 1 Select the Options tab, then select the Combine altered debug sessions with unaltered sessions check box to merge debug and non-debug results, or clear it to leave debug and non-debug results as separate entries in the Code Coverage report. 1 Optionally, run the report. To edit report criteria In the Code Coverage view, right-click the desired report and select Edit. The Code Coverage Report Request dialog box appears. Edit the criteria as needed and click OK. To remove a filter from a report configuration In the Code Coverage view, right-click the desired report and select Remove. The filter is removed from the report configuration.

10 Using Filters Filters enable users to get data that meets specific reporting criteria. They can be used to report coverage results on specific sections of the source code such as date or currency fields to help ensure that code changed has been tested. Filters can help determine whether certain code such as recently modified code was executed during code coverage testing. Users can filter lines or blocks of code, indicate start and end columns to be filtered, filter whole words, and exclude code from filtering. Critical vs. Exclude Filters Two types of filters can be created: critical filters and exclude filters. Critical filters allows users to focus on a particular area of critical code to determine whether certain lines or blocks of code were executed. The filter results from a critical mask are included in the "Critical" columns on the Code Coverage report. If the critical branches and critical verbs are less than 100%, some critical code was not tested. Critical filters also yield a relative risk metric to help users determine the programs with the highest risk of failure is not thoroughly tested. Exclude filters allows users to skip certain code when determining how thoroughly the program was executed. This can be particularly helpful for skipping error-handling routines that are not part of the program s main logic; if they were included in the Code Coverage statistics, the program s main logic would appear less thoroughly executed. By using an exclude filter, the filter results for this code are not included in the net code coverage statistics. Line vs. Block Masks Masks are strings the user wants to look for in the program. Line masks and block masks define the scope of the filter. Line masks identify the number of times a user-specified text string occurs between user-specified starting and ending positions in the code. The lines of code that contain the text string in the specified column range are the filtered results. A line mask could be used, for example, to display coverage information for every line of code that has the verb, MOVE, between column 1 and 80. Block masks identify a block of code using user-specified starting and ending text strings. Lines of code between these text strings are the filtered results. For example, the mask might have P99100-GENERAL-ERROR as the starting mask and P99100-GENERAL-ERROR-EXIT as the ending mask. This filter would find code that started with P GENERAL-ERROR and ended with P99100-GENERAL-ERROR-EXIT. To create and apply a filter Do one of the following: On the Apply Filters page, which appears after clicking Next on the Code Coverage Report Criteria page, click New. In the Code Coverage view, click. In the Code Coverage view, right-click Report Filters and select New. In the Code Coverage view, from the View menu ( ), select Create a New Filter. The Create Filter dialog box appears. In the Name field, enter a name for the filter. Click Add. The Add Filter Criteria dialog box appears so individual filter criteria for the new filter can be specified. 4. In the Type box, select one of the following: Critical

11 Exclude 5. In the Scope box, select one of the following types of masks. Line Block 6. Enter the details of the mask: For a line mask, type the text string to search for in the Begin mask field, the starting column position in the Start field, and the ending column position in the End field. For a block mask, type the starting text string to search for in the Begin mask field, type the ending text string in the End mask field, and enter starting and ending column positions in which to search. 7. Select the matching option to use: Select Within start/end range to find the text string anywhere it occurs between the start and end columns. Select Exactly at start position to find the text string when it starts at the starting column position. 8. Optionally, select the Whole word check box to find the text string of a line mask only when it occurs as a whole word, not when it is embedded within other words. This option only applies to line masks. 9. When you have finished creating the filter criteria, click OK. The new filter criteria is added to the Create Filter dialog box. Note: To remove filter criteria from a filter, select the filter criteria and click Remove. The filter criteria is deleted. To edit filter criteria, select the filter and click Edit. Edit the criteria and click OK. 10. To add more filter criteria for this filter, click Add and repeat the steps above. 1 Click OK. The new filter and its filter criteria appear on the Apply Filters dialog box. 1 In the Filters box, select the check boxes for each of the filters to be applied to the Code Coverage report. The criteria for each filter appears in the Filter criteria box. 1 Click Finish. A message appears asking whether to run the report now. 14. Click Yes or No. If the report is run now, the report view (indicated by the report name as the title) appears. To edit an existing filter's criteria Do one of the following: In the Code Coverage view, right-click the filter and select Edit. With the desired report in the report view, click. The Apply Filters dialog box appears. From the Filters box, select the filter name (not the check box) to be edited. Click Edit. The Edit Filter dialog box appears showing the various filter criteria included in the chosen filter. From the Filter criteria box, select the filter criteria to be edited and click Edit. the Add Filter Criteria dialog box appears.

12 Follow the instructions above to use this dialog box. 4. When all changes have been made, click OK. The revised criteria appear in the Edit Filter dialog box. 5. Click OK. To delete an existing filter In the Code Coverage view, right-click the filter and select Delete. A confirmation message appears. Click Yes. To remove filter criteria from an existing filter Do one of the following: In the Code Coverage view, right-click the filter and select Edit. With the desired report in the report view, click. The Apply Filters dialog box appears. From the Filters box, select the filter name (not the check box) to be edited. Click Edit. The Edit Filter dialog box appears showing the various filter criteria included in the chosen filter. From the Filter criteria box, select the filter criteria and click Remove. The filter criteria is removed from the filter. To duplicate an existing filter configuration Do one of the following: In the Code Coverage view, select the filter then click. In the Code Coverage view, right-click the filter and select Duplicate. The Edit Filter dialog box appears. The Name field shows the original filter name followed by a number indicating the duplication. If desired, revise the name in the Name field. Add to, edit, or remove the filter criteria as needed. 4. Click OK. The new filter is added to the Filters list in the Code Coverage view. To apply filters to the current Code Coverage report Do either of the following: In the Code Coverage view, right-click the desired report and select Select Filters. With the desired report in the report view, click.

13 With the desired report in the report view, from the View menu ( Current Report. The Apply Filters dialog box appears. ), select Apply Filters to the In the Filters box, select the check boxes for the filter(s) to be applied to the Code Coverage report. The criteria for each filter appears in the Filter criteria box. Click Finish. Note: Filters can also be created or edited from the Apply Filters dialog box.

14 Set Code Coverage preferences Follow the steps below to select which perspective opens when a code coverage report runs. Select which perspective opens when a code coverage report runs Do one of the following: From the Window menu, select Preferences. Toggle open the Compuware node and select Code Coverage. In the Code Coverage view, click. In the Code Coverage view, from the View menu ( ), select Configure Code Coverage. The Preferences dialog box's Code Coverage pane appears. In the General Code Coverage Preferences section, select the preferred behavior for opening a perspective when a code coverage report runs: Select Always to always open the chosen perspective when a code coverage report is run. Select Never to not open any perspective when a code coverage report is run. Select Prompt to be prompted to select the perspective to open when a code coverage report is run. From the Perspective list, select the perspective to open when a code coverage report runs. 4. Click OK.

15 The Code Coverage View The Code Coverage view is used for the following: The Repositories node shows the host defined in Host Explorer and shows the repositories that have been added via the Code Coverage perspective. From this node, users can do the following: Create a new Code Coverage repository. Add a Code Coverage repository to be used when creating Code Coverage reports. The Report Requests node shows reports that have been created. From this node, users can do the following: Create a new report. Edit report criteria. Remove a filter from a report. The Report Filters node shows the filters that have been created. From this node, users can do the following: Create a new filter. Select filters to be applied to a report. Edit a filter or any of its filter criteria. Duplicate existing filter criteria configuration. Delete a filter. The Code Coverage view also allows users to do the following: Run a report. Duplicate an existing report configuration. Delete a report configuration. Set Code Coverage preferences. Remove a Code Coverage repository.

16 Run a Report After a report has been created, it can be run and rerun as needed. The report can be exported. To run a Code Coverage report Do one of the following in the Code Coverage view: Select the report and click. Right-click the desired report and select Run. Double-click the desired report. The Code Coverage report runs and the results appear in the report view.

17 Duplicate an Existing Report Configuration After a report has been created, it can be easily duplicated. To duplicate an existing report configuration In the Code Coverage view, do one of the following: In the Code Coverage view, select the report then click. Right-click the report and select Duplicate. The Code Coverage Report Request wizard appears. The Name field shows the original report name followed by a number indicating the duplication. If desired, revise the name in the Name field. Edit the report criteria as needed. 4. Click OK. The new report configuration is added to the Report Requests list in the Code Coverage view.

18 Delete a Report Configuration A report configuration that is no longer needed can be deleted. To delete an existing report configuration In the Code Coverage view, right-click the report configuration and select Delete. A confirmation message appears. Click Yes.

19 The Report View The report view displays the Code Coverage results. The default columns in the report view display the following code coverage data: Name The systems and, depending on the summary level selected on the Code Coverage Report Criteria page, the test IDs, user IDs, load modules, or programs contained in the repository. For programs, this column lists the compile date and time and, if applicable, a debug indicator and an optimized indicator. Risk The estimated risk for the systems, load modules, and programs. Any risk greater than 800 appears in red. Critical verb % If a critical filter was specified, the percentage of critical verbs executed. Verb % The percentage of verbs that were executed. Critical branch % If a critical filter was specified, the percentage of critical branches executed in the program. Branch % The percentage of branches that were executed. By default, several columns of a Code Coverage report display a percentage. For example, the Verb % column shows the percentage of verbs executed. Detailed statistics used to calculate the percentage can be seen by hovering over the percentage, as shown below. For example, hovering over the Verb % shows the number of verbs executed out of the total number of verbs in the program. The optimized indicator (Optimized or Debug ) appears when applicable and indicates whether the code was compiled with the optimized option. Code Coverage results are based, in part, on the mapping of program source code to the compiler-generated machine instructions executed. Mismatches can occur due to optimization. Many other columns can be added to the report view including, but not limited to, the following: Excluded branch % If an exclude filter was specified, the percentage of excluded branches executed. Excluded verb% If an exclude filter was specified, the percentage of excluded verbs executed. Net branch % The percentage of net branches based on the total number of executable branches in the program minus the excluded branches. Net verb % The percentage of net verbs based on the total number of executable verbs in the program minus the excluded verbs. The report view is also used to do the following: Select columns to display in the Code Coverage report. Apply filters to the current report. Export a report. The currently displayed Code Coverage report, with the currently applied filter criteria and column selections, can be exported for use in a spreadsheet or other tool of choice. For information on importing the data, refer to the documentation shipped with the application being used for the import. The report view's tree format allows users to expand and contract items to view the level of detail needed. To expand all levels of the tree at the same time, from the click. To collapse all levels at the same time, click. To populate the report view Run the Code Coverage report. The title of the report view matches the report name. To view detailed statistics used to calculate a percentage

20 Hover over the percentage in the report view. The detailed statistics used to calculate the percentage appear. To select columns to display With the desired report in the report view, from the View menu ( Column dialog box appears. ), select Select Columns. The Select From the Available columns list, select the column(s) to be added to the report view display. Click Add. The columns are added to the box on the right. 4. To rearrange the order of the columns, select a column and click Move Up or Move Down. 5. When finished, click OK. The report view refreshes to display the selected columns. To export the report to a comma-delimited file With the desired report in the report view, from the View menu ( dialog box appears. ), select Export Report. The Export Report In the File name field, type a name for the report or keep the default name, which matches the Code Coverage report name. From the Save as type list, select the file type to save the file as. The default is.csv (a comma-delimited file). 4. Click Save. The report is exported to the selected location.

21 What is risk? The risk metric helps identify the programs that have the highest risk of failure if not thoroughly tested. The risk metric does not indicate how well the code has been tested because there is no way to know whether the proper input data was used. Therefore, the risk metric is never zero. The risk factors used in Code Coverage/Eclipse are described below. The factors are listed in decreasing order of importance. If the number in the Risk column is... These risk factors exist in the program: Explanation: 800 or more Unexecuted critical verbs Indicates that at least one unexecuted critical statement is present Executed critical verbs Indicates that critical statements are present, all of which were executed Unexecuted code Program complexity Indicates that no critical statements are present. The ranges listed in the table above can be used to identify which of the risk factors are present in each program. A count above 800 indicates that at least one unexecuted critical line is present. How high the count is above 800 depends on what other risk factors are present. When determining which programs have the highest risk, understand that a program with a higher count than another is not necessarily riskier when both are in the same range (for example, if one program has a count of 801 and another has a count of 856). The unexecuted code is the higher of: (1) the percentage of verbs unexecuted or (2) the percentage of branches unexecuted.

22 The Annotated Listing The Annotated Listing displays the source listing in an editor in browse mode. To view and use the Annotated Listing With the desired report in the report view, do one of the following: Right-click the program and select View Annotated Listing. Double-click the report. The Annotated Listing appears and the Annotations view populates with detailed summary information about the source listing. Do the following: Review the highlighting in the Annotated Listing determine the extent to which code was executed. By default, the following colors are used: Green indicates executed verbs. Yellow indicates partially executed branches. Red indicates unexecuted verbs. Gray indicates an optimized line. If a filter was applied to the report, review the markers in the vertical ruler in the left margin of the Annotated Listing to see whether there were any excluded or critical lines: indicates code that met an exclude filter. indicates code that met a critical filter. indicates code that met both an exclude and a critical filter. Note: Markers only appear in the vertical ruler if a filter has been applied and the filter criteria have been met. Note: Hover the mouse over the icon or over the vertical ruler for any executable line to reveal a tool tip giving information on the execution status, filter type, and branch status. Inspect the overview ruler in the right margin of the Annotated Listing, which indicates graphically unexecuted code and code that matches filter criteria. Click the red or green rectangle to go directly to the corresponding line of code. To view a printer-friendly Annotated Listing When printing, choose the printer-friendly Annotated Listing since it contains the exclude and critical markers that appear in the left margin of the Annotated Listing. With the desired report in the report view, right-click the program and select View Printer-Friendly Annotated Listing. The Printable Report Options dialog box appears. Select the options for the report: Select All to print the entire report. Select Starting at line to print a report from that line forward.

23 Select Line range and enter a start line and end line to print only those lines of the report. Select Include highlighting to print a report that shows the highlighting displayed in the Annotated Listing. Select Include program information to print a report that shows the program, system, load module, test, user, language, and repository information used, as well as debug and optimized indicators. Select Include annotations legend to print a report that contains a legend explaining the annotations used in the report. Select Include statement numbers to print a report that lists statement numbers. Click OK. A printer-friendly version of the report appears in a new tab in the Annotated Listing. 4. To print the report, from the File menu, select Print. 5. Complete the Print dialog box. To change the way annotations display Use the Preferences dialog box's Annotations page to control annotation behavior such as text highlighting, the color in which code coverage annotations appear, and the vertical ruler and overview ruler. Refer to the Eclipse documentation for how to use this page.

24 The Annotations View The Annotations view shows a summary of all annotations in the Annotated Listing. From this view, users can go directly to any line in the Annotated Listing, such as an unexecuted line. By default, the Annotations view is grouped by execution status. To select annotations to display in the Annotations view From the Annotations view's View menu ( appears. ), select Select Annotations. The Select Annotations dialog box Select one of the following: Select All selected annotations to show annotations for all of the selected check boxes. This is the AND condition. Use this to, for example, show all unexecuted and critical annotations. Select Any selected annotations to show annotations for any of the selected check boxes. This is the OR condition. Select all applicable check boxes: Executed Unexecuted Critical Exclude Optimized 4. Click OK. The Annotations view refreshes to match the selected criteria. To select columns to display in the Annotations view From the Annotations view's View menu ( Selection dialog box appears. ), select Select Columns. The Code Coverage Column Use the Add and Remove buttons to select the columns to be shown in the Annotations view. Use the Move Up and Move Down buttons to arrange the selected columns in the desired order for the view. Note: At any time, click Restore Defaults to return to the default settings. 4. When finished, click OK. To change how annotations are grouped in the Annotations view From the Annotations view's View menu ( ), select Group By and then select one of the following: Select Execution Status to group by execution status (executed or unexecuted). The default grouping is by execution status. Select Filter Type to group by critical filters, exclude filters, and no filters. Select Branch Status to group by the execution status of a branch. Select None to group by line number. Note: The columns are sortable by clicking on the headers. To view a line item in the Annotated Listing

25 In the Annotations view, double-click any line item, such as an unexecuted critical line. The corresponding line of code appears in the Annotated Listing.

26 Exporting and Importing Code Coverage Configuration Settings Code Coverage configurations can be exported and then imported into the local file system. Code Coverage settings such as host connection information, repositories, DDIO overrides, filters, columns to display, annotations, and highlighting can be exported. The Code Coverage configuration settings that can be exported or imported are as follows: Code Coverage - All Code Coverage configuration settings Preferences and View Settings - Preferences and view settings from the Code Coverage perspective

27 Product Assistance Compuware provides assistance for customers with its documentation and Compuware Support Center. Documentation The product documentation set includes the following: The Topaz Workbench Installation Guide provides information on installation. The online help provides descriptions of the product operating procedures and reference information. The release notes and installation guide can be found at Online books are provided in PDF format, and require a supported version of Adobe Reader to view them. The free Adobe Reader is available on the Adobe web site at If you cannot locate the information you need, or the information is not clear, please let us know by contacting Customer Solutions. Compuware Support Center Visit the Compuware Support Center, to find product documentation, knowledge articles, and other technical resources. You can open a case with the Customer Solutions team, order products, and much more. Contact Customer Solutions by phone: USA and Canada: or All other countries: Contact your local Compuware office. Contact information is available at Please gather the following information before calling Compuware's 24-hour telephone support: The name, release number, and build number of your product. This information is displayed in the About dialog box. Installation information including installed options, whether the product uses local or network databases, whether it is installed in the default directories, whether it is a standalone or network installation, and whether it is a client or server installation. Environment information, such as the operating system and release on which the product is installed, memory, hardware and network specification, and the names and releases of other applications that were running when the problem occurred. The location of the problem within the running application and the user actions taken before the problem occurred. The exact application, licensing, or operating system error messages, if any. Visit Compuware on the web at for additional product information. Compuware also offers user communities, online forums to collaborate, network, and exchange best practices with other Compuware solution users worldwide. Go to to join.