| Issue 29: | setStyle() appears to have no affect when using runtestremote() | |
| 1 person starred this issue and may be notified of changes. | Back to list |
What steps will reproduce the problem? 1. http://localhost:8500/mxunit/tests/framework/AssertTest.cfc? method=runtestremote 2. See all failed tests (and dump in #6). 3. Message and actual param seemed to be swapped ... normalize() issue? What is the expected output? What do you see instead? All tests should pass, which is what happens when running with the pluggin. But not in runtestremote. Getting coffee ... maybe solution will appear after more caffeine ;-)
Nov 29, 2007
Note: Also seems to occur when running Ant task.
Nov 29, 2007
ah, i think i see what's going on. this appears to be related to the setup/teardown
issues. AssertTest does setTestStyle("default") in setUp so that it always gets
reset. probably what's happening is that some test is calling setTestSTyle("cfunit")
and then all the other tests are running with that style since it's not getting reset.
Nov 29, 2007
fixed. I added a setTestStyle("default") into tearDown and that, coupled with the
fixes to TestSuite that ensure setUp and tearDown are run, did the trick
Status:
Fixed
Owner: marc.esher |
without looking at your tests, I can tell you that if you use named arguments, setTestStyle() isn't necessary. it's only necessary wehn you have this: <cfset assert("message",expected,actual)> if you have <cfset assert(message="message",expected=1,actual=SomeVar)> then you definitely don't want to use setTestStyle(). Is that the problem?