Proposal: Remove Application.cfm

[Randy]

I propose that we remove the main Application.cfm file from the
repository/project. Looking at it the only thing in the file is:

<cfapplication name="MXUnitFramework"
applicationtimeout="#CreateTimeSpan(0,1,0,0)#"
sessionmanagement="true">

The reason for suggesting that we remove it is so that dynamic
mappings will work correctly with unit tests.

The only thing that gives me pause in removing the Applciation.cfm is
the sessionmanagement=true but after searching through the code it
appears that Sessions aren't used anywhere, so there is not a need for
them.

The only real requirement for running MXUnit is to have it reside in
the root or have the /mxunit mapping so that the tests will run
correctly. By removing the Applicaiton.cfm file it allows the
directory that contains the mxunit to set the dynamic mappings
negating the need for hard-coded mappings in the administrator.

I would encourage people to test it out by deleting the
Application.cfm file from the mxunit directory and see if it has any
issues with their setup.

Any thoughts or reasons this would cause massive problems?

Thanks!

Randy

[Marc Esher]

No objections here.

Though I think all the same it'd be a good idea to have folks remove that directory from their framework install, run their existing tests, and confirm nothing bad happened

[Randy]

I haven't had any troubles so far from removing the application.cfm
file. it works fine with the Eclipse plugin and in the browser.

Anyone else tried removing it and had any issues?

Randy

[Marc Esher]

This broke the ant run, so I made a small change to the JUnitTestResult and now everything's working as expected for me.

marc

[Nick Kaijaks]

Tests run fine in my environment (where mxunit isn't at the webroot) with Application.cfm deleted.

Nick

> Though I think all the same it'd be a good idea to have folks remove that
> directory from their framework install, run their existing tests, and
> confirm nothing bad happened

--
Scanned for Warwick Business School by iCritical.

[Randy]

From what I am hearing it doesn't seem to break anything, other than
the fix that Marc did to the JUnitTestResult. Should we remove it from
the trunk to test it out on a broader scale before the next release?

Randy

[Mark Mandel]

The way I've been doing this, is having a cfc that extends the HttpTestRunner and/or the RemoteFacade CFC in the directory that I want my unit tests in.

Works a treat

Mark

--
E: mark....@gmail.com
T: http://www.twitter.com/neurotic
W: www.compoundtheory.com

[Marc Esher]

+1 for removing

[bill shelton]

adios, application.cfm.

On Sep 7, 8:42 am, Marc Esher <marc.es...@gmail.com> wrote:
> +1 for removing
>

> On Thu, Sep 3, 2009 at 8:50 PM, Mark Mandel <mark.man...@gmail.com> wrote:
> > The way I've been doing this, is having a cfc that extends the
> > HttpTestRunner and/or the RemoteFacade CFC in the directory that I want my
> > unit tests in.
>
> > Works a treat
>
> > Mark
>

> > On Fri, Sep 4, 2009 at 10:48 AM, Randy <zoram...@gmail.com> wrote:
>
> >> From what I am hearing it doesn't seem to break anything, other than
> >> the fix that Marc did to the JUnitTestResult. Should we remove it from
> >> the trunk to test it out on a broader scale before the next release?
>
> >> Randy
>
> > --

> > E: mark.man...@gmail.com

[John Allen]

+1 for removing.

[Randy]

Sweet! Lets get rid of it and see if anyone notices any problems
before the next release.

Randy

[Randy]

The application.cfm is now removed from the trunk. If anyone has any
issues please post them to the group so we can get them resolved.

[Shannon]

Randy,

I didn't have any problems from my web based test runner, but tests in
my Eclipse plugin failed left and right . This may be just my
environment(see my post on <a href="http://groups.google.com/group/
mxunit/browse_thread/thread/7c04f62c810bb9e1#">Application.cfm and
Eclipse Plugin</a>). But it seems that tests run via the Eclipse
plugin were only seeing the MxUnit application and not my SUT
application and they were also not executing the setup() method in my
TestCase. You may want to check this for yourself to verify that this
is only a problem on my system.

For example, my TestCase contains:
<cffunction name="setup" access="public" output="no"
returntype="void">
<cfset Application.db = "myDB"> <!--- added to handle running tests
in Eclipse --->
</cffunction>

But I still got "Expression: Element DB is undefined in APPLICATION"