diff options
Diffstat (limited to 'guide/overview.html')
-rw-r--r-- | guide/overview.html | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/guide/overview.html b/guide/overview.html index c78efdc..7f98ef3 100644 --- a/guide/overview.html +++ b/guide/overview.html @@ -58,13 +58,13 @@ analysis tools.</p><p>The <a class="link" href="shell.html" title="Chapter 18.� to test your project manually. You can automate these unit tests with <a class="link" href="eunit.html" title="Chapter 19. EUnit">EUnit</a> and test your entire system with <a class="link" href="ct.html" title="Chapter 20. Common Test">Common Test</a>. -<a class="link" href="coverage.html" title="Chapter 22. Code coverage">Code coverage</a> can of course +<a class="link" href="coverage.html" title="Chapter 23. Code coverage">Code coverage</a> can of course be enabled during tests.</p><p>Erlang.mk comes with features to make your life easier when -setting up and using <a class="link" href="ci.html" title="Chapter 23. Continuous integration">Continuous integration</a>.</p><p>On the static analysis side of things, Erlang.mk comes with -support for <a class="link" href="dialyzer.html" title="Chapter 24. Dialyzer">Dialyzer</a> and <a class="link" href="xref.html" title="Chapter 25. Xref">Xref</a>, +setting up and using <a class="link" href="ci.html" title="Chapter 24. Continuous integration">Continuous integration</a>.</p><p>On the static analysis side of things, Erlang.mk comes with +support for <a class="link" href="dialyzer.html" title="Chapter 25. Dialyzer">Dialyzer</a> and <a class="link" href="xref.html" title="Chapter 26. Xref">Xref</a>, to perform success typing analysis and cross referencing -of the code.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_need_more"></a>3.5. Need more?</h2></div></div></div><p>Not convinced yet? You can read about <a class="link" href="why.html" title="Chapter 28. Why Erlang.mk">why you should use Erlang.mk</a> -and its <a class="link" href="history.html" title="Chapter 29. Short history">history</a>. And if you’re still not +of the code.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_need_more"></a>3.5. Need more?</h2></div></div></div><p>Not convinced yet? You can read about <a class="link" href="why.html" title="Chapter 29. Why Erlang.mk">why you should use Erlang.mk</a> +and its <a class="link" href="history.html" title="Chapter 30. Short history">history</a>. And if you’re still not convinced after that, it’s OK! The world would be boring if everyone agreed on everything all the time.</p></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="getting_started.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="updating.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top"> </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> </td></tr></table></div> </main> |