Mxunit / Test folders

[russplaysguitar]

So I see there is an mxunit folder and a test folder. Do we need both of these? It makes it a little confusing when looking for the tests...

[jfrux]

Ya, I did that for the assets because I forgot how to get the assets to
load... I prefer just to have a test folder since it kind of has become
sort of a standard.

The mxunit is just for CSS/js of the test suite... Let me know how to map
that and we can remove it

Sent from my iPhone

On Oct 6, 2012, at 3:57 PM, Russ notifications@github.com wrote:

So I see there is an mxunit folder and a test folder. Do we need both of
these? It makes it a little confusing when looking for the tests...

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/11.

[russplaysguitar]

I think you just make a mapping to mxunit, right? or put it in your webroot?

[jfrux]

I made a mapping to /mxunit correct, but it doesn't map the web assets like css/js

[russplaysguitar]

Can't you just put the web assets in webroot too?

[jfrux]

maybe it's an issue with railo?
for some reason, railo mappings only work for components and internal stuff, not http accessable web assets...
so you can't go to localhost:8888/mxunit/cssfile.css and expect it to load on each new instance

[atuttle]

Mappings don't work for non-CFML files in ACF either. CF (be it ACF, Railo, etc) doesn't get the opportunity to respond when you request .css/.js/etc, so it can't use mappings.

Just put the mxunit folder in your web root and call it a day. :)