Velo? Logan? Did you get a chance to read this post?

This is quite a big deal - if your tests fail without stack traces it
really slows you down trying to find the problem.

Have you been able to reproduce this or am I doing something stupid?

thanks,

Neil

On Jan 29, 3:17 pm, neil thorne <[email protected]> wrote:
> Hi,
>
> I read here
>
> http://blog.flex-mojos.info/2008/11/09/advanced-unit-testing-support-...
>
> that stacktraces should now be available when running say FlexUnit
> tests. Am I right in thinking this means that when a failure occurs
> within my test I should be able to see a full stack trace with line
> numbers?
>
> I'm using 2.0.3 and I always get just the first line of the error
> message.
>
> eg. I checked out the following test-harness example from
>
> http://svn.sonatype.org/flexmojos/tags/flex-mojos-2.0.3/test-harness/...
>
> and modified the pom just a little (just changed the variable flex-
> mojos.version to hardcoded '2.0.3').
>
> I was then able to run mvn clean test and inspect the surefire
> reports. Here's the TestCalculator2 test results.
>
> testsuite errors="1" failures="1"
> name="com.adobe.example.TestCalculator2" tests="3" time="0.0">
> - <testcase name="testFail" time="0.0">
>   <failure message="expected:<10> but was:<8>"
> type="flexunit.framework::AssertionFailedError" />
>   </testcase>
> - <testcase name="testError" time="0.0">
>   <error message="An second error" type="Error" />
>   </testcase>
>   <testcase name="testPass" time="0.0" />
>   </testsuite>
>
> Wouldn't we expect a bigger stack trace for the "An second error"?
>
> best regards,
>
> Neil
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Flex Mojos" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/flex-mojos?hl=en?hl=en

http://blog.flex-mojos.info/
-~----------~----~----~----~------~----~------~--~---

Reply via email to