Details
-
Type: New Feature
-
Status: Closed
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: 1.7.1
-
Fix Version/s: 1.8.1
-
Component/s: Bridge, Framework, ICE-Components
-
Labels:None
-
Environment:Test
-
ICEsoft Forum Reference:
Description
Take a look at the feasibility of using JSFUnit for developer oriented testing of our modules, classes, apps, etc.
I have created a JSFUnit test for an existing ICEfaces application., I declared the existing application as a dependency in my test application which is all good and I can write code to verify various items in the output of the page. According to this page, however, I see I need to copy the web.xml file from my existing application and modify it to contain servlet settings for JSFUnit and to create a 'stub' web application for JSFUnit. JSFUnit then merges the two web applications
It seems like I should be able to obtain a reference to the FacesContext available to application on the server. According to the following link, there is some ThreadLocal manipulation required to make this possible and the API seems to support this. However, at any point in the JSFUnit test code when I try to retrieve the instance (essentially from the JSFUnit thread, not the cactus application calling thread as I understand it) its value is null.
http://www.jboss.org/community/docs/DOC-10963
The ICEfaces blocking request strategy and server push. While JSFUnit supports Ajax requests by allowing the components to fire their native javascript, support for ICEfaces blocking receive-updated-views and receive-updates + merging of the updates into the JSFUnit DOM is an unsupported operation.
http://www.jboss.org/community/docs/DOC-10971