'Re: [Scilab-Dev] test_run: new tag "<-- BROKEN --> by {#bug_id of breaking bug]"'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       scilab-dev
Subject:    Re: [Scilab-Dev] test_run: new tag "<-- BROKEN --> by {#bug_id of breaking bug]"
From:       Samuel Gougeon <sgougeon () free ! fr>
Date:       2019-02-02 18:40:50
Message-ID: 1034be68-9bc9-55f6-73dc-3e8d12ac0007 () free ! fr
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

Le 02/02/2019 à 19:32, Samuel Gougeon a écrit :
>
> As a general policy, i am not in favour of multiplying the number of 
> available tags.
> However, what about creating a new one to point this situation?
> It could be
>  // <-- BROKEN -->  by 15790
> Such a test would be skipped, and in the test_run report, "skipped: 
> broken by 15790" would be displayed.
>

Another processing could be: the test is run anyway. Then,

  * if it passes: "passed. No longer broken by 15790" is displayed.
    This would focus on the fact that the test's header must be updated.

  * otherwise: "failed: broken by 15790" is displayed
    This would focus on fixing the bug 15790.

[Attachment #5 (text/html)]

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Le 02/02/2019 à 19:32, Samuel Gougeon a
      écrit :<br>
    </div>
    <blockquote cite="mid:12f5f493-5049-d79a-6907-661ee42415c5@free.fr"
      type="cite"> <br>
      <p> As a general policy, i am not in favour of multiplying the
        number of available tags.<br>
        However, what about creating a new one to point this situation?<br>
        It could be<br>
        <tt> // &lt;-- BROKEN --&gt;  by 15790</tt><tt><br>
        </tt>Such a test would be skipped, and in the test_run report,
        "skipped: broken by 15790" would be displayed.<br>
      </p>
    </blockquote>
    <br>
    Another processing could be: the test is run anyway. Then,<br>
    <ul>
      <li>if it passes: "passed. No longer broken by 15790" is
        displayed.<br>
        This would focus on the fact that the test's header must be
        updated.<br>
        <br>
      </li>
      <li>otherwise: "failed: broken by 15790" is displayed<br>
        This would focus on fixing the bug 15790.</li>
    </ul>
    <br>
  </body>
</html>

_______________________________________________
dev mailing list
dev@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/dev

[prev in list] [next in list] [prev in thread] [next in thread] 