[JBoss JIRA] (ARQGRA-194) Mark a test so it will only run against certain browsers
by Brian Leathem (JIRA)
Brian Leathem created ARQGRA-194:
------------------------------------
Summary: Mark a test so it will only run against certain browsers
Key: ARQGRA-194
URL: https://issues.jboss.org/browse/ARQGRA-194
Project: Arquillian Graphene
Issue Type: Feature Request
Reporter: Brian Leathem
It would be useful to be able to annotate a particular test so it will only run when driven by a particular set of browsers.
Some sample use cases:
# Some tests cannot target the incomplete js impl found in html unit. I would mark such tests not to run when htmlunit is the configured browser (in CI for instance)
# Some tests may target non-standard behaviour in certain browsers (older IE versions for instance) and may not make sense to run in all browsers. I would mark such tests not to run only when IE is the configured browser.
--
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
11 years, 7 months
[JBoss JIRA] (ARQGRA-213) print contextpath and option to sleep after starting the @Deployment
by Mark Struberg (JIRA)
Mark Struberg created ARQGRA-213:
------------------------------------
Summary: print contextpath and option to sleep after starting the @Deployment
Key: ARQGRA-213
URL: https://issues.jboss.org/browse/ARQGRA-213
Project: Arquillian Graphene
Issue Type: Feature Request
Reporter: Mark Struberg
Most graphene unit test have a @Deployment section and something similar to the following:
{code}
@ArquillianResource
private URL contextPath;
{code}
When debugging the Server for finding the bug in the webapp it's often needed to manually click through the application and invoke requests directly. But to do that you need the contextpath! It would be nice if Arquillian Graphene would log this information.
Another highly useful feature would be to stop the test after a @Deployment via a -D java option. Currently I need to add a Thread.sleep(600000L) to my test manually if I like to test the server. If I don't do that Selenium aborts the test with a failure after 30s if I'm debugging the server.
--
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
11 years, 7 months
[JBoss JIRA] Created: (ARQAJO-67) Reduce logging levels
by Karel Piwko (JIRA)
Reduce logging levels
---------------------
Key: ARQAJO-67
URL: https://issues.jboss.org/browse/ARQAJO-67
Project: Arquillian Ajocado
Issue Type: Feature Request
Components: junit, testng
Affects Versions: 1.0.0.Alpha2
Reporter: Karel Piwko
Assignee: Lukáš Fryč
Ajocado outputs many debug information under INFO logging level. This level should be reduced to debug or even debug/fine.
It makes execution of the test slower and this information is not required until debugging.
It manifest namely with JUnit which redirects test output to console.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 7 months