Re: [sv-ec] Behavior of at_least options with default bins.

Hi ,

Please provide with your thoughts.

I feel that the following should be the behavior ::

1) Default bins with hit_count >= at_least  should be shown with/as covered bins.
2) Default bins with      1 <= hit_count < at_least should be shown with/as uncovered bins.
         Currently as per the LRM uncoverered default bins are not reported.
	 But i feel that if the default bin is hit , irrespective of the at_least values it should be shown somewhere.
3) Default bins will not affect coverage calculation in any way.


Thanks
Saurabh

Saurabh Sharma wrote:

> Hi
>
> I have a query about reporting of default bins when at_least options 
> is also set.
>
> As per the LRM
>     "The default bin catches the values of the coverage point that do 
>      not lie within any of the defined bins."
> And it also states that
>     " The default is useful for catching unplanned or invalid values."
>
> At_least is an instance specific coverage option and
> It refers to Minimum number of hits for each bin. A bin with a hit 
> count that is less than number is not considered covered.
>
>
> But does the concept of COVERED applies to DEFAULT bins.
> default bins do not impact coverage calculation in any way. They are 
> used just to know if there is any unplanned value being hit.
>
> If a default bin is hit but the count is less than at_least
> then should we report it or not. Not reporting it may cause user
> to miss on important information.
>
> And what should be an appropriate way of reporting it.
>
> Looking forward to your thoughts.
>
> Thanks
> Saurabh
>
>
>


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.