<div dir="ltr">Okay, if you&#39;re going to twist my arm about it :)<div><br></div><div><a href="https://github.com/nose-devs/nose/issues/829">https://github.com/nose-devs/nose/issues/829</a><br></div><div><br></div><div>Eric</div>

<div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Aug 3, 2014 at 6:00 AM, Ned Batchelder <span dir="ltr">&lt;<a href="mailto:ned@nedbatchelder.com" target="_blank">ned@nedbatchelder.com</a>&gt;</span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div bgcolor="#FFFFFF" text="#000000">
    Eric, if by &quot;make my own custom nose plugin,&quot; you mean, &quot;submit a
    patch to the nose plugin that implements the option to skip the
    report,&quot; then yes, that sounds good! :)<span class="HOEnZb"><font color="#888888"><br>
    <br>
    --Ned.</font></span><div><div class="h5"><br>
    <br>
    <div>On 8/2/14 8:36 PM, Eric Larson wrote:<br>
    </div>
    <blockquote type="cite">
      <div dir="ltr">Hey Ned,
        <div><br>
        </div>
        <div>I might give that a shot. Your comment also got me thinking
          that I could make my own custom nose plugin that utilizes your
          module without making the report() command that the built-in
          one does. That solution might work better for the projects I
          have in mind -- but in either case, thanks for the quick
          response!</div>
        <div><br>
        </div>
        <div>Cheers,</div>
        <div>Eric</div>
        <div><br>
        </div>
      </div>
      <div class="gmail_extra"><br>
        <br>
        <div class="gmail_quote">On Sat, Aug 2, 2014 at 4:07 PM, Ned
          Batchelder <span dir="ltr">&lt;<a href="mailto:ned@nedbatchelder.com" target="_blank">ned@nedbatchelder.com</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div bgcolor="#FFFFFF" text="#000000">
              <div> On 8/2/14 6:16 PM, Eric Larson wrote:<br>
                <blockquote type="cite">
                  <div dir="ltr">Hello,
                    <div><br>
                    </div>
                    <div>I am using `nose` combined with `coverage` to
                      test code coverage in several projects, and it is
                      working well. However, I would like to be able to
                      run nosetests and generate coverage information
                      (i.e., the .coverage file) but *not* print the
                      results of the coverage report to the terminal.</div>
                    <div><br>
                    </div>
                  </div>
                </blockquote>
              </div>
              It sounds like you are using the coverage nose plugin.  It
              prints a textual report when the tests are finished.
              <div><br>
                <blockquote type="cite">
                  <div dir="ltr">
                    <div>In my case, each PR on Github automatically
                      sends info to Coveralls, which generates nice
                      reports, so I don&#39;t need to see it. Moreover,
                      having the printout makes it more difficult to
                      scroll to the points in the tests that might have
                      failed.</div>
                    <div><br>
                    </div>
                    <div>Is there a way to generate coverage information
                      but not print it out?</div>
                  </div>
                </blockquote>
                <br>
              </div>
              I prefer to use coverage to run nosetests rather than to
              run coverage within nose.  The nose plugin seems to have
              no option to skip the report.  &quot;coverage run&quot; will run a
              program under coverage measurement, then later (if you
              wish), &quot;coverage report&quot; will report on the results.<br>
              <blockquote type="cite">
                <div dir="ltr">
                  <div><br>
                  </div>
                  <div>Cheers,</div>
                  <div>Eric</div>
                  <div><br>
                  </div>
                </div>
                <br>
                <fieldset></fieldset>
                <br>
                <pre>_______________________________________________
testing-in-python mailing list
<a href="mailto:testing-in-python@lists.idyll.org" target="_blank">testing-in-python@lists.idyll.org</a>
<a href="http://lists.idyll.org/listinfo/testing-in-python" target="_blank">http://lists.idyll.org/listinfo/testing-in-python</a>
</pre>
              </blockquote>
              <br>
            </div>
            <br>
            _______________________________________________<br>
            testing-in-python mailing list<br>
            <a href="mailto:testing-in-python@lists.idyll.org" target="_blank">testing-in-python@lists.idyll.org</a><br>
            <a href="http://lists.idyll.org/listinfo/testing-in-python" target="_blank">http://lists.idyll.org/listinfo/testing-in-python</a><br>
            <br>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset></fieldset>
      <br>
      <pre>_______________________________________________
testing-in-python mailing list
<a href="mailto:testing-in-python@lists.idyll.org" target="_blank">testing-in-python@lists.idyll.org</a>
<a href="http://lists.idyll.org/listinfo/testing-in-python" target="_blank">http://lists.idyll.org/listinfo/testing-in-python</a>
</pre>
    </blockquote>
    <br>
  </div></div></div>

<br>_______________________________________________<br>
testing-in-python mailing list<br>
<a href="mailto:testing-in-python@lists.idyll.org">testing-in-python@lists.idyll.org</a><br>
<a href="http://lists.idyll.org/listinfo/testing-in-python" target="_blank">http://lists.idyll.org/listinfo/testing-in-python</a><br>
<br></blockquote></div><br></div>