Headless Deployment Test Specification

Author: Jiri Skrivanek
Version: 1.1
Last update: 2006/04/06
Introduction: This is test specification of headless deployment. The aim of headless deployment is to reduce the number of changes which are necessary in order to make building, deployment, etc. of NB projects work without the IDE.
Comment: Supported servers are only Tomcat 5.5.x and Glassfish. Tomcat doesn't support re-deploy (i.e. it is not possible to deploy the same application twice over). On Unix can be problem to detect default browser.

Table of Contents

Test suite 1: Tomcat Web Application

Purpose: Test headless deployment on the same computer the project was created, on a different computer than the project was created and with project from CVS repository.
Setup:

#Test caseDescription
1Prepare application
  1. Create a new Web Application from template (use bundled Tomcat server).
  2. Go to Runtime view and open properties of Servers|Bundled Tomcat instance.
  3. Change default port to something else.
  4. Start the server.
2Test command line for Tomcat Web Application
  1. Open command line and go to project folder.
  2. Execute 'ant run-deploy' command.
  3. Check build was finished successfully and application is listed in Runtime view under server instance.
  4. Execute 'ant run-undeploy' command.
  5. Check build was finished successfully and application is not listed in Runtime view under server instance.
  6. Execute 'ant run' command.
  7. Check build was finished successfully and index.jsp page is opened in browser.
Teardown: Execute 'ant run-undeploy' command.
3Copy project
  1. Clean project.
  2. Import project into CVS repository (call 'CVS|Import into Repository' on project node).
  3. Copy project to a different computer.
4Test command line for copied project
Setup:Start IDE on different computer, open project and start Tomcat server.
  1. Open command line and go to project folder.
  2. Execute 'ant run-deploy' command.
  3. Check build was finished successfully and application is listed in Runtime view under server instance.
  4. Execute 'ant run-undeploy' command.
  5. Check build was finished successfully and application is not listed in Runtime view under server instance.
  6. Execute 'ant run' command.
  7. Check build was finished successfully and index.jsp page is opened in browser.
Teardown: Execute 'ant run-undeploy' command.
5Test command line for project from CVS
Setup:Checkout project from CVS repository and open it in IDE.
  1. Open command line and go to project folder.
  2. Execute 'ant run-deploy' command.
  3. Check build was finished successfully and application is listed in Runtime view under server instance.
  4. Execute 'ant run-undeploy' command.
  5. Check build was finished successfully and application is not listed in Runtime view under server instance.
  6. Execute 'ant run' command.
  7. Check build was finished successfully and index.jsp page is opened in browser.
Teardown: Execute 'ant run-undeploy' command.

Test suite 2: Glassfish Enterprise, EJB, Web, Client Applications on the same computer

Purpose: Test headless deployment on the same computer the project was created.
Setup: Install Glassfish server from http://glassfish.dev.java.net.

#Test caseDescription
1Prepare Enterprise Application
  1. Go to Runtime view and add Glassfish server instance.
  2. Start Glassfish server.
  3. Create a new Enterprise Application project from template (use Glassfish server and check Application Client to be created).
  4. Add JDBC Resource: Open new file wizard in Enterprise application project, select Sun Resources|JDBC Resource and go through the wizard. There should be created a connection pool and dataresource under Server Resources node.
  5. Create a new session bean in enclosed EJB project.
2Test command line for Enterprise Application
  1. Open command line and go to project folder.
  2. Execute 'ant run-deploy' command.
  3. Check build was finished successfully. Application and JDBC resources should be listed in Runtime view under server instance.
  4. Execute 'ant run-undeploy' command.
  5. Check build was finished successfully and application is not listed in Runtime view under server instance.
  6. Execute 'ant run' command.
  7. Check build was finished successfully and index.jsp page is opened in browser.
Teardown: Execute 'ant run-undeploy' command.
3Test command line for EJB Application
  1. Open command line and go to EJB sub project folder.
  2. Execute 'ant run-deploy' command.
  3. Check build was finished successfully and application is listed in Runtime view under server instance.
  4. Execute 'ant run-undeploy' command.
  5. Check build was finished successfully and application is not listed in Runtime view under server instance.
  6. Execute 'ant run' command.
  7. Check build was finished successfully.
Teardown: Execute 'ant run-undeploy' command.
4Test command line for Web Application
  1. Open command line and go to WAR sub project folder
  2. Execute 'ant run-deploy' command.
  3. Check build was finished successfully and application is listed in Runtime view under server instance.
  4. Execute 'ant run-undeploy' command.
  5. Check build was finished successfully and application is not listed in Runtime view under server instance.
  6. Execute 'ant run' command.
  7. Check build was finished successfully and index.jsp page is opened in browser.
Teardown: Execute 'ant run-undeploy' command.
5Test command line for Application Client
  1. Open command line and go to APP-CLIENT sub project folder
  2. Execute 'ant run-deploy' command.
  3. Check build was finished successfully and application is listed in Runtime view under server instance.
  4. Execute 'ant run-undeploy' command.
  5. Check build was finished successfully and application is not listed in Runtime view under server instance.
  6. Execute 'ant run' command.
  7. Check build was finished successfully and index.jsp page is opened in browser.
Teardown: Execute 'ant run-undeploy' command.

Test suite 3: Glassfish Enterprise, EJB, Web, Client Applications on different computer

Purpose: Test headless deployment on a different computer than the project was created.
Setup: Install Glassfish server from http://glassfish.dev.java.net.

#Test caseDescription
1Copy Enterprise Application
  1. Clean project.
  2. Copy project to a different computer.
  3. Start IDE on that different computer.
  4. Go to Runtime view and add Glassfish server instance.
  5. Start Glassfish server.
  6. Open project in IDE.
  7. Resolve all reference problems and then open all sub projects using 'Open Required Projects' action on project node.
2Test command line for Enterprise Application
  1. Open command line and go to project folder.
  2. Execute 'ant run-deploy' command.
  3. Check build was finished successfully. Application and JDBC resources should be listed in Runtime view under server instance.
  4. Execute 'ant run-undeploy' command.
  5. Check build was finished successfully and application is not listed in Runtime view under server instance.
  6. Execute 'ant run' command.
  7. Check build was finished successfully and index.jsp page is opened in browser.
Teardown: Execute 'ant run-undeploy' command.
3Test command line for EJB Application
  1. Open command line and go to EJB sub project folder.
  2. Execute 'ant run-deploy' command.
  3. Check build was finished successfully and application is listed in Runtime view under server instance.
  4. Execute 'ant run-undeploy' command.
  5. Check build was finished successfully and application is not listed in Runtime view under server instance.
  6. Execute 'ant run' command.
  7. Check build was finished successfully.
Teardown: Execute 'ant run-undeploy' command.
4Test command line for Web Application
  1. Open command line and go to WAR sub project folder
  2. Execute 'ant run-deploy' command.
  3. Check build was finished successfully and application is listed in Runtime view under server instance.
  4. Execute 'ant run-undeploy' command.
  5. Check build was finished successfully and application is not listed in Runtime view under server instance.
  6. Execute 'ant run' command.
  7. Check build was finished successfully and index.jsp page is opened in browser.
Teardown: Execute 'ant run-undeploy' command.
5Test command line for Application Client
  1. Open command line and go to APP-CLIENT sub project folder
  2. Execute 'ant run-deploy' command.
  3. Check build was finished successfully and application is listed in Runtime view under server instance.
  4. Execute 'ant run-undeploy' command.
  5. Check build was finished successfully and application is not listed in Runtime view under server instance.
  6. Execute 'ant run' command.
  7. Check build was finished successfully and index.jsp page is opened in browser.
Teardown: Execute 'ant run-undeploy' command.

Test suite 4: Unsupported server

Purpose: Test headless deployment with unsupported server.
Setup:

#Test caseDescription
1Prepare application
  1. Go to Runtime view and add JBoss or other unsupported server instance.
  2. Create a new Web Application from template (use JBoss server).
2Test command line for unsupported server
  1. Open command line and go to project folder.
  2. Execute 'ant run-deploy' command.
  3. Check build failed with descriptive message like this: 'Deploy is not supported for the current target server'.
  4. Repeat for 'ant run-undeploy' and 'ant run' commands.

Generated: 2006 04 06 05:39

Project Features

About this Project

QA was started in November 2009, is owned by Jiří Kovalský, and has 97 members.
By use of this website, you agree to the NetBeans Policies and Terms of Use (revision 20160708.bf2ac18). © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo
 
 
Close
loading
Please Confirm
Close