[phc-internals] Expected test results

[Paul Biggar]

Good point. The simplest thing to do is just run:

    make check

Alternatively, run:

    test/framework/driver.php --help

to see the options for running the tests.


Paul

On Sun, Oct 10, 2010 at 11:13 PM, Andrei Alvares <logytech at gmail.com> wrote:
> Nice job Paul. Could you please add a simple how-to to show how to run
> the tests? I believe I could really use it. (;
>
> On Sun, Oct 10, 2010 at 7:08 PM, Paul Biggar <paul.biggar at gmail.com> wrote:
>> Hi folks,
>>
>> I've been cleaning up some of the bitrotten code recently, and needed
>> to keep track of it. So I added a few small changes which allow us to
>> tell whether we broke a test, or whether it was broken already.
>>
>> test/expected_results/ contains what we expect to happen when we run
>> the tests. After tests run, the test driver now diffs the results
>> against the expected results, and says whether or not it differs. This
>> is very coarse, but it kinda works. The disadvantage is that we must
>> run the full set of tests to have something to compare.
>>
>> After making a change which fixes some tests, you can run
>> misc/copy_expected to copy the latest results over test/expected/*,
>> which should be committed along with the fix.
>>
>> Let me know if this is helpful, and please submit any tweaks you find useful.
>>
>> Thanks,
>> Paul
>>
>> --
>> Paul Biggar
>> paul.biggar at gmail.com
>> _______________________________________________
>> phc-internals mailing list
>> phc-internals at phpcompiler.org
>> https://nova.villiros.com/cgi-bin/mailman/listinfo/phc-internals
>>
>



-- 
Paul Biggar
paul.biggar at gmail.com