Test all errors and outputs

[pbiggar]

We nearly have a framework for testing all outputs, so we'll be able to
test errors. Every phc_error and phc_warning should be tested.

Original issue reported on code.google.com by paul.biggar on 2007-11-20 15:09:29

[pbiggar]

Basically, we need to add tests to the test/subjects/phc/ directory, which have
deja-gnu style entries to indicate the error expected. 

Original issue reported on code.google.com by paul.biggar on 2008-09-06 16:24:17

[pbiggar]

Its trivial, it'll just take time.

Original issue reported on code.google.com by paul.biggar on 2008-09-06 16:24:44

• Labels added: Difficulty-Trivial
• Labels removed: Difficulty-Medium

[pbiggar]

(No text was entered with this change)

Original issue reported on code.google.com by paul.biggar on 2008-09-14 09:42:08

• Labels added: Component-Testing

[pbiggar]

Is this issue still open for a beginner's contributor ?

Original issue reported on code.google.com by alain091 on 2011-09-18 10:27:00

[pbiggar]

Yes, and it's very easy. Grep through the code to find "phc_error" and "phc_warnings",
write code to trigger them, and write test cases for them (see existing examples in
test/subjects/phc/).

Original issue reported on code.google.com by paul.biggar on 2011-09-18 15:21:43