[arquillian-issues] [JBoss JIRA] Commented: (ARQ-437) Introduce annotation to control lifecycle of selenium session

[Karel Piwko (JIRA)]

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

Karel Piwko commented on ARQ-437:
---------------------------------

Lukas,

If was thinking about this: You can't configure this via an annotation as during the BeforeSuite event you have no idea what files are in the suite and thus you can't go through source code creating appropriate browser instances. It is difficult to get this added to Arquillian runners, as JUnit has no {After,Before}Suite events.

So only thing actually available in BeforeSuite event is configuration from arquillian.xml. So I can create a Drone Extension, which if activated, creates all instance in BeforeSuite and TestEnricher will later inject all field instances from SuiteScope context. If no browser instance is found, it will safely fail.

This means that you will have possibility to use either BEFORE_SUITE + BEFORE_METHOD or BEFORE_CLASS + BEFORE_METHOD browsers, latter being the default. Do you find this usable?

Proposed extension:
{code:xml}
<extension qualifier="drone-lifecycle">
    <property name="browser-lifecycle">suite|class</property>
</extension>
{code}

WDYT?


> Introduce annotation to control lifecycle of selenium session
> -------------------------------------------------------------
>
>                 Key: ARQ-437
>                 URL: https://issues.jboss.org/browse/ARQ-437
>             Project: Arquillian
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Extension - Drone
>            Reporter: Lukáš Fryč
>
> Following options are being considered:
> BEFORE_SUITE
> BEFORE_CLASS
> BEFORE_METHOD

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira