JSFUnit restructured
by Stan Silvert
I've restructured the JSFUnit project to more closely align with Maven
standards and also to make jboss-parent the parent project. This
changes the group ID to be "jboss".
I also uploaded all the dependencies to the JBoss Maven Repo. And I
released a snapshot to the JBoss Maven Snapshot Repo.
All this should mean to you is that you might want to do a clean
checkout and rebuild because lots of directories are renamed. At the
very least you will need to do a svn update.
If you are curious about the Maven change and what it means to have
jboss-parent as the parent project, see:
http://wiki.jboss.org/wiki/Wiki.jsp?page=Maven
http://snapshots.jboss.org/maven2/jboss/jboss-parent/2-SNAPSHOT/jboss-par...
I'll be mostly unavailable until Monday, June 3rd. But I'll try to
check email from time to time between now and then.
Stan
19 years
JSFUnit plan and schedule
by Stan Silvert
Here is a broad outline of milestones I see for the project in the next
few months.
I'm working on these right now:
* Put all JSFUnit dependencies into the JBoss Maven repo.
* Make JSFUnit a child of the jboss-parent Maven project. This brings
the project in line with other Mavenized JBoss projects.
* Do a snapshot build and put it into the JBoss Maven snapshot repository.
TODO for me:
* More doco
* Create cactify tool for JSFUnit/Maven 2
Matt Wringe
* Create JSFUnit tests for JBoss Portal Admin
* Create cactify tool for JSFUnit/Ant
Mike Millison
* Examine code coverage tools with JSFUnit
I think if we can finish all that then we will be ready for a beta
release along with some press about it. I also think the most important
milestone will be Matt's evaluation of JSFUnit's suitability to testing
the Portal Admin. It's very important to get real-world feedback before
we go to beta.
Right now, I've set a beta date of mid-July. What do you guys think of
the plan?
Stan
19 years
patched cactus and ant example application
by Matt Wringe
Hi,
I have the patched cactus ant jars and have also created an ant build
file that takes the hellojsf webapp and adds the jsfunit bits [I also
have a very small doc about how to use the ant with jsfunit].
I have a couple of questions:
1) where should the patched cactus jars go?
2) I would like to get the ant example into svn, but I am a bit unsure
about a couple of things. Would it be ok to set it up like other ant
projects and put its dependency jars into svn? Or to set it up to use
the Maven tasks for ant so that dependencies and such come from the
maven repo? I currently have it setup as a bit of both (it grabs some of
the jars from the repo, but it won't download them if they are not in
the repo).
Thanks,
Matt Wringe
19 years
Re: Status: 2007-05-17
by Stan Silvert
Sohil Shah wrote:
>> have a simple test case created, but it wont work right now since
>> jsfunit expects an httpresponse and portal uses a portalresponse.
>
>
> For now you can just unit test it as a standalone JSF web application.
> The same application should just be intergrated into the portal via a
> JSFBridge.
>
CC'd the jsfunit dev list.
I'd be interested in knowing how important it will be to have portlet
support for JSFUnit. Do you guys think it's a high priority?
Right now I'd rather concentrate on getting things built out a little
more on the base project. But if the portal team needs portlet support
within a certain time frame then we'll prioritize accordingly.
Stan
19 years
test
by Stan Silvert
Aren't these fun?
19 years
test
by Julien Viet
Julien Viet
JBoss Portal Project Lead
Red Hat Inc.
http://jbossportal.blogspot.com/
Red Hat France SARL, 171 Avenue Georges Clemenceau, 92024 Nanterre
Cedex, France.
Siret n° 421 199 464 00056
19 years
test
by Julien Viet
test
Julien Viet
JBoss Portal Project Lead
Red Hat Inc.
http://jbossportal.blogspot.com/
Red Hat France SARL, 171 Avenue Georges Clemenceau, 92024 Nanterre
Cedex, France.
Siret n° 421 199 464 00056
19 years
