From 6029c8d8f090cc98bb8f46986fc16262383796c2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Hoguin?= Date: Wed, 24 Jan 2018 13:44:51 +0100 Subject: Update user guide --- guide/overview.html | 34 +++++++++++++++++----------------- 1 file changed, 17 insertions(+), 17 deletions(-) (limited to 'guide/overview.html') diff --git a/guide/overview.html b/guide/overview.html index 4e5743f..1c6f842 100644 --- a/guide/overview.html +++ b/guide/overview.html @@ -62,26 +62,26 @@ That’s where Asciidoc comes in.

T to be separate from source. It will generate HTML, PDF, man pages and more from the documentation you write in the doc/src/ folder in your repository.

3.4. Running tests

Erlang.mk supports a lot of different testing and static -analysis tools.

The make shell -Chapter 16, Erlang shell command allows you +analysis tools.

The make shell +Chapter 17, Erlang shell command allows you to test your project manually. You can automate these -unit tests with EUnit -Chapter 17, EUnit and test -your entire system with Common Test -Chapter 18, Common Test. -Code coverage -Chapter 19, Code coverage can of course +unit tests with EUnit +Chapter 18, EUnit and test +your entire system with Common Test +Chapter 19, Common Test. +Code coverage +Chapter 20, Code coverage can of course be enabled during tests.

Erlang.mk comes with features to make your life easier when -setting up and using Continuous integration -Chapter 20, Continuous integration.

On the static analysis side of things, Erlang.mk comes with -support for Dialyzer -Chapter 21, Dialyzer and Xref -Chapter 22, Xref, +setting up and using Continuous integration +Chapter 21, Continuous integration.

On the static analysis side of things, Erlang.mk comes with +support for Dialyzer +Chapter 22, Dialyzer and Xref +Chapter 23, Xref, to perform success typing analysis and cross referencing -of the code.

3.5. Need more?

Not convinced yet? You can read about why you should use Erlang.mk -Chapter 25, Why Erlang.mk -and its history -Chapter 26, Short history. And if you’re still not +of the code.

3.5. Need more?

Not convinced yet? You can read about why you should use Erlang.mk +Chapter 26, Why Erlang.mk +and its history +Chapter 27, Short history. 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.

Prev   Next
 Home 
-- cgit v1.2.3