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 8: report needs stack trace on error
2 people starred this issue and may be notified of changes. Back to list
Status:  Fixed
Owner:  marc.es...@gmail.com
Closed:  Sep 2007
Cc:  virtix


 
Project Member Reported by marc.es...@gmail.com, Aug 6, 2007
What steps will reproduce the problem?
1. run this:
http://localhost:8501/mxunit/framework/tests/RemoteFacadeTest.cfc?method=runtestremote

What is the expected output? What do you see instead?
the two methods that fail don't report any trace, so it's hard for me to
track down the problem

i'd expect to see the entire tag context so that i can easily get at the
problem

Please use labels and text to provide additional information.


Aug 6, 2007
Project Member #1 marc.es...@gmail.com
scratch the URL above. try this one:
http://localhost:8501/mxunit/framework/tests/internal/ThrowsAnErrorTest.cfc?method=runtestremote
Aug 21, 2007
Project Member #2 virtix
Added stacktrace info to exceptions so line/col numbers now print. In addition, the 
message parameter as in assertTrue(message,expression) now prints as the message in 
the exception, as well as in the User Message section
Sep 22, 2007
Project Member #3 virtix
Refactored TestResult so that the primary datastructure is an array of structs that 
contain the test run results. The full stacktrace is easily accessible. Further, 
there is now an XMLTestResult object that extends TestResult. This is used by the 
runTestRemote method for generating quick html output on single test cases. 
Status: Fixed

Powered by Google Project Hosting