Unit testing - Erlang Programming

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Message from discussion Unit testing
Received-SPF: pass (google.com: domain of erlang-questions-boun...@erlang.org designates 192.121.151.104 as permitted sender) client-ip=192.121.151.104;
Message-ID: <4EF3AB72.6020...@erlang-solutions.com>
Date: Thu, 22 Dec 2011 23:13:06 +0100
From: Jesper Louis Andersen <jesper.louis.ander...@erlang-solutions.com>
Organization: Erlang Solutions
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
 rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: erlang-questi...@erlang.org
References: <CAJ=2b07+tLjXiputEf7tLXM4Eff5y=CVLe0TxoZ017+Eq4L...@mail.gmail.com>
 <CAJ=2b06dXTd3Dp7=+54RBKJwB_MX-6n5A-jfcaYiz7RQm7S...@mail.gmail.com>
 <14C7BD11-34CC-450A-AE9F-D0A027D4D...@lovely.email.ne.jp>
In-Reply-To: <14C7BD11-34CC-450A-AE9F-D0A027D4D...@lovely.email.ne.jp>
Subject: Re: [erlang-questions] Unit testing
Precedence: list
Content-Type: multipart/mixed; boundary="===============5936844374186910832=="
Errors-To: erlang-questions-boun...@erlang.org
Sender: erlang-questions-boun...@erlang.org

This is a multi-part message in MIME format.
--===============5936844374186910832==
Content-Type: multipart/alternative;
 boundary="------------040608070709070105060002"

This is a multi-part message in MIME format.
--------------040608070709070105060002
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 12/21/11 12:41 AM, Joseph Norton wrote:
> I'd recommend to use QuickCheck (http://www.quviq.com/) and/or PropEr 
> (http://proper.softlab.ntua.gr/) for testing Erlang and non-Erlang 
> applications. Just in case no one else has mentioned either of these 
> tools to you.
>
We use PropEr in etorrent currently. We were using QuickCheck until 
Magnus Klaar changed us to PropEr. We run PropEr from eunit actually, 
just because it is easier to hook into the tool chain. But this is for 
internal testing of individual modules.

The other tool we use it Common Test (ct) which is a bit more involved 
to set up. We use it to spawn a small local BitTorrent network and test 
that our application can communicate with itself and a foreign 
BitTorrent client. This tend to weed out many problems right away. The 
advantage of Erlang is that you can use it through ct to control other 
applications while you are running tests.

So my approach would be: Internal test => eunit, Large scale blackbox 
test => CommonTest. And finally, use PropEr or QuickCheck for writing 
the test cases so you can automatically generate a couple 1000 tests and 
get your system properly tested.

-- 
Jesper Louis Andersen
   Erlang Solutions Ltd., Copenhagen, DK


--------------040608070709070105060002
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    On 12/21/11 12:41 AM, Joseph Norton wrote:
    <blockquote
      cite="mid:14C7BD11-34CC-450A-AE9F-D0A027D4D...@lovely.email.ne.jp"
      type="cite">
      <div>I'd recommend to use QuickCheck (<span
          class="Apple-style-span" style="font-family: helvetica, arial,
          freesans, clean, sans-serif; font-size: 13px; line-height:
          19px; "><a moz-do-not-send="true" href="http://www.quviq.com/"
            style="margin-top: 0px; margin-right: 0px; margin-bottom:
            0px; margin-left: 0px; padding-top: 0px; padding-right: 0px;
            padding-bottom: 0px; padding-left: 0px; color: rgb(65, 131,
            196); text-decoration: none; ">http://www.quviq.com/</a>)&nbsp;</span>and/or
        PropEr (<span class="Apple-style-span" style="font-family:
          helvetica, arial, freesans, clean, sans-serif; font-size:
          13px; line-height: 19px; "><a moz-do-not-send="true"
            href="http://proper.softlab.ntua.gr/" style="margin-top:
            0px; margin-right: 0px; margin-bottom: 0px; margin-left:
            0px; padding-top: 0px; padding-right: 0px; padding-bottom:
            0px; padding-left: 0px; color: rgb(65, 131, 196);
            text-decoration: none; ">http://proper.softlab.ntua.gr/</a>)
          for testing Erlang and non-Erlang applications. &nbsp;</span>Just
        in case no one else has mentioned either of these tools to you.</div>
      <br>
    </blockquote>
    We use PropEr in etorrent currently. We were using QuickCheck until
    Magnus Klaar changed us to PropEr. We run PropEr from eunit
    actually, just because it is easier to hook into the tool chain. But
    this is for internal testing of individual modules.<br>
    <br>
    The other tool we use it Common Test (ct) which is a bit more
    involved to set up. We use it to spawn a small local BitTorrent
    network and test that our application can communicate with itself
    and a foreign BitTorrent client. This tend to weed out many problems
    right away. The advantage of Erlang is that you can use it through
    ct to control other applications while you are running tests.<br>
    <br>
    So my approach would be: Internal test =&gt; eunit, Large scale
    blackbox test =&gt; CommonTest. And finally, use PropEr or
    QuickCheck for writing the test cases so you can automatically
    generate a couple 1000 tests and get your system properly tested.<br>
    <br>
    <pre class="moz-signature" cols="72">-- 
Jesper Louis Andersen
  Erlang Solutions Ltd., Copenhagen, DK</pre>
  </body>
</html>

--------------040608070709070105060002--

--===============5936844374186910832==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
erlang-questions mailing list
erlang-questi...@erlang.org
http://erlang.org/mailman/listinfo/erlang-questions

--===============5936844374186910832==--
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
