From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id 8090A7F1AA for ; Thu, 10 Sep 2015 12:09:57 +0200 (CEST) IronPort-PHdr: 9a23:yhowNBN4SltL53SqKNUl6mtUPXoX/o7sNwtQ0KIMzox0Kf36rarrMEGX3/hxlliBBdydsKIYzbOK+4nbGkU+or+5+EgYd5JNUxJXwe43pCcHRPC/NEvgMfTxZDY7FskRHHVs/nW8LFQHUJ2mPw6anHS+4HYoFwnlMkItf6KuStKU1pj//tvx0qOQSj0AvCC6b7J2IUf+hiTqne5Sv7FfLL0swADCuHpCdrce72ppIVWOg0S0vZ/or9ZLuh5dsPM59sNGTb6yP+FhFeQZXwIdLnst6cb3mR7GRAqJrjtAAyRF2iZPVirC7BeydZfrszDmsfJ91TPSGMbfSag1Xznqu6VuQxbskCYBHzg87CfahtEm34xBpxf0iRV12Y/fbcmxObJQc7jGdNUGDT5vV8xLVidMRKexWIUCFPEIO/pwro/nplJIowHoVlrkP//m1jId3iy+5qY9yel0VFyf0Q== Authentication-Results: mail3-smtp-sop.national.inria.fr; spf=None smtp.pra=fabrissimo@gmail.com; spf=Pass smtp.mailfrom=fabrissimo@gmail.com; spf=None smtp.helo=postmaster@mail-la0-f54.google.com Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of fabrissimo@gmail.com) identity=pra; client-ip=209.85.215.54; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="fabrissimo@gmail.com"; x-sender="fabrissimo@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of fabrissimo@gmail.com designates 209.85.215.54 as permitted sender) identity=mailfrom; client-ip=209.85.215.54; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="fabrissimo@gmail.com"; x-sender="fabrissimo@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-la0-f54.google.com) identity=helo; client-ip=209.85.215.54; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="fabrissimo@gmail.com"; x-sender="postmaster@mail-la0-f54.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0BqAQDIVfFVmzbXVdFdDoNpaQaDIKkikmaHNAc8EAEBAQEBAQEBEAEBAQEBBgsLCSEugh2CBwEBBBIRHQEtCwEDDAEFBQsNAgIJHQICIhIBBQEKEgYTEgkHh3cDEg2pEYEwPjGLQYRlihUnAwqFEgEFDoEUg0GHC4d8gUMFhXsMj0+FCodwghKXGhIjgRc4ZYMIQDwziEkBAQE X-IPAS-Result: A0BqAQDIVfFVmzbXVdFdDoNpaQaDIKkikmaHNAc8EAEBAQEBAQEBEAEBAQEBBgsLCSEugh2CBwEBBBIRHQEtCwEDDAEFBQsNAgIJHQICIhIBBQEKEgYTEgkHh3cDEg2pEYEwPjGLQYRlihUnAwqFEgEFDoEUg0GHC4d8gUMFhXsMj0+FCodwghKXGhIjgRc4ZYMIQDwziEkBAQE X-IronPort-AV: E=Sophos;i="5.17,503,1437429600"; d="scan'208";a="145338338" Received: from mail-la0-f54.google.com ([209.85.215.54]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/AES128-GCM-SHA256; 10 Sep 2015 12:09:56 +0200 Received: by lanb10 with SMTP id b10so24280964lan.3 for ; Thu, 10 Sep 2015 03:09:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=HE87ncaGYFF000S0xcD0V/Mq5ccEpPDtL3Rldv+Y/rI=; b=p2M1m78r9uhYdtkXKbw4f7HVh2H9m4pyAIHDiNOkEhiCLGFDgsc19unLY3GoWWe1vw rW+WRAn32wFlBbr4TuqeTaUZIiCn4RL87TMiK1edO6X3uGhmTedJGTr1Yk8X/Xojfw18 05pQ3TklcKlxV1JtMdBjObB2PyNozIF1gpTPuAFp540sAfE+cdI1LuLMZ9QhxwdB68oM 1hersP5GG2EPo8C1603/aQlzfJiKgh8dI0j7f3nGBVfTHmV3zhvIxbeeynXJgYaVElz8 vzh9Me89/PEYFRVs+MUmMo427AXULuUp9q5P0dx7EoGr5NJ2q+j6KzlQ2GwQQXZPwtB4 uBeA== X-Received: by 10.112.168.7 with SMTP id zs7mr35248372lbb.26.1441879795985; Thu, 10 Sep 2015 03:09:55 -0700 (PDT) MIME-Version: 1.0 Sender: fabrissimo@gmail.com Received: by 10.25.125.4 with HTTP; Thu, 10 Sep 2015 03:09:36 -0700 (PDT) In-Reply-To: <55F09806.1030507@nmt.edu> References: <55F09806.1030507@nmt.edu> From: Fabrice Le Fessant Date: Thu, 10 Sep 2015 12:09:36 +0200 X-Google-Sender-Auth: xYUQVxE-7S89waTgCfu2FDAgz8A Message-ID: To: John Christopher McAlpine Cc: Ocaml Mailing List Content-Type: text/plain; charset=UTF-8 Subject: Re: [Caml-list] Use of unit testing frameworks in OCaml One reason to avoid OCaml tests framworks for the compiler is probably that, if the compiler is broken, we still want to be able to run the testsuite, to break down the problem to the smallest failing test. If the test framework is written in OCaml and compiled by the failing compiler, it might not be able to run the tests at all. Maybe a solution would be to use a tests framework written for OCaml... but in another language :-) (which is currently the case, it is written in Makefiles...) --Fabrice On Wed, Sep 9, 2015 at 10:35 PM, John Christopher McAlpine wrote: > From what I can tell, the tests for the OCaml compiler and standard > libraries are all done with a fairly small framework designed specifically > for testing the compiler and standard libraries. Is there any particular > reason not to use a tool such as OUnit or Broken for these tests? I am aware > that adding dependencies to the compiler is generally frowned upon, but > these libraries could significantly improve the maintainability of the core > language and libraries. > > -- > Caml-list mailing list. Subscription management and archives: > https://sympa.inria.fr/sympa/arc/caml-list > Beginner's list: http://groups.yahoo.com/group/ocaml_beginners > Bug reports: http://caml.inria.fr/bin/caml-bugs -- Fabrice LE FESSANT Chercheur en Informatique INRIA Paris Rocquencourt -- OCamlPro Programming Languages and Distributed Systems