JUnit 4 do not requires to be extended from TestCase, but it makes intensive use of Java 1.5 annotations. Annotations are Java classes, so you still need to include JUnit dependencies. A short example of JUnit 4 could be found here: http://www.instrumentalservices.com/content/view/45/52/#_Cut_the_chase_to%20JUnit%204.0
Worst, JUnit 4 is still not supported by Maven (http://jira.codehaus.org/browse/SUREFIRE-31) that's why I'm not considering the migration for now.
Concerning my dev tools, I'm using only Maven command line and Eclipse (I give a try to Mevenide, but it sometimes conflicts with maven-eclipse-plugin settings, and is not very usefull for my needs). The first time you get sources of JWebUnit, just run mvn eclipse:eclipse to create .project and .classpath files. Now create a new project from sources in Eclipse for each module (jwebunit-core, jwebunit-htmlunit-plugin, jwebunit-tests-commons). To run unit tests, you can use Eclipse internal JUnit plugin (right click on jwebunit-htmlunit-plugin/src/test/java/JWebUnitTest.java -> run as -> JUnit test), or switch to a console and hit mvn test.
The only interest of Mevenide is the interface to add a new dependency to the project, but you can live without. Just add manually your dependency in the pom.xml, run mvn eclipse:eclipse again, and refresh your Eclipse project.
If you need more informations, feel free to ask ;)
++
Julien
Worst, JUnit 4 is still not supported by Maven (http://jira.codehaus.org/browse/SUREFIRE-31) that's why I'm not considering the migration for now.
Concerning my dev tools, I'm using only Maven command line and Eclipse (I give a try to Mevenide, but it sometimes conflicts with maven-eclipse-plugin settings, and is not very usefull for my needs). The first time you get sources of JWebUnit, just run mvn eclipse:eclipse to create .project and .classpath files. Now create a new project from sources in Eclipse for each module (jwebunit-core, jwebunit-htmlunit-plugin, jwebunit-tests-commons). To run unit tests, you can use Eclipse internal JUnit plugin (right click on jwebunit-htmlunit-plugin/src/test/java/JWebUnitTest.java -> run as -> JUnit test), or switch to a console and hit mvn test.
The only interest of Mevenide is the interface to add a new dependency to the project, but you can live without. Just add manually your dependency in the pom.xml, run mvn eclipse:eclipse again, and refresh your Eclipse project.
If you need more informations, feel free to ask ;)
++
Julien
----- Message d'origine ----
De : Nicholas Neuberger - Home <[EMAIL PROTECTED]>
À : [email protected]; Julien HENRY <[EMAIL PROTECTED]>
Envoyé le : Jeudi, 28 Septembre 2006, 1h28mn 16s
Objet : Re: [Jwebunit-users] Re : Simple Scraping Approach
De : Nicholas Neuberger - Home <[EMAIL PROTECTED]>
À : [email protected]; Julien HENRY <[EMAIL PROTECTED]>
Envoyé le : Jeudi, 28 Septembre 2006, 1h28mn 16s
Objet : Re: [Jwebunit-users] Re : Simple Scraping Approach
On Wednesday 27 September 2006 10:44 am, Julien HENRY wrote:
> Hi,
>
> I'm currently working on refactoring JWebUnit for release 2.x, and one of
> the feature request is to remove JUnit dependency (in order to allow use of
> another testing framework, like TestNG). jwebunit-2.0 will be splitted in
> the following Maven modules:
> - jwebunit-core
> - jwebunit-htmlunit-plugin
> - jwebunit-selenium-plugin
> - jwebunit-junit-plugin (wrap jwebunit-core with JUnit assertion)
From what I have heard is that the latest release of JUnit is a major change
from the original. I think the latest of junit no longer requires to be
extended from TestCase. I think. You might want to consider this for
jwebunit...
Also, can you tell me your dev tools for developing with jwebunit. I know you
use maven naturally. I'm so used to using eclipse for the past 4 years or
so.... Do you use eclipse or just straight command line stuff for
controlling maven? Or a maven - eclipse plugin....??
Let me know. I'm wanting to migrate another oss application that I'm
developing to use maven.
My project right now, is heavily centric around eclipse / springframework /
hibernate / and tomcat / with sysdeo plugin....
Any thoughts!!!
See Ya,
Nick Neuberger
> Hi,
>
> I'm currently working on refactoring JWebUnit for release 2.x, and one of
> the feature request is to remove JUnit dependency (in order to allow use of
> another testing framework, like TestNG). jwebunit-2.0 will be splitted in
> the following Maven modules:
> - jwebunit-core
> - jwebunit-htmlunit-plugin
> - jwebunit-selenium-plugin
> - jwebunit-junit-plugin (wrap jwebunit-core with JUnit assertion)
From what I have heard is that the latest release of JUnit is a major change
from the original. I think the latest of junit no longer requires to be
extended from TestCase. I think. You might want to consider this for
jwebunit...
Also, can you tell me your dev tools for developing with jwebunit. I know you
use maven naturally. I'm so used to using eclipse for the past 4 years or
so.... Do you use eclipse or just straight command line stuff for
controlling maven? Or a maven - eclipse plugin....??
Let me know. I'm wanting to migrate another oss application that I'm
developing to use maven.
My project right now, is heavily centric around eclipse / springframework /
hibernate / and tomcat / with sysdeo plugin....
Any thoughts!!!
See Ya,
Nick Neuberger
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ Jwebunit-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jwebunit-users
