<div dir="ltr"> <div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> > 3) Hard to get a message about what failed if the predicate only succeeds of fails. I save off results instead of pushing IO into the test harness though. I felt it made more sense. I also don’t like pushing IO through the test cases, but I didn’t accomplish to put test cases into a list. After reading in the reference manual section 8.3, that higher-order terms can cause problems in polymorphic collection types, I gave up my try to collect test cases in a list. </blockquote><div>I'm not using Polymorphism. <pre>:- type test_result <a name="cl-53"></a> ---> test_result(result_test_name::string, <a name="cl-54"></a> result_test_disposition::test_disposition). <a name="cl-55"></a></pre> </div><div>Eventually, I'll want to flesh that out with things like the hostname, startTime, stopTime, etc... but this is all I needed for no </div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> For a simple XML parser, I wrote dozens of test cases like these: %% testDCG(TestNo, DCG-predicate, InputToBeParsed, ExpectedResult, !IO) testDCG(1, nameStartChar, ":", yes(':'), !IO), testDCG(2, nameStartChar, "-", no, !IO), testDCG(3, nameChar, "-", yes('-'), !IO), testDCG(4, name, "Name", yes("Name"), !IO), testDCG(5, attValue, "\"AttValue\"", yes("AttValue"), !IO), testDCG(6, attribute, "attribute=\"Value\"", yes({"attribute", "Value"}), !IO), … I don’t understand the syntax of test_case yet. Could you please give me an example, how I can write a list of test cases for different DCG predicates? </blockquote> </div><div class="gmail_quote">You don't pass in the predicate-under-test as a parameter, instead you build a test predicate and call predicate-under-test from there. </div><div class="gmail_quote">Below is an example of test cases defined in terms of named predicates, instead of lambdas. I am currently No Good at DCGs, but I'll write something similar to what I think you're first test does and hopefully you can figure out how to adapt it. </div><div class="gmail_quote"><pre>:- pred pass_test(test_disposition::out) is det. <a name="cl-13"></a>pass_test(Disposition) :- <a name="cl-14"></a> Disposition = pass. <a name="cl-15"></a> <a name="cl-16"></a>:- pred fail_test(test_disposition::out) is det. <a name="cl-17"></a>fail_test(Disposition) :- <a name="cl-18"></a> Disposition = fail("Fail tests aways Fail"). </pre><pre>:- pred name_start_test(test_disposition::out) is det. name_start_test(Disposition) :- nameStartChar(":someString" OutStartChar), ( if OutStartChar = ":" then Disposition = pass else Disposition = fail("Expected StartChar to be : But got " ++ OutStartChar ++ " instead" ). </pre><pre> TestList = [ <a name="cl-51"></a> test_case("PassTest", pass_test), <a name="cl-52"></a> test_case("FailTest", fail_test), test_case("NameStartTest), name_start_test) ] </pre> </div><div class="gmail_quote">the if...then...else in name_start_test could have been a call to assertions.are_equal instead: </div><div class="gmail_quote">name_start_test(Disposition) </div><div class="gmail_quote"> nameStartChar(":someString", OutStartChar), </div><div class="gmail_quote"> assertions.are_equal(univ(":"), univ(OutStartChar), Disposition). </div><div class="gmail_quote"> </div><div class="gmail_quote">Cheers! </div><div class="gmail_quote">Charles </div></div></div>