[arquillian-issues] [JBoss JIRA] (ARQGRA-301) Support for assertions on errors and console output

Brian Leathem (JIRA) jira-events at lists.jboss.org
Wed May 15 03:33:06 EDT 2013


    [ https://issues.jboss.org/browse/ARQGRA-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12774380#comment-12774380 ] 

Brian Leathem commented on ARQGRA-301:
--------------------------------------

If you look at the code sample I linked to, you'll see how I stored the js errors using the window.onerror listener.  I stored them in the DOM, for later retreival by Selenium, so I could make an assertion.  Graphene should be able to do this more cleanly, by string the errors in a suitable global and retrieving them with a suitable javascript interface.
                
> Support for assertions on errors and console output
> ---------------------------------------------------
>
>                 Key: ARQGRA-301
>                 URL: https://issues.jboss.org/browse/ARQGRA-301
>             Project: Arquillian Graphene
>          Issue Type: Feature Request
>            Reporter: Brian Leathem
>
> In a recent Graphene based test [\[1\]|https://github.com/richfaces/components/commit/857f73bbf87f495e36c33072c5c4415d4b02be10#L1R85] I registered a window.onerror listener to store errors in the DOM for later retrieval by Graphene/Selenium for use in an assertion.
> It would be great if Graphene could do this automatically, providing an API for accessing both error messages, and console output.
> [1] https://github.com/richfaces/components/commit/857f73bbf87f495e36c33072c5c4415d4b02be10#L1R85

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the arquillian-issues mailing list