Re: [GSoC] MyFaces CODI RAD status
Hi, That sounds really great! I will do the required package refactoring and continue with the functionality impl. Regarding keeping it external at apache-extras sounds like the best solution for now, for integrating it as a sub-project of MyFaces I will try to provide a complete and reliable version and extract the core functionality for future IDE plugins. @Mark Thanks for the support, and yes if I encounter any issues it would be great to communicate with Lincoln Regards, Cosmin On Sat, Aug 27, 2011 at 10:42 PM, Mark Struberg strub...@yahoo.de wrote: Hi! a.) congratulations to the plugin, looks really good. Thanks for putting all this work into it! b.) I retweeted the repo link and Lincoln (creator and maintainer of Seam-Forge) already retweeted it. So if you need some further assistence, I'm sure we can connect you to the right people ;) LieGrue, strub --- On Fri, 8/26/11, Gerhard Petracek gerhard.petra...@gmail.com wrote: From: Gerhard Petracek gerhard.petra...@gmail.com Subject: Re: [GSoC] MyFaces CODI RAD status To: MyFaces Development dev@myfaces.apache.org Date: Friday, August 26, 2011, 6:39 PM hi cosmin, first of all thx for your work. i'm happy to hear that you plan to continue with the project. imo rule #1 is just for 3rd party projects to avoid that they use names of apache projects (without the permission of the community) in order to benefit from them. (before apache-extras started we reserved several project names for the same reason.)if other pmc members have objections, we have to think about it. however, we have to think about the future of this project: 1) keep it external at apache-extras (for now) and refactor package names (in this case all myfaces committers would get access as with other apache-extras projects related to myfaces)2) it continues as myfaces sub-project (e.g. near to other tools like archetypes) esp. with 2) we have to think about a lot of topics (esp. about current and future dependencies). since this project (currently) depends on the success of forge itself (which is still beta), i would keep it at apache extras. it's also easier for cosmin to continue with his work, because he doesn't have commit rights right now. (to keep the community involved, we should continue to use the myfaces dev list and wiki even though it is an external project.) regards,gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/8/26 Martinconi Cosmin cosmin.martinc...@codebeat.ro Hi everyone, The GSoC program for this year is finished and you can find the current status of the project at a new location[1]. The current 0.9.0 version provides the functionality proposed for this program, more details about the commands supported can be found in the README file. As part of the apache-extra project host the project doesn't completely comply with the guidelines. The problems come from:1) not using Apache or an existing Apache project name in your Apache Extras project name, and 2) not using org.apache as the prefix. I am considering renaming the packages as org.apacheExtra, any suggestion regarding this is welcomed. There is more work to be done for the plugin to be complete and eventually extend the functionality to other CODI IDE plugins, and I will be happy to continue working and supporting any Codi RAD functionality. Special thanks to Gerhard, my mentor for this program. Regards, Cosmin [1] http://code.google.com/a/apache-extras.org/p/myfaces-codi-rad/
[GSoC] MyFaces CODI RAD status
Hi everyone, The GSoC program for this year is finished and you can find the current status of the project at a new location[1]. The current 0.9.0 version provides the functionality proposed for this program, more details about the commands supported can be found in the README file. As part of the apache-extra project host the project doesn't completely comply with the guidelines. The problems come from:1) not using Apache or an existing Apache project name in your Apache Extras project name, and 2) not using org.apache as the prefix. I am considering renaming the packages as org.apacheExtra, any suggestion regarding this is welcomed. There is more work to be done for the plugin to be complete and eventually extend the functionality to other CODI IDE plugins, and I will be happy to continue working and supporting any Codi RAD functionality. Special thanks to Gerhard, my mentor for this program. Regards, Cosmin [1] http://code.google.com/a/apache-extras.org/p/myfaces-codi-rad/
Re: [VOTE] Release of Extensions CDI (CODI) 1.0.1
+1 Regards, Cosmin On Fri, Aug 19, 2011 at 3:04 PM, Bart Kummel b...@kummelweb.nl wrote: +1 Best regards, Bart On Thu, Aug 18, 2011 at 22:58, Gerhard Petracek gpetra...@apache.orgwrote: Hi, I was running the needed tasks to get the 8th release of Apache MyFaces Extensions CDI (aka MyFaces CODI) out. The artifacts are deployed to Nexus [1] (and [2]). The release contains the following modules: - CODI Core - CODI JSF Module (for 1.2 and 2.0 and 2.1) - CODI JPA Module - CODI BV Module - CODI I18N-Message Module - CODI Scripting Module - CODI Trinidad Support Module - CODI Alternative Config and Impl Modules - CODI Bundles - CODI OSGi Bundles - CODI Base Test-Infrastructure Module - CODI JUnit-Support Module - CODI Cargo-Support Module - CODI OpenWebBeans Test-Support Module - CODI JSF Test-Support Module - CODI JSF Example Please take a look at the 1.0.1 artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Gerhard [1] https://repository.apache.org/content/repositories/orgapachemyfaces-054/ [2] https://repository.apache.org/content/repositories/orgapachemyfaces-054/org/apache/myfaces/extensions/cdi/myfaces-extcdi-parent/1.0.1/myfaces-extcdi-parent-1.0.1-source-release.zip [3] http://www.apache.org/foundation/voting.html#ReleaseVotes -- ___ *Bart Kummel* Author of the book Apache MyFaces 1.2 Web Application Developmenthttp://tinyurl.com/am12wad blog: BK http://www.bartkummel.net/ | twitter: @bkummel http://twitter.com/bkummel
[GSoC] CODI RAD
Hi, The GSoC program is near to it's finish and the features proposed and fixed for the project within this program are available at [1]. A new auto-complete functionality is added which can be tested with the codi viewconfigResource --name command, and also some fixes and enhancements were done. All the informations required to launch and test the plugin are available within the README file. I will enjoy continuing working on the project and would appreciate any feedback and future requirement suggestions. Regards, Cosmin [1] http://gsoc2011-seam-forge-codi-plugin.googlecode.com/svn/trunk/
Re: [GSoC] CODI RAD
Hi, I have started working on such a quick start guide where using a forge script that contains a series of commands a complete application can be created. Some initial work can be found in the examples module of the project, but for it to be complete some more work is required for using a forge ScafoldProvider and also bringing more features to the plugin. Regarding extending in order to create IDE plugins, that will be great and I think it will not be to hard to extract a core impl because I tried to use forge support functionality as less as possible. Regards, Cosmin On Fri, Aug 19, 2011 at 10:34 PM, Leonardo Uribe lu4...@gmail.com wrote: Hi Looks great. It could be good to have a quick start guide, where step by step an application is created from scratch (installing tools, configuring, running, testing ...). regards, Leonardo Uribe 2011/8/19 Gerhard Petracek gerhard.petra...@gmail.com: hi cosmin, thx for the update. i think users who prefer command-line tools will like it. with some additional work we could create e.g. ide plugins based on the core logic. i think it would be nice to promote it to apache-extras (it's easy for you to continue there). after an ongoing and close interaction with the community even after gsoc, ali became a committer last year. i'm looking forward to seeing the same with you and codi-rad. regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/8/19 Martinconi Cosmin cosmin.martinc...@codebeat.ro Hi, The GSoC program is near to it's finish and the features proposed and fixed for the project within this program are available at [1]. A new auto-complete functionality is added which can be tested with the codi viewconfigResource --name command, and also some fixes and enhancements were done. All the informations required to launch and test the plugin are available within the README file. I will enjoy continuing working on the project and would appreciate any feedback and future requirement suggestions. Regards, Cosmin [1] http://gsoc2011-seam-forge-codi-plugin.googlecode.com/svn/trunk/
Re: [GSoC] Seam-Forge plugin for MyFaces CODI
Hi everyone, I have done some more work on the GSoC project Seam-Forge plugin for MyFaces CODI, the current status of the project can be checked at [1]. The features provided until now include: - *codi viewconfig-create-folder --name Pages* - creates a new Folder(ViewConfig) configuration named Pages in the base package directory and a new directory: ./main/webapp/pages - *codi viewconfig-create-folder --name Wizard --in Pages* - creates a new folder config named Wizard in the Pages ViewConfig and a new directory: ./main/webapp/pages/wizard - *codi viewconfig-create-page --name Step1 --in Pages.Wizard*- creates a new page config named Step1 in the Pages.Wizard folder and a new page:./main/webapp/pages/wizard/step1.xhtml - *codi viewconfig-create-config --name SecuredPages --voter LoginAccessDecisionVoter* - creates a new ViewConfig file called SecuredPages with an @Secured(LoginAccessDecisionVoter.class) annotation. Also an LoginAccessDecisionVoter java file which extends AbstractAccessDecisionVoter is created - codi viewconfig-list-all - prints all the configuration for a given ViewConfig. Other commands available are: - codi viewconfig-create-page --name ErrorPage --in Pages --errorPage - codi viewconfigResource --name Pages --redirect - codi viewconfigResource --name Pages.Wizard --extendWith SecuredPages - codi viewconfig-list-pages I provided a README.txt file in the project that will give more details. Any new requirements and suggestions are welcomed. Regards, Cosmin [1]http://wiki.apache.org/myfaces/GSoC2011_Codi_RAD On Thu, Jul 7, 2011 at 7:03 PM, Gerhard Petracek gerhard.petra...@gmail.com wrote: hi cosmin, great! i'll have a look at it within the next days. regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/7/7 Martinconi Cosmin cosmin.martinc...@codebeat.ro Hi, I am currently working on the Seam-Forge plugin for MyFaces CODI[1] project for this year's GSoC and I would highly appreciate your feedback regarding the implementation and any future requirements for the plugin. You can checkout the project from [2] where a README file will provide the necessary information regarding the setup and usage instruction. For now the plugin provides ''setup and add-new-view commands. The first one will install the CodiFacet which ensures that all required dependencies are added to a given project. The add-new-view command offers support for adding new views and view configurations in a type-safe CODI manner. I am currently working on the add-new-view functionality. Any inputs and suggestions regarding the plugin are welcomed. Regards, Cosmin [1] http://wiki.apache.org/myfaces/GSoC2011_Codi_RAD [2] http://gsoc2011-seam-forge-codi-plugin.googlecode.com/svn/trunk/
[GSoC] Seam-Forge plugin for MyFaces CODI
Hi, I am currently working on the Seam-Forge plugin for MyFaces CODI[1] project for this year's GSoC and I would highly appreciate your feedback regarding the implementation and any future requirements for the plugin. You can checkout the project from [2] where a README file will provide the necessary information regarding the setup and usage instruction. For now the plugin provides ''setup and add-new-view commands. The first one will install the CodiFacet which ensures that all required dependencies are added to a given project. The add-new-view command offers support for adding new views and view configurations in a type-safe CODI manner. I am currently working on the add-new-view functionality. Any inputs and suggestions regarding the plugin are welcomed. Regards, Cosmin [1] http://wiki.apache.org/myfaces/GSoC2011_Codi_RAD [2] http://gsoc2011-seam-forge-codi-plugin.googlecode.com/svn/trunk/
Re: [VOTE] Release of Extensions CDI (CODI) 1.0.0
+1 On Sun, Jul 3, 2011 at 3:59 PM, Mark Struberg strub...@yahoo.de wrote: +1 LieGrue, strub --- On Sun, 7/3/11, Hazem Saleh haz...@apache.org wrote: From: Hazem Saleh haz...@apache.org Subject: Re: [VOTE] Release of Extensions CDI (CODI) 1.0.0 To: MyFaces Development dev@myfaces.apache.org Date: Sunday, July 3, 2011, 11:09 AM +1 On Sun, Jul 3, 2011 at 12:40 PM, Matthias Wessendorf mat...@apache.org wrote: +1 On Sun, Jul 3, 2011 at 5:00 AM, Gerhard Petracek gerhard.petra...@gmail.com wrote: +1 regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/7/3 Gerhard Petracek gpetra...@apache.org Hi, I was running the needed tasks to get the 7th release of Apache MyFaces Extensions CDI (aka MyFaces CODI) out. The artifacts are deployed to Nexus [1] (and [2]). The release contains the following modules: - CODI Core - CODI JSF Module (for 1.2 and 2.0 and 2.1) - CODI JPA Module - CODI BV Module - CODI I18N-Message Module - CODI Scripting Module - CODI Trinidad Support Module - CODI Alternative Config and Impl Modules - CODI Bundles - CODI OSGi Bundles - CODI Base Test-Infrastructure Module - CODI JUnit-Support Module - CODI Cargo-Support Module - CODI OpenWebBeans Test-Support Module - CODI JSF Test-Support Module - CODI JSF Example Please take a look at the 1.0.0 artifacts and vote! Please note: This vote is majority approval with a minimum of three +1 votes (see [3]). [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Gerhard [1] https://repository.apache.org/content/repositories/orgapachemyfaces-009/ [2] https://repository.apache.org/content/repositories/orgapachemyfaces-009/org/apache/myfaces/extensions/cdi/myfaces-extcdi-parent/1.0.0/myfaces-extcdi-parent-1.0.0-source-release.zip [3] http://www.apache.org/foundation/voting.html#ReleaseVotes -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Hazem Ahmed Saleh Ahmed Author of (The Definitive Guide to Apache MyFaces and Facelets): http://www.amazon.com/Definitive-Guide-Apache-MyFaces-Facelets/dp/1590597370 http://www.amazon.com/-/e/B002M052KY Visualize and share your social networks 2D and 3D: http://www.mapmysocial.com
[GSoC] Seam-Forge plugin for MyFaces CODI
Hi, I created a wiki page with my application proposal[1] for the Seam-Forge plugin for MyFaces CODI issue, for this years Google Summer of Code program. You can find the Jira issue at [2]. I would really appreciate any feedback and comments. Thanks, Cosmin [1] http://wiki.apache.org/myfaces/GSoC2011_CodiPlugin [2] https://issues.apache.org/jira/browse/EXTCDI-159
Re: [GSoC] Seam-Forge plugin for MyFaces CODI
Hi Gerhard, Yes, that is a good idea, I have renamed it to GSoC2011_Codi_RAD, you can now find the project proposal at [1]. Regards, Cosmin [1] http://wiki.apache.org/myfaces/GSoC2011_Codi_RAD On Mon, Apr 4, 2011 at 11:56 AM, Gerhard Petracek gerhard.petra...@gmail.com wrote: hi cosmin, looks good to me. maybe we should rename the page to: http://wiki.apache.org/myfaces/GSoC2011_Codi_ForgePlugin or e.g. http://wiki.apache.org/myfaces/GSoC2011_Codi_RAD since it would be a rad-tool for codi implemented as forge-plugin, i would prefer #2 regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/4/4 Martinconi Cosmin cosmin.martinc...@codebeat.ro Hi, I created a wiki page with my application proposal[1] for the Seam-Forge plugin for MyFaces CODI issue, for this years Google Summer of Code program. You can find the Jira issue at [2]. I would really appreciate any feedback and comments. Thanks, Cosmin [1] http://wiki.apache.org/myfaces/GSoC2011_CodiPlugin [2] https://issues.apache.org/jira/browse/EXTCDI-159
Re: gsoc 2011 - ideas
Hi, I took a look on MyFaces wiki page for the current GSoC ideas you proposed and they sound really interesting. Last year I participated in GSoC with the Automated Webapp Test[1] project, I am still a student and I would enjoy participating also in this years program. The Seam-Forge plugin for CODI project sounds great, and I would enjoy working on it. So, if it's ok with everybody and if nobody announced its interest into this project, I would really like to learn more and dig in on this. Regards, Cosmin [1] http://wiki.apache.org/myfaces/AutomatedWebappTest_Status On Mon, Jan 31, 2011 at 10:15 AM, Matthias Wessendorf mat...@apache.orgwrote: Thanks Gerhard, Jakob and I posted these links already on twitter. I'd recommend that others do the same :-) Especially the tooling plugins are interesting! -Matthias On Sun, Jan 30, 2011 at 10:12 PM, Gerhard gerhard.petra...@gmail.com wrote: i've created [1] for collecting ideas for the next gsoc. regards, gerhard [1] http://wiki.apache.org/myfaces/GSoC2011 http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [DISCUSS] [GSoC] Automated webapp test framework integration
Hi, Together with the integration of the framework, for a better overview and for an initial step in continuing work within this project I have created a wiki page[1] with some detailed description of the API, together with the improvements and weaknesses that should be solved. Your comments, suggestions and issue reports are welcomed. Regards, Cosmin [1] http://wiki.apache.org/myfaces/AutomatedWebappTest_Status On Sat, Sep 4, 2010 at 11:45 PM, Leonardo Uribe lu4...@gmail.com wrote: Hi No objections for my side, but could you be more explicit about what you gonna do? Do you want to include it as a separate module for myfaces-test (note this requires an official vote)? or maybe create a branch on myfaces-test so we can enhance it and when it is ready, do some alpha/beta releases?. regards, Leonardo Uribe 2010/9/4 Jakob Korherr jakob.korh...@gmail.com Hi, If no objections I'll start the integration today into myfaces/test/webapptest. Regards, Jakob 2010/8/23 Jakob Korherr jakob.korh...@gmail.com Hi, Since GSoC is over, we can now integrate the code into our codebase. The code currently lives in a google code project [1]. Because of the fact that this is a test framework, I would really like to put it into the test folder rather then creating a new (myfaces-)top-level entry. However I do not want to integrate it into the current MyFaces test framework (that currently lives in the test folder), because this is a completely different thing and IMO we have to be able to do separate releases of those two. In addition I would like to create a new project in the JIRA for the automated webapp tests framework. Something like WEBAPPTEST. Suggestions are welcome! What do you think? Any objections, thoughts, ideas? Thanks for looking into this! Regards, Jakob [1] http://code.google.com/p/gsoc2010-automated-myfaces-tests/ -- Jakob Korherr blog: http://www.jakobk.com twitter: http://twitter.com/jakobkorherr work: http://www.irian.at -- Jakob Korherr blog: http://www.jakobk.com twitter: http://twitter.com/jakobkorherr work: http://www.irian.at
Re: [GSoC] Automated webapp tests project
Hi,
Thanks for your feedback and suggestions, and special thanks to Jakob, for a
great collaboration, and Gerhard my mentors for this project. GSoC codding
is over, and it would be my pleasure to continue working on this project
within MyFaces. So, as Jakob mentioned, I will initially provide a wiki
page with a more detailed description of the project, the drawbacks and the
improvements needed and you are very welcomed to input any suggestions.
Yes, this is a pre-pre-alpha version of the API, but I'm looking forward
continuing it and hope we can make it a great testing framework.
Cheers,
Cosmin
On Wed, Aug 18, 2010 at 12:21 PM, Jakob Korherr jakob.korh...@gmail.comwrote:
Hi,
That's really great Rudy. Thanks for trying it out :)
Frankly I would say that the current version is somewhere pre-pre-alpha,
because there is a lot of stuff that has to be improved (like e.g. your
custom maven repo), but the code from Cosmin is a solid base and we can
totally build upon it!
Cosmin told me he is willing to work on it after GSoC and the first thing
he will do is providing a DevDoc wiki page. There we can post
problems/suggestions/improvements. Furthermore we can use JIRA (maybe as a
new project - WEBAPPTESTS ?).
Werner, I think we can do a lot of your tests using the
automated-webapp-tests. I am looking forward to trying it out :)
Regards,
Jakob
2010/8/18 Werner Punz werner.p...@gmail.com
Hi I added meta logging facilities to _ExtLang.js a while ago I have been
using this mainly for manual testing with Selenium as afterthought. It might
be a base to start off for the ajax stuff.
What it does is to be able to log into a console if it exists,
and also to a div with a certain id if this one exists in the dom tree.
Also there is a small unit testing javascript class in UnitTest.js
which takes care of asserts on top of it the way junit does.
Again currently only used by me internally.
We might take that one as a small base for testing on the client side in
conjunction with selenium.
Werner
Am 18.08.10 09:08, schrieb Rudy De Busscher:
Hi,
I also did some tests and had to make a small modification so that it
finds my custom maven repository (defined in the settings.xml). For the
rest, it seems to work great.
I can add that code after the integration is done.
regards
rudy.
On 17 August 2010 22:02, Jakob Korherr jakob.korh...@gmail.com
mailto:jakob.korh...@gmail.com wrote:
Hi Leo,
After the integration, we can do that. I would like to have this too
:)
Regards,
Jakob
2010/8/17 Leonardo Uribe lu4...@gmail.com mailto:lu4...@gmail.com
Hi
Good to know that. I'll take a look at this one. I would like to
have a test suite for flash scope and ajax stuff.
regards,
Leonardo Uribe
2010/8/10 Martinconi Cosmin cosmin.martinc...@codebeat.ro
mailto:cosmin.martinc...@codebeat.ro
Hi,
The GSoC program for this year is almost finished and I
wanted to let you know about the progress and the current
state of the Automated webapp tests for MyFacescore and
extensions, my project for this GSoC.
You can follow the API and the implementation(SVN google
code) on:
* http://wiki.apache.org/myfaces/AutomatedWebappTestsAPI
*
https://gsoc2010-automated-myfaces-tests.googlecode.com/svn/trunk/
The API that I have followed is the one from the wiki,
including small changes like introducing @Tester and
@Assertable instead of @Inject for the resource
injection configuration. The @Tester will inject an
WebappTester instance that will provide all required
functionality, and @Assertable to inject proxy instances
for assertions.
Also an @ConfigurationTestSuite configuration was
provided, where the user of the API can specify a list of
configurations and the API will run the test case with all
the configs, meaning an n configured test case will
generate n tests for the same test instance but with each
of the specified configs.
The API provides the following actions: click(buttonId),
input(string).into(fieldId); and the assertions:
assertThat(methodCall/ELexpression).is(Object).before/after(PhaseId)
and expectCall(methodCall/ELexpression).in(PhaseId)
I am currently working on some issues regarding expectCall()
that I overlooked, but this should be functional by the end
of this week. Other drawbacks of the project are that I
couldn't get rid of the method:
@Deployment
public static Archive? createDeployment() {
return webappTestCase.createArchive(null);
}
Arquillian is looking
[GSoC] Automated webapp tests project
Hi,
The GSoC program for this year is almost finished and I wanted to let you
know about the progress and the current state of the Automated webapp tests
for MyFacescore and extensions, my project for this GSoC.
You can follow the API and the implementation(SVN google code) on:
- http://wiki.apache.org/myfaces/AutomatedWebappTestsAPI
- https://gsoc2010-automated-myfaces-tests.googlecode.com/svn/trunk/
The API that I have followed is the one from the wiki, including small
changes like introducing @Tester and @Assertable instead of @Inject
for the resource injection configuration. The @Tester will inject an
WebappTester instance that will provide all required functionality, and
@Assertable to inject proxy instances for assertions.
Also an @ConfigurationTestSuite configuration was provided, where the user
of the API can specify a list of configurations and the API will run the
test case with all the configs, meaning an n configured test case will
generate n tests for the same test instance but with each of the specified
configs.
The API provides the following actions: click(buttonId),
input(string).into(fieldId); and the assertions:
assertThat(methodCall/ELexpression).is(Object).before/after(PhaseId) and
expectCall(methodCall/ELexpression).in(PhaseId)
I am currently working on some issues regarding expectCall() that I
overlooked, but this should be functional by the end of this week. Other
drawbacks of the project are that I couldn't get rid of the method:
@Deployment
public static Archive? createDeployment() {
return webappTestCase.createArchive(null);
}
Arquillian is looking for a method annotated with @Deployment and if such a
method is not provided it fails the test run. Another inconvenience is that,
for the embaded Tomcat container, Arquillian requires, for now, a servlet
mapping in the web.xml of the testing webapp, like:
servlet
servlet-nameServletTestRunner/servlet-name
servlet-classorg.apache.myfaces.test.webapp.api.runner.WebappServletTestRunner/servlet-class
/servlet
servlet-mapping
servlet-nameServletTestRunner/servlet-name
url-pattern/ArquillianServletRunner/url-pattern
/servlet-mapping
I would highly appreciate any feedback, comments or suggestions on the
project and the implementation.
Regards,
Cosmin
[GSOC] Testing framework for the new testing API
Hi, I've started working on my GSoC project Automated webapp tests for MyFaces core and extensions, and the first target of the project is to create an testing API that will be used for the project's testing of MyFaces core, and if required for any extensions. For this after some studying and discussions I proposed Arquillian as a framework in order to be integrated into the API. Other frameworks that I considered are HTTPUnit and Canoo WebTest. What do you think about Arquillian, any other ideas, should we reconsider another framework? The scope of the API is to be used for MyFaces core, bot also for any extension and application testing that is needed. For more reference regarding my GSoC proposal and Arquillian documentation you can check out: - http://wiki.apache.org/myfaces/GSoC2010_AutomatedTests - http://docs.jboss.org/arquillian/reference/latest/en-US/html_single/ Regards, Cosmin
Re: [GSOC] Testing framework for the new testing API
Hi Leonardo, Thanks for the feedback. Yes, as far as I saw it's ASL v2 licensed, so it should be no problem regarding this. Regards, Cosmin On Sat, Jun 5, 2010 at 6:03 PM, Leonardo Uribe lu4...@gmail.com wrote: Hi What license is Arquillian? It is some kind of GPL or LGPL you should read this link: http://www.apache.org/legal/resolved.html Looking some source files of that project it seems it is Apache License v 2.0, so it is ok. I'll take a look at your proposal. regards, Leonardo Uribe 2010/6/5 Martinconi Cosmin cosmin.martinc...@codebeat.ro Hi, I've started working on my GSoC project Automated webapp tests for MyFaces core and extensions, and the first target of the project is to create an testing API that will be used for the project's testing of MyFaces core, and if required for any extensions. For this after some studying and discussions I proposed Arquillian as a framework in order to be integrated into the API. Other frameworks that I considered are HTTPUnit and Canoo WebTest. What do you think about Arquillian, any other ideas, should we reconsider another framework? The scope of the API is to be used for MyFaces core, bot also for any extension and application testing that is needed. For more reference regarding my GSoC proposal and Arquillian documentation you can check out: - http://wiki.apache.org/myfaces/GSoC2010_AutomatedTests - http://docs.jboss.org/arquillian/reference/latest/en-US/html_single/ Regards, Cosmin
Re: [GSoC] Automated webapp tests
Hi Mike, Thanks for the feedback. I did considered Selenium, but after some discussions we concluded that the testing should be done totally automated within maven and without a browser, so that excludes Selenium since it needs a browser running in order to work. Regards, Cosmin On Wed, Apr 7, 2010 at 8:57 PM, Mike Kienenberger mkien...@gmail.comwrote: I'd like to recommend that you also consider Selenium as a test framework. On Wed, Apr 7, 2010 at 10:04 AM, Martinconi Cosmin cosmin.martinc...@codebeat.ro wrote: Hi, I also prepared an application proposal, that I submitted to Google and a wiki page: http://wiki.apache.org/myfaces/GSoC2010_AutomatedTests for the Automated webapp tests for MyFaces Core and extensions issue. You can find the Jira Issue at: https://issues.apache.org/jira/browse/MYFACESTEST-6 I would really appreciate any feedback and comments. Thanks, Cosmin
[GSoC] Automated webapp tests
Hi, I also prepared an application proposal, that I submitted to Google and a wiki page: http://wiki.apache.org/myfaces/GSoC2010_AutomatedTests for the Automated webapp tests for MyFaces Core and extensions issue. You can find the Jira Issue at: https://issues.apache.org/jira/browse/MYFACESTEST-6 I would really appreciate any feedback and comments. Thanks, Cosmin
Re: [GSoC] Proposal - Automated webapp tests
Hi, This sounds really good, I would enjoy working on this. So, if it's ok with everybody, I would really like to dig in on this issue and the test frameworks that can be used for this. Regards, Cosmin On Fri, Mar 26, 2010 at 2:25 AM, Jakob Korherr jakob.korh...@gmail.comwrote: Hi, As we currently only have normal JUnit tests for automated testing in MyFaces Core, it would be really great to have a way to test MyFaces Core automatically in a real webapp at build time with maven. Of course, we currently have the test-webapp, but we still have to check each page manually here, if we want to test everything, which is long-winded. To accomplish something like that we could use test frameworks like e.g. Canoo WebTest or HttpUnit + Jetty or something similar. I also want to mention JSFUnit here, although we won't be able to use it since it is LGPL licensed. The goal of this GSoC project would be to find alternatives and also to find the best-fitting test framework for MyFaces Core. Then the goal would be to integrate it with MyFaces Core, to define rules and provide how-tos and to write a bunch of test cases. This would help us enormously in ensuring and improving the quality of MyFaces Core by getting a far bigger test coverage and more possibilities to test. What do you think? Are there any students who are interested in working on this? Regards, Jakob
