[
https://issues.jboss.org/browse/ARQGRA-500?page=com.atlassian.jira.plugin...
]
Vsevolod Golovanov edited comment on ARQGRA-500 at 3/30/17 5:01 AM:
--------------------------------------------------------------------
Then again, some parameter provider class wouldn't know the context to decide on
parameters. Only the test does. Some location decider probably can get the current test
instance and call some callback on it. The test just needs to implement the interface
ParameterProvider - this would be the trigger. No need to alter the \@Location
annotation.
Upd: it's probably not possible to "get the current test instance" without
hardcoding some specific test framework like JUnit.
was (Author: vsevolodgolovanov):
Then again, some parameter provider class wouldn't know the context to decide on
parameters. Only the test does. Some location decider probably can get the current test
instance and call some callback on it. The test just needs to implement the interface
ParameterProvider - this would be the trigger. No need to alter the \@Location
annotation.
Navigation with URL parameters
------------------------------
Key: ARQGRA-500
URL:
https://issues.jboss.org/browse/ARQGRA-500
Project: Arquillian Graphene
Issue Type: Feature Request
Reporter: Vsevolod Golovanov
I need to add a dynamic URL parameter to a location of a page before navigating to it.
I don't want to use Selenium's navigation, because I would then need to
reinvent/shoehorn Graphene's location deciding.
A special landing page would be a pretty ugly workaround.
I get that it's not possible with annotations. But at least support this with
Graphene.goTo methods.
Actually it may be possible with annotations, if you could supply some provider class?
E.g. {{\@Location(value = "MyView.xhtml", parameterProvider =
MyParameterProvider.class)}}.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)