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.
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 case
Description
1
Prepare application
Create a new Web Application from template (use bundled Tomcat server).
Go to Runtime view and open properties of Servers|Bundled Tomcat instance.
Change default port to something else.
Start the server.
2
Test command line for Tomcat Web Application
Open command line and go to project folder.
Execute 'ant run-deploy' command.
Check build was finished successfully and application is listed in Runtime view under server
instance.
Execute 'ant run-undeploy' command.
Check build was finished successfully and application is not listed in Runtime view under
server instance.
Execute 'ant run' command.
Check build was finished successfully and index.jsp page is opened in browser.
Teardown:
Execute 'ant run-undeploy' command.
3
Copy project
Clean project.
Import project into CVS repository (call 'CVS|Import into Repository' on project node).
Copy project to a different computer.
4
Test command line for copied project
Setup:Start IDE on different computer, open project and start Tomcat server.
Open command line and go to project folder.
Execute 'ant run-deploy' command.
Check build was finished successfully and application is listed in Runtime view under server
instance.
Execute 'ant run-undeploy' command.
Check build was finished successfully and application is not listed in Runtime view under
server instance.
Execute 'ant run' command.
Check build was finished successfully and index.jsp page is opened in browser.
Teardown:
Execute 'ant run-undeploy' command.
5
Test command line for project from CVS
Setup:Checkout project from CVS repository and open it in IDE.
Open command line and go to project folder.
Execute 'ant run-deploy' command.
Check build was finished successfully and application is listed in Runtime view under server
instance.
Execute 'ant run-undeploy' command.
Check build was finished successfully and application is not listed in Runtime view under
server instance.
Execute 'ant run' command.
Check build was finished successfully and index.jsp page is opened in browser.
Purpose: Test headless deployment on the same computer the project was created.
Setup:
Install Glassfish server from http://glassfish.dev.java.net.
#
Test case
Description
1
Prepare Enterprise Application
Go to Runtime view and add Glassfish server instance.
Start Glassfish server.
Create a new Enterprise Application project from template (use Glassfish server and check Application Client to be created).
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.
Create a new session bean in enclosed EJB project.
2
Test command line for Enterprise Application
Open command line and go to project folder.
Execute 'ant run-deploy' command.
Check build was finished successfully. Application and JDBC resources should be listed in Runtime view under server instance.
Execute 'ant run-undeploy' command.
Check build was finished successfully and application is not listed in Runtime view under server instance.
Execute 'ant run' command.
Check build was finished successfully and index.jsp page is opened in browser.
Teardown:
Execute 'ant run-undeploy' command.
3
Test command line for EJB Application
Open command line and go to EJB sub project folder.
Execute 'ant run-deploy' command.
Check build was finished successfully and application is listed in Runtime view under server
instance.
Execute 'ant run-undeploy' command.
Check build was finished successfully and application is not listed in Runtime view under
server instance.
Execute 'ant run' command.
Check build was finished successfully.
Teardown:
Execute 'ant run-undeploy' command.
4
Test command line for Web Application
Open command line and go to WAR sub project folder
Execute 'ant run-deploy' command.
Check build was finished successfully and application is listed in Runtime view under server
instance.
Execute 'ant run-undeploy' command.
Check build was finished successfully and application is not listed in Runtime view under
server instance.
Execute 'ant run' command.
Check build was finished successfully and index.jsp page is opened in browser.
Teardown:
Execute 'ant run-undeploy' command.
5
Test command line for Application Client
Open command line and go to APP-CLIENT sub project folder
Execute 'ant run-deploy' command.
Check build was finished successfully and application is listed in Runtime view under server instance.
Execute 'ant run-undeploy' command.
Check build was finished successfully and application is not listed in Runtime view under server instance.
Execute 'ant run' command.
Check build was finished successfully and index.jsp page is opened in browser.
Purpose: Test headless deployment on a different computer than the project was created.
Setup:
Install Glassfish server from http://glassfish.dev.java.net.
#
Test case
Description
1
Copy Enterprise Application
Clean project.
Copy project to a different computer.
Start IDE on that different computer.
Go to Runtime view and add Glassfish server instance.
Start Glassfish server.
Open project in IDE.
Resolve all reference problems and then open all sub projects using
'Open Required Projects' action on project node.
2
Test command line for Enterprise Application
Open command line and go to project folder.
Execute 'ant run-deploy' command.
Check build was finished successfully. Application and JDBC resources should be listed in Runtime view under server instance.
Execute 'ant run-undeploy' command.
Check build was finished successfully and application is not listed in Runtime view under server instance.
Execute 'ant run' command.
Check build was finished successfully and index.jsp page is opened in browser.
Teardown:
Execute 'ant run-undeploy' command.
3
Test command line for EJB Application
Open command line and go to EJB sub project folder.
Execute 'ant run-deploy' command.
Check build was finished successfully and application is listed in Runtime view under server
instance.
Execute 'ant run-undeploy' command.
Check build was finished successfully and application is not listed in Runtime view under
server instance.
Execute 'ant run' command.
Check build was finished successfully.
Teardown:
Execute 'ant run-undeploy' command.
4
Test command line for Web Application
Open command line and go to WAR sub project folder
Execute 'ant run-deploy' command.
Check build was finished successfully and application is listed in Runtime view under server
instance.
Execute 'ant run-undeploy' command.
Check build was finished successfully and application is not listed in Runtime view under
server instance.
Execute 'ant run' command.
Check build was finished successfully and index.jsp page is opened in browser.
Teardown:
Execute 'ant run-undeploy' command.
5
Test command line for Application Client
Open command line and go to APP-CLIENT sub project folder
Execute 'ant run-deploy' command.
Check build was finished successfully and application is listed in Runtime view under server instance.
Execute 'ant run-undeploy' command.
Check build was finished successfully and application is not listed in Runtime view under server instance.
Execute 'ant run' command.
Check build was finished successfully and index.jsp page is opened in browser.