Difference between revisions of "JSF Tools Smoke Tests"

From Eclipsepedia

Jump to: navigation, search
(Added test case for loading resource bundles)
Line 143: Line 143:
 
*#The pages should open successfully.
 
*#The pages should open successfully.
  
'''JSF_023 Project Creation: Loading Resource Bundles'''
+
<br/>
*Steps
+
 
*#Follow the steps in the tutorial document to load a resource bundle.
+
=='''<font color="dimgray">Test Case JSF_023:</font> &nbsp; <font color="maroon">Project Creation: Loading Resource Bundles</font>'''==
*Criteria
+
 
*#The resource bundle should be added successfully as suggested in the tutorial document.
+
=== Steps ===
*#One should be able to successfully use the properties of the resource bundle as specified in the tutorial document.
+
 
 +
<br/>
 +
 
 +
* '''<font color="maroon">Add a Properties File</font>'''
 +
 
 +
<br />
 +
 
 +
: As outlined in the [http://www.eclipse.org/webtools/jsf/docs/tutorial/JSFTools_1_0_tutorial.html tutorial], move the static strings that you have used in the JSP file to a [http://java.sun.com/javase/6/docs/api/java/util/ResourceBundle.html resource bundle]. To do this, add a file called say '''messages.properties''' in the folder '''com.tutorial''' for example. Define the properties as shown below and save the file.  
 +
 
 +
<br/>
 +
 
 +
: [[Image:JsfResourceBundle1.png]]
 +
 
 +
<br/>
 +
 
 +
: [[Image:JsfResourceBundle3.png|frame|You can drag-and-drop the tag from the '''JSF Core''' section of the Palette View]] <br/>
 +
 
 +
 
 +
* '''<font color="maroon">Add the loadBundle Tag</font>'''
 +
 
 +
<br />
 +
 
 +
: Add the JSF tag, '''loadBundle''' as shown below.
 +
 
 +
<br/>
 +
 
 +
: [[Image:JsfResourceBundle2.png]]
 +
 
 +
<br/>
 +
 
 +
: Instead of typing it in, you may also drag-and-drop the '''loadBundle''' tag from the '''JSF Core''' section of the Palette View, as shown in the image on the right. If you choose to do it this way, double-click on the '''loadBundle''' widget that appears on the page and enter the '''basename''' and '''var''' attributes.
 +
 
 +
<br/>
 +
 
 +
* '''<font color="maroon">Test whether Auto-Complete Works</font>'''
 +
 
 +
<br/>
 +
 
 +
: Delete a hard-coded string from a value attribute in a JSF tag and replace it with '''<tt>"#{}"</tt>'''
 +
 
 +
<br/>
 +
 
 +
: Now place the cursor inside the braces, and press Ctrl+Space (or equivalent). You should see a popup with a list that includes the '''msg''' variable defined in the '''loadBundle''' tag. Select it.
 +
 
 +
<br/>
 +
 
 +
: [[Image:JsfResourceBundle4.png]]
 +
 
 +
<br/>
 +
 
 +
: Enter a dot after msg and and hit '''Ctrl+Space''' (or equivalent). You should see a pop-up with a list of properties defined in the '''messages.properties''' file. Select the property '''name'''
 +
 
 +
<br/>
 +
 
 +
: [[Image:JsfResourceBundle5.png]]
 +
 
 +
<br/>
 +
 
 +
* '''<font color="maroon">Test the Preview</font>'''
 +
 
 +
<br/>
 +
 
 +
: Click on the Preview tab on the editor
 +
 
 +
<br/>
 +
 
 +
: [[Image:JsfResourceBundle6.png]]
 +
 
 +
<br/>
 +
 
 +
: Ensure that you can see all the output labels replaced with their appropriate values from the properties resource bundle.
 +
 
 +
<br/>
 +
 
 +
: [[Image:JsfResourceBundle7.png]]
 +
 
 +
<br/>
 +
 
 +
* '''<font color="maroon">Test the Rendering on the Server</font>'''
 +
 
 +
<br/>
 +
 
 +
: Right click on your JSP file and select "'''Run on Server'''". Test whether the property values are rendered correctly.
 +
 
 +
<br/>
 +
 
 +
: [[Image:JsfResourceBundle7.png]]
 +
 
 +
<br/>
 +
 
 +
==== Criteria ====
 +
 
 +
Ensure that the following criteria are met:
 +
 
 +
* '''<font color="dodgerblue">loadBundle.</font>''' You should be able to add a loadBundle tag successfully.
 +
* '''<font color="dodgerblue">Autocomplete.</font>''' All the properties of the resource bundle should be displayed correctly when Ctrl+Spacebar (or equivalent) is pressed.
 +
* '''<font color="dodgerblue">Preview.</font>''' The preview should display correctly (with appropriate values from the properties file)
 +
* '''<font color="dodgerblue">Rendering on Server.</font>''' When run on the server, the rendered JSP page should display correctly.
 +
 
 +
<br/>
 +
 
  
 
[[JSF Tools Test Plans| Back to Test Plans]]
 
[[JSF Tools Test Plans| Back to Test Plans]]
 
[[Category:Eclipse Web Tools Platform Project]]
 
[[Category:Eclipse Web Tools Platform Project]]

Revision as of 19:14, 27 March 2008

NOTE: Draft version, subject to change Reference

Tests

JSF_001-Create JSF Library in preference page

  • Steps
    1. Window -> Preferences…->Web and XML -> JSF Libraries
  • Criteria
    • JSF Library is created successfully.

JSF_002-JSF Project Facets Wizard Page

  • Steps
    1. Select ""JavaServer Faces v1.1 Project"" preset in Project Facet Wizard page.
  • Criteria
    • Can select JavaServer Faces preset and move to next page.

JSF_003-JSF Capabilities: JSF Library Wizard Page

  • Steps
    1. Check JSF Capabilities wizard on libraries selection and check for deployment.
  • Criteria
    • Can configure selection of JSF libraries and check for deployment and finish project creation.

JSF_004-Project Creation: JSF Library Reference Property Page

  • Steps
    1. Project properties -> JSF Library Reference.
  • Criteria
    • See the same configuration as configured in JSF_003.

JSF_005 Project Creation: J2EE Module Dependencies

  • Steps
    1. Project properties --> J2EE Module Dependencies
  • Criteria
    • All JARs from JSF libraries checked for deployment should listed in the table.

JSF_006-Project Creation: Java Build Path

  • Steps
    1. Project properties -> Java Build Path
  • Criteria
    • All JARs from selected JSF libraries should be listed in path.

JSF_007-JSF Library Reference Property Page: J2EE Module Dependencies update

  • Steps
    1. Project properties -> JSF Library Reference.
    2. Uncheck/check a selected JSF libraries for deployment.
  • Criteria

JARs from changed JSF library should be added/removed from J2EE Module Dependencies.

JSF_008 JSF Library Reference Property Page: Java Build Path update

  • Steps
    1. Project properties -> JSF Library Reference.
    2. Add/Remove a selected JSF component library.
  • Criteria
  • JARs from the added/removed JSF library should be added/removed from build path.

JSF_009 JSF Facet installation + JSF library reference

  • Steps
    1. Create a web application w/o JSF facet installed during project creation.
    2. Project properties->Project Facets -> Add/Remove Project Facet.

Criteria JSF library references are added. Module dependencies and build path are updated accordingly.

JSF_010 JSF Facet installation/un-installation

  • Steps
    1. Create a web application w JSF facet installed during project creation.
    2. Uninstall JSF facet. Project properties->Project Facets -> Add/Remove Project Facet.
  • Criteria
    1. A JSF facet is uninstalled. But, JSF library reference remain unchanged. Designed behavior.

JSF_011 Syntax Checking

  • Steps
    1. Follow steps in tutorial document.
  • Criteria
    1. Syntax checking performed as suggested in tutorial document.

JSF_012 Semantic Checking

  • Steps
    1. Follow steps in tutorial document.
  • Criteria
    1. Semantic checking performed as suggested in tutorial document.

JSF_013 Quick Fix

  • Steps
    1. Follow steps in tutorial document.
  • Criteria
    1. Quick fix performed as suggested in tutorial document.

JSF_014 Content Assist

  • Steps
    1. Follow steps in tutorial document.
  • Criteria
    1. Content assist performed as suggested in tutorial document.

JSF_015 FacesConfig Editor: Add Managed Bean

  • Steps
    1. Follow steps in tutorial document.
  • Criteria
    1. Managed bean is added successfully.

JSF_016 FacesConfig Editor: Add JSP pages in Navigation rule tab.

  • Steps

Follow steps in tutorial document.

  • Criteria
    1. JSP pages are added successfully.

JSF_017 FacesConfig Editor: Connect JSP pages in Navigation rule tab.

  • Steps
    1. Follow steps in tutorial document.
  • Criteria
    1. JSP pages are connected successfully.

JSF_018 FacesConfig Editor: Link properties set up in Navigation rule tab.

  • Steps
    1. Follow steps in tutorial document.
  • Criteria
    1. Link properties are set up properly as suggested in tutorial document.

JSF_019 Runtime: Module dependencies are deployed

  • Steps

Deploy a JSF web application to a container.

  • Criteria
    1. Check if JARs are deployed with the application

JSF_020 Runtime: Login page displayed

  • Steps
    1. Right-click on login.jsp page and perform ""Run on Server""."
  • Criteria
    1. Web application should be deployed and login page should display properly.

JSF_021 Runtime: Page navigation.

  • Steps
    1. Enter a value for name and click Login.
  • Criteria
    1. Navigate to a welcomed page with name populated from login page.

JSF_022 Documentation

  • Steps
    1. Open the Eclipse Help, Help->HelpContents
    2. Check the links in the JavaServerFaces Tooling User Guide and JavaServerFaces Tooling Developer Guide
      1. JavaServerFaces Tooling Developer Guide->Programmer's guide->JSF Expression Language->(All the links)
      2. JavaServerFaces Tooling Developer Guide->Tutorial->Implementing a New Tag based EL variable contributor for JSP
  • Criteria
    1. The pages should open successfully.


Test Case JSF_023:   Project Creation: Loading Resource Bundles

Steps


  • Add a Properties File


As outlined in the tutorial, move the static strings that you have used in the JSP file to a resource bundle. To do this, add a file called say messages.properties in the folder com.tutorial for example. Define the properties as shown below and save the file.


JsfResourceBundle1.png


You can drag-and-drop the tag from the JSF Core section of the Palette View


  • Add the loadBundle Tag


Add the JSF tag, loadBundle as shown below.


JsfResourceBundle2.png


Instead of typing it in, you may also drag-and-drop the loadBundle tag from the JSF Core section of the Palette View, as shown in the image on the right. If you choose to do it this way, double-click on the loadBundle widget that appears on the page and enter the basename and var attributes.


  • Test whether Auto-Complete Works


Delete a hard-coded string from a value attribute in a JSF tag and replace it with "#{}"


Now place the cursor inside the braces, and press Ctrl+Space (or equivalent). You should see a popup with a list that includes the msg variable defined in the loadBundle tag. Select it.


JsfResourceBundle4.png


Enter a dot after msg and and hit Ctrl+Space (or equivalent). You should see a pop-up with a list of properties defined in the messages.properties file. Select the property name


JsfResourceBundle5.png


  • Test the Preview


Click on the Preview tab on the editor


JsfResourceBundle6.png


Ensure that you can see all the output labels replaced with their appropriate values from the properties resource bundle.


JsfResourceBundle7.png


  • Test the Rendering on the Server


Right click on your JSP file and select "Run on Server". Test whether the property values are rendered correctly.


JsfResourceBundle7.png


Criteria

Ensure that the following criteria are met:

  • loadBundle. You should be able to add a loadBundle tag successfully.
  • Autocomplete. All the properties of the resource bundle should be displayed correctly when Ctrl+Spacebar (or equivalent) is pressed.
  • Preview. The preview should display correctly (with appropriate values from the properties file)
  • Rendering on Server. When run on the server, the rendered JSP page should display correctly.



Back to Test Plans