PCT and OEUnit integration based on current release of OEUnit 1.3 and Jamie Townsend's version of OEUnit that supports PCT.

I've found old version of OEUnit that supports PCT here:
http://www.oehive.org/node/1881

I had to do some minor changes to integrate this with current release of
OEUnit 1.3. Fixed error: "Unable to evaluate expression for PUT
statement."

Tested in OpenEdge Architect and run from command line, which was main
goal - automate unit testing with PCT.

My first commit to GitHub so please be gentle. I tried to push my
changes to CameronWills repository but unfortunately it is read-only.
Therefore, forked it here.
Add in methods to count the number of tests present in the results
Implement Reporter base class, and inherited JUnit reporter
Merge pull request #2 from msabbott/master

Count Number of Tests & Add JUnit XML format reporting to OEUnit
Some minor refactoring to follow
Merge pull request #1 from iaforek/master

Merged PCT support. Some refactoring to follow
Version 1.4

Refactored merged changes to remove redundant code sections and folder
structure
Removed 'Author' from the file headers - a leftover relic from a heading
template and not conducive to social coding :)
Tested with OpenEdge 11.3 on Windows 7 64bit
Fixing Comments

Fixing some of the header comments, copy and paste mistakes
Create base FileReporter class for reports which are sent to one file.
Implement a basic Text format reporter and a CSV format reporter.
Correct missing ROUTINE-LEVEL ON ERROR UNDO, THROW statement from BaseReporter
Refactor JUnitReporter to use FileReporter as a parent class
Update documents to show how to report the results of testing runs.
Add missing ROUTINE-LEVEL ON ERROR UNDO, THROW. in JUnitReporter
Merge pull request #3 from msabbott/master

More Reporters, Some Refactoring, Documentation
Add Rerun procedure for Progress Developer Studio

Some users would like to rerun the last test using a keyboard shortcut,
whilst perhaps having some other file open in the editor or even the
editor closed. To resolve I have added a new procedure that can be run
from Progress Developer Studio to rerun the last test and display the
results.
Resolves #4
Adding link to new Releases page, and updating requirements in documentation.
Fixed assertions for undefined logicals

Fixed bug where Assert:IsTrue(?) and Assert:IsFalse(?) both returned
true, these should return false and the null/undefinied value (?) is
neither true nor false.
Fixes #6
Remove noisy lines from error call stack

The callstack for a simple AssertionFailedError included a lot of lines
detailing the plumbing of OEUnit which makes it difficult to quickly
find which line number the actual error was thrown from - this is
particularly important when a lot of assertions are grouped inside a
test method. This change removes/filters the call stack of the error
objects to show calls from within the user's code - i.e. not OEUnit.
Added a ToString method to only output errors
added r code so others don't have to compile the program