Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

One test method cannot trigger another failing, synchronous test method (in another Runner) without a RTE #1

Closed
GoogleCodeExporter opened this issue Mar 13, 2015 · 5 comments

Comments

@GoogleCodeExporter
Copy link

1. Create and run a test method (i.e.
TestMethodExecution.testAllMetaDataMethodsExecuted)
2. Within the said test method, create and run another Runner with an
assertion that fails synchronously

An uncaught Flash Error is displayed (in the debug Flash player). This is
because the Wrapper for the first test method has not completed execution
of its method before the second test method failed.

Original issue reported on code.google.com by boynamed...@gmail.com on 13 Mar 2008 at 3:33

@GoogleCodeExporter
Copy link
Author

Original comment by boynamed...@gmail.com on 13 Mar 2008 at 3:53

  • Changed title: One test method cannot trigger another failing, synchronous test method (in another Runner) without a RTE

@GoogleCodeExporter
Copy link
Author

This one may not be fixable, since ActionScript does not allow you to set a 
default
error-handler (and the Error in question is being thrown after an event is 
dispatched).

Original comment by boynamed...@gmail.com on 13 Mar 2008 at 11:27

@GoogleCodeExporter
Copy link
Author

Perhaps the RunNotifier could be made aware of all associated ITestWatcher 
classes.
Then, instead of notifying them via an Event, it could call methods on them 
directly
and inform them of what has happened.

In this situation, catching a resulting Error would be possible.

Original comment by boynamed...@gmail.com on 13 Mar 2008 at 11:30

@GoogleCodeExporter
Copy link
Author

Upon further review of this issue, I'm not sure it's worth resolving. It may be 
fair
to make the assertion that runtime errors and/or assertion failures can *only* 
occur
within (a) the test method itself or (b) one of the wrapped event handlers 
(created
using addAsync).

Original comment by boynamed...@gmail.com on 15 Mar 2008 at 3:07

@GoogleCodeExporter
Copy link
Author

Original comment by boynamed...@gmail.com on 13 Apr 2008 at 9:58

  • Changed state: WontFix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant