[JBoss JIRA] (ARQGRA-282) Create Graphene guide on arquillian.org
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-282?page=com.atlassian.jira.plugin... ]
Juraj Húska edited comment on ARQGRA-282 at 3/26/13 9:29 AM:
-------------------------------------------------------------
IMHO it can be done in this way:
* change the feature reference _Drive the Browser_ from [here|http://arquillian.org/features/], to contain _Graphene_ reference. It would be nice to have there also Graphene logo (ARQGRA-69)(together with Drone logo)
* reuse and alter the already existing [functional testing using drone|http://arquillian.org/guides/functional_testing_using_drone/], because IMHO there are valuable parts, which are needed (_Assumptions_, _Introducing Client Mode_, _Enabling Client Mode_, _Drone Overview_). So dropping the whole guide is not a good option for me.
* it can be done in a similar way as the [guide for JPA testing|http://arquillian.org/guides/testing_java_persistence/] is done. So _Introducing the application we are going to write tests for_, _Preparation for testing with Graphene_, _Developing tests_, _Running the tests_
* basically I have not recognized other candidates from Lukas's ones, I just ordered them in the outline.
The guide outline itself can look like:
# Assumptions
# Introducing Client Mode
# Enabling Client Mode
# Drone Overview
## There are mentioned all the browsers drivers Drone currently has support for, we can emphasize _Graphene_ here and say that we are going to setup a test suite project with use of it from now on.
# Introducing the application we are going to write tests for
## We can show how to develop a simple _HTML 5_ page, which will use _AJAX_ calls to retrieve backend data from _JAX-RS_ endpoints.
## *Or* we can reuse again the _JSF_ sample which is already there, logging fragment, and to add some parts to easily showcase _Graphene_ features on it. My concert here is the _JSF_. I would like to showcase that _Graphene_ can be used with all front end frameworks and most importantly with now most coolest POH5 applications. By this IMHO we can get much bigger audience.
## It does not have to be all in this guideline. There can be just snippets from whole Graphene showcase, which will be developed as well. (ARQGRA-174)
# _Graphene_ scaffolding
# Senium server setup, remote reusable, chrome browser -> fast development turnaround
# Developing tests
## Showcasing some of the _Graphene_ features: _request guards_, _fluent waitings_, _Page Ojects_, _Page Fragments_
## This should be probably the biggest part of the guideline. My concern here is that it will be too big. On the other side I do not have a major problem with it. IMHO the navigation which is used in arquillian.org is quite clear and that the platform is suitable for long posts as well.
# Running and debugging the test in IDE
# Best practices from developing and running tests
What do you think guys ?
was (Author: jhuska):
IMHO it can be done in this way:
* change the feature reference _Drive the Browser_ from [here|http://arquillian.org/features/], to contain _Graphene_ reference. It would be nice to have there also Graphene logo (ARQGRA-69)(together with Drone logo)
* reuse and alter the already existing [functional testing using drone|http://arquillian.org/guides/functional_testing_using_drone/], because IMHO there valuable parts, which are needed (_Assumptions_, _Introducing Client Mode_, _Enabling Client Mode_, _Drone Overview_). So dropping the whole guide is not a good option for me.
* it can be done in a similar way as the [guide for JPA testing|http://arquillian.org/guides/testing_java_persistence/] is done. So _Introducing the application we are going to write tests for_, _Preparation for testing with Graphene_, _Developing tests_, _Running the tests_
* basically I have not recognized other candidates from Lukas's ones, I just ordered them in the outline.
The guide outline itself can look like:
# Assumptions
# Introducing Client Mode
# Enabling Client Mode
# Drone Overview
## There are mentioned all the browsers drivers Drone currently has support for, we can emphasize _Graphene_ here and say that we are going to setup a test suite project with use of it from now on.
# Introducing the application we are going to write tests for
## We can show how to develop a simple _HTML 5_ page, which will use _AJAX_ calls to retrieve backend data from _JAX-RS_ endpoints.
## *Or* we can reuse again the _JSF_ sample which is already there, logging fragment, and to add some parts to easily showcase _Graphene_ features on it. My concert here is the _JSF_. I would like to showcase that _Graphene_ can be used with all front end frameworks and most importantly with now most coolest POH5 applications. By this IMHO we can get much bigger audience.
## It does not have to be all in this guideline. There can be just snippets from whole Graphene showcase, which will be developed as well. (ARQGRA-174)
# _Graphene_ scaffolding
# Senium server setup, remote reusable, chrome browser -> fast development turnaround
# Developing tests
## Showcasing some of the _Graphene_ features: _request guards_, _fluent waitings_, _Page Ojects_, _Page Fragments_
## This should be probably the biggest part of the guideline. My concern here is that it will be too big. On the other side I do not have a major problem with it. IMHO the navigation which is used in arquillian.org is quite clear and that the platform is suitable for long posts as well.
# Running and debugging the test in IDE
# Best practices from developing and running tests
What do you think guys ?
> Create Graphene guide on arquillian.org
> ---------------------------------------
>
> Key: ARQGRA-282
> URL: https://issues.jboss.org/browse/ARQGRA-282
> Project: Arquillian Graphene
> Issue Type: Feature Request
> Components: doc
> Reporter: Juraj Húska
> Assignee: Juraj Húska
> Fix For: 2.0.0.Alpha4
>
> Original Estimate: 3 hours
> Remaining Estimate: 3 hours
>
> Possible option is to alter functional testing guide which is here:
> http://arquillian.org/guides/functional_testing_using_drone/
--
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, 9 months
[JBoss JIRA] (ARQGRA-282) Create Graphene guide on arquillian.org
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-282?page=com.atlassian.jira.plugin... ]
Juraj Húska commented on ARQGRA-282:
------------------------------------
IMHO it can be done in this way:
* change the feature reference _Drive the Browser_ from [here|http://arquillian.org/features/], to contain _Graphene_ reference. It would be nice to have there also Graphene logo (ARQGRA-69)(together with Drone logo)
* reuse and alter the already existing [functional testing using drone|http://arquillian.org/guides/functional_testing_using_drone/], because IMHO there valuable parts, which are needed (_Assumptions_, _Introducing Client Mode_, _Enabling Client Mode_, _Drone Overview_). So dropping the whole guide is not a good option for me.
* it can be done in a similar way as the [guide for JPA testing|http://arquillian.org/guides/testing_java_persistence/] is done. So _Introducing the application we are going to write tests for_, _Preparation for testing with Graphene_, _Developing tests_, _Running the tests_
* basically I have not recognized other candidates from Lukas's ones, I just ordered them in the outline.
The guide outline itself can look like:
# Assumptions
# Introducing Client Mode
# Enabling Client Mode
# Drone Overview
## There are mentioned all the browsers drivers Drone currently has support for, we can emphasize _Graphene_ here and say that we are going to setup a test suite project with use of it from now on.
# Introducing the application we are going to write tests for
## We can show how to develop a simple _HTML 5_ page, which will use _AJAX_ calls to retrieve backend data from _JAX-RS_ endpoints.
## *Or* we can reuse again the _JSF_ sample which is already there, logging fragment, and to add some parts to easily showcase _Graphene_ features on it. My concert here is the _JSF_. I would like to showcase that _Graphene_ can be used with all front end frameworks and most importantly with now most coolest POH5 applications. By this IMHO we can get much bigger audience.
## It does not have to be all in this guideline. There can be just snippets from whole Graphene showcase, which will be developed as well. (ARQGRA-174)
# _Graphene_ scaffolding
# Senium server setup, remote reusable, chrome browser -> fast development turnaround
# Developing tests
## Showcasing some of the _Graphene_ features: _request guards_, _fluent waitings_, _Page Ojects_, _Page Fragments_
## This should be probably the biggest part of the guideline. My concern here is that it will be too big. On the other side I do not have a major problem with it. IMHO the navigation which is used in arquillian.org is quite clear and that the platform is suitable for long posts as well.
# Running and debugging the test in IDE
# Best practices from developing and running tests
What do you think guys ?
> Create Graphene guide on arquillian.org
> ---------------------------------------
>
> Key: ARQGRA-282
> URL: https://issues.jboss.org/browse/ARQGRA-282
> Project: Arquillian Graphene
> Issue Type: Feature Request
> Components: doc
> Reporter: Juraj Húska
> Assignee: Juraj Húska
> Fix For: 2.0.0.Alpha4
>
> Original Estimate: 3 hours
> Remaining Estimate: 3 hours
>
> Possible option is to alter functional testing guide which is here:
> http://arquillian.org/guides/functional_testing_using_drone/
--
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, 9 months
[JBoss JIRA] (ARQGRA-283) Create blog entry about Graphene vs WebDriver
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-283?page=com.atlassian.jira.plugin... ]
Juraj Húska commented on ARQGRA-283:
------------------------------------
First proposal:
# Introduction
## Testing difficulties in general: _unreliable waits_,
## _testing of ajax behavior_,
## _coupling of HTML and test code_
# Introducing Graphene
## Coolest features: _request guards_,
## _Page Objects_ - support for {{@Page}}, nested pages, {{@FindBy}}, _JQuery_ locators, locators from field names, enriching of other injection points like {{@Drone}}, {{@Location}} mechanism
## _Page Fragments_ - rooting mechanism, reference to RichFaces page fragments, dynamically creatable
## _fluent API_ for waits - example
## _JS interfaces_ - example
## _Interceptors_ - example for resolving {{Stale..}} exceptions
## highly extendable and usable with {{Arquillian}} life cycle
# Wrap-up
## nice table which summarizes all the features in comparison to {{WebDriver}}
General notes:
* Where it is possible I will reference to {{WebDriver}} to showcase the difference. So for example when I will be speaking about waits I will also show how it is done in {{WebDriver}}.
What do you think Lukas ?
> Create blog entry about Graphene vs WebDriver
> ---------------------------------------------
>
> Key: ARQGRA-283
> URL: https://issues.jboss.org/browse/ARQGRA-283
> Project: Arquillian Graphene
> Issue Type: Task
> Components: doc
> Reporter: Juraj Húska
> Assignee: Juraj Húska
> Fix For: 2.0.0.Alpha4
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> Create blog entry about core differences between WebDriver and Graphene. It should summarize all Graphene features to promote them.
--
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, 9 months