Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space ENGINES1031 and version 10.3.4

You can import findings into the IDE from DTP server or from an .xml report file. The filter must be configured in order to download findings from DTP (see Customizing Import Options). If you cannot choose a filter from the filter configuration drop-down menu, verify that you have appropriate access in DTP (see "Project Creation and Configuration" in the DTP documentation for additional information).

Choose Parasoft> Import Findings to quickly import findings from the enabled DTP server (see Connecting to DTP) according to the Import Options configuration (see Customizing Import Options). You can also import findings from the DTP Findings view menus.

  1. If not already open, choose Parasoft> Show View> DTP Findings from the IDE main menu.
  2. Click the DTP Findings view menu drop-down and choose Import from> DTP or Local File or URL...


    Conditional Content
    product: (cpptest, jtest)
    product: (cpptest, jtest)
    sv-attr:0A01020401598D973E6641760F8AF4E50A01020401598D973E6749C5267CE6FE 0A01020401598D973E671AAA268425A3

    If you chose to import findings from DTP, then the import will begin immediately.
    If you are importing from an .xml file, either enter the URL of the file or browse for the file when prompted to begin the import.
    An alert will tell you how many findings were imported.

  3. Enable the Show imported findings now option in the alert and click OK to load the findings into the Findings view. 

    Conditional Content
    product: (cpptest, jtest)
    product: (cpptest, jtest)
    sv-attr:0A01020401598D973E6641760F8AF4E50A01020401598D973E6749C5267CE6FE 0A01020401598D973E671AAA268425A3

    If the imported findings are associated with a file that has been modified, a message appears specifying the file(s) that are out of sync. The markers associated with these findings (including the line numbers) may not match the location in the local resource files or may indicate findings that have already been resolved.
    Findings associated with resources missing locally are not imported and the displayed message lists the files that are unavailable. 

    Conditional Content
    product: (cpptest, jtest)
    product: (cpptest, jtest)
    sv-attr:0A01020401598D973E6641760F8AF4E50A01020401598D973E6749C5267CE6FE 0A01020401598D973E671AAA268425A3