| Issue 19: | Accessing ComponentUtils fails when framework is not directly under webroot | |
| Back to list |
What steps will reproduce the problem? 1. Install MXUNIT in a webroot sub-directory; e.g., /apps/mxunit 2. Run any sample test What is the expected output? What do you see instead? Sample tests should execute fine, but exception is thrown trying to find mxunit.util.ComponentUtils Resolution: Find a way to invoke ComponentUtils irregardless of it's location OR place ComponentUtils in the framework package.
Oct 6, 2007
Project Member
#1
virtix
Oct 7, 2007
Playing aroud this morning with sniffing out the install root from TestCase
constructor with the assumption *all tests must extend
some.form.of.mxunit.framework.TestCase*. So, finding where mxunit is installed at
runtime should be simple. I'll update the repository with TestCase, that will have a
property that can be used by the framework or plugin to instantiate objects based on
this property. E.g., createObject("component", evaluate(this.installRoot
& ".mxunit.framework.TestResult")) or createObject("component", evaluate
(this.installRoot & ".mxunit.util.ComponentUtils")) ...
Cc:
virtix
Oct 19, 2007
Moved ComponentUtils into framework package and altered dependencies. All seems well, but we should validate with an eclipse build.
Oct 30, 2007
(No comment was entered for this change.)
Status:
Fixed
|