[LLVMdev] [Patch] Adding unit tests to LLVM

[Talin]

Do the existing tests use a wildcard rule to gather all test sources? We
would need to insure that the wildcard rule for the unit tests and the large
tests are mutually exclusive.
Also, will the unit tests be one executable or many? They will probably
compile/run faster if there is a smaller number of executables.

On Mon, Dec 29, 2008 at 1:43 PM, Misha Brukman <brukman at gmail.com> wrote:

> 2008/12/29 Talin <viridia at gmail.com>
>
>> I'm working on an update to the patch. The only thing holding me up is
>> trying to come to a final decision as to where all the various pieces should
>> live. Specifically, the Google Test library, and the actual unit tests
>> themselves.
>
>
> I would recommend putting Google Test in llvm/test/googletest .  The
> unittests should probably go in llvm/test with other tests, in the same
> directories, e.g., tests of the various analysis algorithms would live in
> llvm/test/Analysis, 1 file per analysis, unless folks think they should go
> further into the tree: llvm/test/Analysis/Andersens/, etc., but I think it
> would be cleaner and easier if the files for a single library were in the
> same directory, as we would be able to create a single unittest from all of
> them, to speed up the build/link/test cycle.
>
> Thoughts?
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
>


-- 
-- Talin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20081229/f9a6175e/attachment.html>