Home › projects › OEUnit - Unit Testing Framework › Releases

OEUnit - Unit Testing Framework 1.2

Sun, 2011-02-20 08:41 — cwills
Download: OEUnit-1.2.zip
Size: 183.64 KB
md5_file hash: c9e7ddd4fb1dd5ca7773f33ac9382293
First released: Sun, 2011-02-20 08:41
Last updated: Sun, 2011-02-20 08:39

Updated for OpenEdge 10.2b (Required)
Includes other minor changes and improvements to framework documentation


Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Tue, 2011-07-19 19:08 — JohanSamyn

Result window not showing

Hi Cameron,
When running a testclass using the OEUnit.Runners.Runtest method, the results window is closed almost immediately. I see it being shown very briefly, but it then disappears without me being able to read the results. I tried this from within the OpenEdge Architect, where the Run-As-Test editor context menu method works fine. Any idea what could be wrong ?
Regards,
Johan


Thu, 2011-07-21 03:33 — cwills

RE: Result window not showing

It sounds like OpenEdge Architect is cleaning up the result window straight after running the tests.
What version/platform of OpenEdge Architect are you running? Any service packs?

Cheers,


Thu, 2011-07-21 13:14 — JohanSamyn

RE: Result window not showing

I'm running OpenEdge 10.2B SP4. On a Win 7 Professional SP1 platform. The Eclipse reports to be eclipse.buildId=M20090211-1700. With no extra plugins installed by me into the OpenEdge Architect Eclipse. Let me know if you need more info.
I do remember having succeeded doing this, but it could well be before my upgrade to 10.2B SP4. Could this be another change caused by going to SP4 ?
-- Johan


Tue, 2011-07-19 18:55 — JohanSamyn

Erroneous example for @test(expected="ErrTypeName") ?

Hi Cameron,
I've been playing a little with OEUnit. Had some trouble trying out the @Test(expected="ErrTypeName") feature. I passed in "Progress.Lang.AppError", as shown in the example in the documentation, but that did not work. I did succeed however using only "AppError", after some digging through the code. So maybe it would be a good idea to modify the docs accordingly ? Unless I missed something of course.
Regards,
Johan


Thu, 2011-07-21 03:28 — cwills

RE: Erroneous example for @test(expected="ErrTypeName")

Hi Johan,

I'm not sure why the test didn't pass with the full error name: Progress.Lang.AppError.
I've just run the test below and it passed.. Perhaps its cultural settings within the OE runtime?


ROUTINE-LEVEL ON ERROR UNDO, THROW.

CLASS Test:

@Test(Expected="Progress.Lang.AppError").
METHOD PUBLIC VOID ThrowsError():
RETURN ERROR NEW Progress.Lang.AppError("error").
END METHOD.

END CLASS.


Thu, 2011-07-21 12:17 — JohanSamyn

RE: Erroneous example for @test(expected="ErrTypeName")

Hmm, a bit weird, but your are right, Cameron. This little test, and my own existing similar test, both pass without a problem now. Only thing I can think of is my upgrading to OpenEdge 10.2B SP4 since my failing attempt. Well, it works now, let's not bother any further. Thanks.