<div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Apr 9, 2020, 7:43 AM Sebastian Huber <<a href="mailto:sebastian.huber@embedded-brains.de">sebastian.huber@embedded-brains.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<p>On 09/04/2020 14:40, Joel Sherrill wrote:<br>
</p>
<blockquote type="cite">
<div>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Apr 9, 2020, 7:28 AM
Utkarsh Rai <<a href="mailto:utkarsh.rai60@gmail.com" target="_blank" rel="noreferrer">utkarsh.rai60@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Hi,
<div>I am willing to add tests for clock_nanosleep with
CLOCK_MONOTONIC. What is the standard way of adding test
for an already present API but with different
configuration? For eg. should I add
'psxtmclocknanosleep04/ 05/ 06' in the testsuite?</div>
</div>
</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">Yes. That is the pattern.</div>
</blockquote>
We should try to reduce the count of test programs since on boards
with a long reboot time, more tests programs means much more test
time (compared to the new test cases alone).<br></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto">And there is the competing factor that you end up with test executables that are overly complex, do not have clean environments for many of the test cases, and are too large to fit on many target boards. </div><div dir="auto"><br></div><div dir="auto">I know you have seen how long the list is of tests that you can't run on many boards. That's a bad quality attribute </div><div dir="auto"><br></div><div dir="auto">--jo</div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
</div>
</blockquote></div></div></div>