<p>There is one unit test binary which contains several hundred tests within it. <code>make check</code> just runs the binary, and if none of the tests within it fail, then <code>make check</code> passes. Because there is only one binary, <code>make check</code> sees this as being only one unit test, but in reality, all 200+ tests are just packaged into the same binary.</p>

CC BY-SA 4.0
2018-09-06T15:51:49.147Z
2018-09-06T15:51:49.147Z
Ava Chow
<p>After building Bitcoin ABC and running <code>make check</code>, I get this:</p>

<pre><code># TOTAL: 1
# PASS:  1
# SKIP:  0
# XFAIL: 0
# FAIL:  0
# XPASS: 0
# ERROR: 0
</code></pre>

<p>Is that correct?</p>

<nodes><ecash><make>
How many unit test should be run after building a node?
Curyous
# How many unit test should be run after building a node?

(Asked by: username_0 on 2018-09-05)

After building Bitcoin ABC and running make check, I get this:
# TOTAL: 1
# PASS:  1
# SKIP:  0
# XFAIL: 0
# FAIL:  0
# XPASS: 0
# ERROR: 0

Is that correct?

**Tags:** nodes, ecash, make


---

## 1 answers

### Answer by username_1 on 2018-09-06. Score: 1

There is one unit test binary which contains several hundred tests within it. `make check` just runs the binary, and if none of the tests within it fail, then `make check` passes. Because there is only one binary, `make check` sees this as being only one unit test, but in reality, all 200+ tests are just packaged into the same binary.


---

