My favorites | Sign in
Project Home Downloads Source
READ-ONLY: This project has been archived. For more information see this post.
Search
for
  Advanced search   Search tips   Subscriptions
Issue 2: AddTrace appears on wrong method.
2 people starred this issue and may be notified of changes. Back to list
Status:  Fixed
Owner:  AnodyneP...@gmail.com
Closed:  Jun 2007


 
Project Member Reported by AnodyneP...@gmail.com, Jun 6, 2007
What steps will reproduce the problem?
1. Added the addTrace() call to a test method.

What is the expected output? 
I expected to see the string in the addTrace method reflected in the output
next to the method it was called in.

What do you see instead?
The output appeared in the output for a different method and seemed to be
affected by the success or failure of individual tests.

It's quite possible that I introduced this bug when I made a change to the
framework/TestSuite.cfc file to get it to work.  There was a line of code
that handled the adding the trace to the results that appeared between the
try block and the first catch block (around line 252). I added it to both
catch blocks.


Jun 10, 2007
Project Member #1 virtix
Yep. Appears to occur when test cases are run in the context of a testSuite. Seems 
ok when running a single testCase. Most likely can be traced back to a design flaw.
Status: Accepted
Jun 10, 2007
Project Member #2 virtix
Ok. Disregard previous comment. What happened, is that a while back I was trying to 
get addTrace() to execute even if there was an exception thrown. Durring this 
effort, I was moving addTrace() around and placed it before the call to evaluate
("o." & methodName & "()");, which, was the cause. So, I moved addTrace() back to 
after this call, and it appears to work as previously determined. But, it still does 
not print when an exception occurs. I'll create another issue for that.

Cheers ... bill
Status: Fixed

Powered by Google Project Hosting