TS 70 WebProject

Web Application Test Specification

Author: Dan Kolar, Jiri Skrivanek
Version: NetBeans 7.0
Last update: 8-th March 2011
Introduction: This test specification is focused on testing of web application creation and modification.
Comments:

Contents


Test suite: Creating web project

Purpose: To test creation of web application.
Setup: Install all supported servers.

  1. Server and Settings panel
    1. Click File -> New Project -> Java Web -> Web Application -> Next
    2. Choose different servers in Server combo box
    3. Check values in "Java EE Version" combo box are "Java EE 6 Web", "Java EE 5" and "J2EE 1.4" for GlassFish 3.x, JBoss 6.0 and Tomcat 7.0.
    4. Check values in "Java EE Version" combo box are only "Java EE 5" and "J2EE 1.4" for GlassFish 2.1, JBoss 5.1 and WebLogic 10.3.
    5. Select "J2EE 1.4" version and check that recommendation message about source level is shown and new check box for setting source level to 1.4 appears.
    6. Choose latest GlassFish as target server
    7. Change context path from default value
    8. Click Next
  2. Frameworks panel
    1. Framework List should contain "Spring Web MVC", "JavaServer Faces", "Struts 1.3.8" and "Hibernate 3.2.5"
    2. Choose Spring Web MVC
    3. In Libraries tab is "Spring Library" selection combo box and "Include JSTL" check box
    4. In Configuration tab is "Dispatcher Name" text field with default value dispatcher and "Dispatcher Mapping" text field with default value *.htm
    5. Insert invalid character (e.g. '*') in each text field and check red warning appears and Next/Finish is disabled.
    6. Choose JavaServer Faces framework
    7. In Libraries tab should be selected "Server Library" JSF 2.0
    8. In Configuration tab is "JSF Servlet URL Pattern" text field with default value "/faces/*". The "Preferred Page Language" combo box contains Facelets.
    9. In Components tab is "Component Suite" combo box and "None" is selected.
    10. Choose Struts 1.3.8
    11. Text fields "Action Servlet Name" with default value action, "Application Resource" with default value com.myapp.struts.ApplicationResource and editable combo box "Action URL Pattern" with default value "*.do" should present.
    12. Choose Hibernate
    13. Combo box "Database Connection" with sample database and text field "Database Dialect" with value "org.hibernate.dialect.DerbyDialect" should be present.
    14. Click Finish
    15. Run project (F6)

EXPECTED RESULT: New web project is successfully created and no errors appears. It is possible to execute application.

Test suite: Testing actions with project

Purpose: To test action associated with web project.
Setup: Created web project.

  1. Building
    1. Right-click project node.
    2. Invoke Build
    3. Check project is built or a dialog with warning about automatic compile (compile on save) is opened
    4. Invoke Clean and Build
    5. Check project is cleaned and built.
    6. Invoke Clean.
    7. Check project is cleaned.
    8. Invoke Verify.
    9. Check project is verified.
    10. Add new Java class or Servlet to project.
    11. Invoke Generate Javadoc.
    12. Check javadoc is generated, browser is opened and javadoc page shown.
  2. Running
    1. Invoke Run (bug 187474)
    2. Check application is deployed and browser with welcome page is opened.
    3. In source editor change body of welcome page.
    4. Invoke Deploy.
    5. Check project is deployed and when you reload page in browser it shows modified content.
    6. Change again something in editor and save it.
    7. Check status message tells that project was deployed and browser shows modified content after reload.
    8. Open project properties
    9. Go to Run tab and uncheck Deploy on Save.
    10. Click OK.
    11. Change again something in editor and save it.
    12. Check status message about deployment is not displayed.
    13. Invoke Debug.
    14. Check debugger is started and page displayed in browser.
    15. Invoke Profile and confirm all dialogs.
    16. Check profiler is started and welcome page is opened in browser.
  3. Renaming
    1. Invoke Copy and confirm default values.
    2. Check copied project was opened in IDE.
    3. Invoke Rename on previously copied project
    4. Change project name, select "Also Rename Project Folder" and click Rename button.
    5. Invoke Move on renamed project.
    6. Append e.g. "\abcd" to "Project Location" and click Move button.
    7. Warning window with IllegalArgument should appear (this is valid only for GNU/Linux systems and Mac OS X).
    8. Close the warning window and invoke Delete.
    9. Choose "Also delete sources.." and click Yes button.
    10. Check project is cleaned, undeployed and deleted.


Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo