mxunit Google Group

Re: Testing code

2008-07-24T16:41:43Z

Well the problem is that cfabort is not an exception. It just halts
processing and flushes the output buffers (and maybe a little under
the hood housekeeping).

I'm not sure I understand what type of logic you're going for, but you
can get the behavior you are describing using cfthrow instead of

Re: [mxunit:660] Testing code

2008-07-23T19:21:42Z

Maybe this is a "test smell", i.e. the inability to test it indicates
that possibly abort shouldn't be used? is there a different/better way
to do what you want to do without aborting? possibly throwing a
different kind of custom exception? "needing" an abort for
functionality just seems weird to me.

Re: [mxunit:663] Spam Issues on MXUnit List

2008-07-19T11:28:56Z

cool... I was going to send a message to you all about this today... thx billy
Timothy Farrar

Spam Issues on MXUnit List

2008-07-19T10:21:21Z

All,

We've been getting one or two spam postings per day for about the last
week. It's annoying to you and me, and it's cumbersome to report the
message, ban the member, and then delete the message. I see that this
will likely only get worse. So, the immediate resolution is to
moderate all new member's messages. The group is still open to anyone

Re: this scope in generated tests

2008-07-19T02:24:13Z

Thanks for the answers. I'll have to test that issue with variables
scope. Always something new.

And yes I saw that I can make my own test generator template. It's
great. I like tools like this one... 1..2..3.. and you got
something ... I wish they all were like that. :-)
I know one I am working on probably won't be

Testing code

2008-07-18T18:54:50Z

Howdy Folks,

I have become a big fan of TDD with MXUnit, but I have come up against
a problem that I am hoping someone here might have experience with or
insight on. I am trying to test a template that has code in it that
does a <cfabort>. My hope was to catch the <cfabort> exception
("coldfusion.runtime.AbortExce ption") either in a catch block or even

Re: this scope in generated tests

2008-07-18T18:07:44Z

Hi Ilya,

There is a somewhat obsure reason why the generated tests are using
the this scope. It has to do with some strange behavior that occurs
when you attempt to run a test against an inherited method. I don't
remember all the particulars, but essentially, running a test against
an inherited method by referencing the variables scope won't see the

Re: [mxunit:656] Re: strange mxunit issue on Leopard - left character missing resolving component

2008-07-18T15:34:10Z

well.... that was easy enough!

thanks for sticking with it Fred.

Marc

Re: strange mxunit issue on Leopard - left character missing resolving component

2008-07-18T15:31:10Z

Fixed!! Many thanks Marc.

oh, you've been immortalized in one of the testcases in the plugin
code:

Fame at last :)

Re: [mxunit:653] Re: strange mxunit issue on Leopard - left character missing resolving component

2008-07-18T15:10:23Z

hey fred, i just put a new version of the plugin on the update site.
Can you give it a shot?

I was able to duplicate your problem in a test case if i added a space
to the webroot. this problem, after looking at it, definitely had the
feel of a string not being trimmed somewhere.

so i added some stuff, got the test to pass. let's see if that fixes it.

this scope in generated tests

2008-07-18T14:49:20Z

I used a cool test generator you guys included with MXUnit and noticed
it's creating an instance of a component being tested in "this" scope,
in setUp method. Just wanted to ask if there is any particular reason
it's not variables scope?
I realize it's probably very minor thing, at first I just glazed over

Re: strange mxunit issue on Leopard - left character missing resolving component

2008-07-18T14:37:02Z

Edit for last post:

Mxunit preferences: (both resolve ok)

URL to remote facade:

[link]

Web root directory:

/Users/fredlee/projects/wwwroo t

Re: strange mxunit issue on Leopard - left character missing resolving component

2008-07-18T14:33:53Z

Hi Marc,

/users/fredlee/projects/waythr ough/wwwroot, right?

Sure was. I've re-arranged my folder structure to be:

/users/fredlee/projects/wwwroo t/waythrough
/users/fredlee/projects/wwwroo t/mxunit
/users/fredlee/projects/wwwroo t/tests

(Apache re-configured to point at the new wwwroot location)

Re: [mxunit:650] Re: strange mxunit issue on Leopard - left character missing resolving component

2008-07-18T14:12:16Z

Vacation? How dare ya . . . You think 1.1's gonna write itself :-)

Thanks for all the hard work!

Best Wishes,
Peter

Re: [mxunit:648] Re: strange mxunit issue on Leopard - left character missing resolving component

2008-07-18T14:06:10Z

thanks fred!