<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 09/04/2020 15:04, Joel Sherrill
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAF9ehCUpjtOWY3-=cTVV3ZU0YaCuPY+X1z0e98k9ydou_9m+ng@mail.gmail.com">
      <div>
        <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"
              moz-do-not-send="true">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"
                        moz-do-not-send="true">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. <br>
      </div>
    </blockquote>
    The RTEMS Test framework has checks to ensure that the environment
    is sane before a new test case is executed. It decouples the test
    cases from the runner. This could be used to group test cases to
    test suites depending on the target memory size.<br>
    <blockquote type="cite"
cite="mid:CAF9ehCUpjtOWY3-=cTVV3ZU0YaCuPY+X1z0e98k9ydou_9m+ng@mail.gmail.com">
      <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 <br>
      </div>
    </blockquote>
    <p>I don't think that tests for clock_nanosleep() will result in big
      executables. The executable size is mostly defined by the feature
      to be tested.<br>
    </p>
  </body>
</html>