[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
patch to add AT_CHECK_EUNIT autotest macro
From: |
Romain Lenglet |
Subject: |
patch to add AT_CHECK_EUNIT autotest macro |
Date: |
Fri, 31 Jul 2009 14:09:49 +0900 |
Hi,
The attached patch defines a new Autotest macro, AT_CHECK_EUNIT, to
execute EUnit unittests in a testsuite. EUnit is a standard unittest
system part of Erlang/OTP.
0001-Add-AT_CHECK_EUNIT-macro-to-run-Erlang-EUnit-unittes.patch
Description: Binary data
I think it would be a good idea to define such macros to integrate
such third party testing system (EUnit, JUnit, etc.), and to consider
Autotest as a general driver to perform all the tests of a package. Is
that a good idea?
Is the macro name OK? The name "EUnit" identifies uniquely the EUnit
system, so there shouldn't be any ambiguity.
The macro requires variables ERL, ERLC, and ERLCFLAGS to be defined. I
documented that those should be configured by configure, and I
modified the generated atconfig file to contain those configured
values. It's simple and transparent, but may be ugly since those will
be defined for all testsuites, even those that don't use
AT_CHECK_EUNIT. Any suggestion to make it better? And should I exit
with code 99, in AT_CHECK_EUNIT, if those variables are not defined?
Also, sorry for the form of this email.
I am sending this pach manually from a system without git.
Best regards,
--
Romain Lenglet
- patch to add AT_CHECK_EUNIT autotest macro,
Romain Lenglet <=