Stats

  • Locked Locked
  • Replies 3
  • Subscribers 66
  • Views 2738
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

vManager/IMC/Coverage: How to know what tests hit a specific coverpoint bin from a merged coverage db

SA20250220540

Hi,

I am new to vManager / IMC, and am trying to analyze my set of tests by looking at the coverage report, but cannot find how to extract the test name that hit a specific coverpoint bin from the merged functional coverage data base.

The individual coverage UCD file is inside its respective test folder, and all the test folders are inside a regression folder, so I am using vManager and/or IMC to create a merged coverage UCD file directly from the GUI by clicking on Collect Runs/Load and selecting the regression folder. It properly creates the merged file, but then I dont know how to find what specific test is hitting each specific bin. I have also tried by running the "correlate runs" but cannot see that information in the attributes section.

Is this a supported feature by vManager/IMC?

If so, is there any particular argument or option needed to keep that data when merging the db?

Finally, how do I get to the actual test name for each coverpoint bin?

Thanks,

S

Parents
  • StephenH

    The correlation feature is the right one to use, and so long as your "collect" step did import the individual coverage files, you should have got a list of the tests that hit the item you wanted to correlate against.

    There might have been an issue loading the coverage files, or you may have some other error that needs investigating. You can start by looking at the tool messages, from the envelope icon at the bottom right of the main window, or in vmanager.log or mdv.log.

    If you don't find anything obvious in there, I would suggest to file a support request by logging in to https://support.cadence.com/ so that one of the AE team can get in touch 1:1 to investigate with you.

Reply
  • StephenH

    The correlation feature is the right one to use, and so long as your "collect" step did import the individual coverage files, you should have got a list of the tests that hit the item you wanted to correlate against.

    There might have been an issue loading the coverage files, or you may have some other error that needs investigating. You can start by looking at the tool messages, from the envelope icon at the bottom right of the main window, or in vmanager.log or mdv.log.

    If you don't find anything obvious in there, I would suggest to file a support request by logging in to https://support.cadence.com/ so that one of the AE team can get in touch 1:1 to investigate with you.

Children
  • SA20250220540
    in reply to StephenH

    Hi StephenH,

    Thanks for your response. It finally worked by using that option, it is insteresting that it only works when merging the individual coverage db from the vmanager by using the "collect" functionality. It does not work when I try to "correlate runs" from a previously generated ucd/ucm file.

    Thanks

  • StephenH
    in reply to SA20250220540

    I'm not quite clear from your comments, but it sounds like you are comparing what happens after a collect operation on multiple runs, versus what happens if you merge outside of vManager and load just the merged coverage file.

    In the Cadence tool flow, merging discards the history of which test hit which bin, meaning that ranking and correlation cannot be performed on a merged coverage file.

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.