Sun Java System Application Server integration Test Specification
Author: Jaroslav Pospisil
Version: 1.0
Last update: 17-th June 2005
Introduction: There are two variants of installators for Netbeans 4.1.
Basic installation comes without SJS Application server,only with appserver plugin and server itself must be installed externally and added in Runtime tab by
"Add server" option. You can download the appserver here. Simply install it by doubleclicking on "exe" file and then run the NetBeans. Open Runtime tab
window and right-click on "Servers". Choose "Add server" and fill SJS appserver location,admin login name and password in the wizard. Appserver instance
will be added and displayed in the Server tree.
Bundled installation of NB 4.1 has SJS App server 8.1_2 built in and it integrates a SJS Application server through plug-in into the IDE. When you first run
NB4.1 IDE,you have already the application server in Runtime tab. Besides deployment and execution of webmodules/servlets and JSPs it allows to do
a simple server management including working with contexts, logs etc. Note that all debugger functionality and features are not mentioned in this
specification since it is a part of web module debugging test specification.
Purpose: To verify a SJS server instance can be easily added/removed and used within the IDE.
Setup: Install the NB4.1 bundle with SJS Application server 8.1 on your computer
#
Test case
Description
1
Check the default Application server instance presence and default properties.
1. Go to the Runtime window and expand the Server Registry instances nodes. 2. Click on the Sun Java System Application Server 8 node representing the default server installation(instance).
RESULT:
Check if the default instance is present and has set following default properties:
2
Remove default instance
1. Perform 'Remove' action on the default App server installation node
RESULT:
The node should disappear and the server should be stopped.
3
Add the default Application server installation back
1. Perform 'Add New Server...' action on Server registry node. 2. In the opened dialog choose server "Sun Java System Application Server 8. and click "Next" 3. In the next screen fill the App server's Location,user name and password 4. Click on "Finish".
RESULT:
A new subnode representing the Application server should appear under the Server registry node.
4
Add a new Application server installation
1. Perform 'Add New Server...' action on Server registry node. 2. In the opened dialog choose server "Sun Java System Application Server 8. and click "Next" 3. In the next screen fill the App server's Location,user name and password 4. Click on "Finish".
RESULT:
A new subnode representing newly added Application server should appear under the Server registry node.
5
Check properties of the added Application server installation
1. Select the new Application server node and check its properties.
RESULT:
If you haven't made any changes in your Application server installation, most of the properties values should be the same as in case of the internall Application server installation.
Purpose: To verify a Application server instance is working propertly and all its actions and properties do what they are supposed to do.
Setup: Use any of SJS appserver installations mentioned above.
#
Test case
Description
1
Start Application server
1. Perform 'Start / Stop Server' action on the Application server instance node. 2. In the opened dialog press 'Start Server' button and wait until the server is running.
RESULT:
The server should be successfully started. Check if there are startup messages in a output window. Verify if the instance node can be expanded and contains a list of deployed webmodules. Try to deploy a webmodule to verify if the server is running properly.
2
Start another Application server
1. Add new Application server installation into the IDE 2. Perform 'Start / Stop Server' action on the Application server instance node. 3. In the opened dialog press 'Start Server' button and wait until the server is running.
RESULT:
The server should be successfully started. Check if there are startup messages in a output window. Verify if the instance node can be expanded and contains a list of deployed webmodules. Try to deploy a webmodule to verify if the server is running properly.
3
Stop Application server
1. Perform 'Start / Stop Server' action on the Application server instance node. 2. In the opened dialog verify that the 'Server is running' status is displayed and press 'Stop Server'.
RESULT:
The server should be successfully stopped. You can verify it by opening server URL in your browser (e.g. http://localhost:4849. The browser shouldn't be able to connect.
4
Start Application server debug
1. Perform 'Start / Stop Server' action on the Application instance node. 2. In the opened dialog press 'Start Server (Debug)' button and wait until the server is running.
RESULT:
The server should be successfully started. Check if there are startup messages in a output window. Verify if the instance node can be expanded and contains a list of deployed webmodules. Try to deploy a webmodule to verify if the server is running properly.
5
View Application server Admin console and server log
1. Start Application server . 2. Perform 'View Admin console' and 'View Server log' actions on the instance node.
RESULT:
1.The Admin console should be opened in the browser. 2.The server log should be opened in the output window and its content should be updated as the server appends something to them.
Purpose: To verify that the Application server contexts management works properly.
Setup: Use any of SJS appserver installations mentioned above.
#
Test case
Description
1
View deployed web applications
1. Start Application server instance. 2. Expand its node.
RESULT:
The instance node should contain 'Applications/Web Applications' subnode which has children representing deployed web applications (contexts).
2
Refresh the web applications list
1. Start default Application server instance. 2. Start Admin console application in you browser by right clicking on SJS Application Server node in Runtime tab and choosing it 3. In the web interface undeploy a web application. 4. Perform 'Refresh' action on Web Applications node
RESULT:
The children nodes should be updated according to the changes you have made.
3
Undeploy a web application
1. Perform 'Undeploy' action on an web application's node.
RESULT:
The node should disappear and the apllication should be undeployed. Verify if the application is really undeployed by opening its context in your browser (http://localhost:8080/WebApplication.
4
Stop a webmodule
1. Perform 'Disable' action on an web application's node.
RESULT:
In node's properties should Disable change to Enable.
5
Start a webmodule
1. Perform 'Enable' action on an web application's node.
RESULT:
In node's properties should Enable change to Disable.
Purpose: To verify that Project Properties Panel works properly.
Setup: Use any of SJS appserver installations mentioned above.Create new Project - Web Application with 2 JSP pages locatad in WEB-INF directory, e.g. index.jsp and index2.jsp.
Minimal two Application server instances have to be installed.
#
Test case
Description
1
Change target server per project
1. Go to Projects window 2. Right-click on the root node of your web project 3. Click on Properties 4. Go to Run - Running Project node 5. From Server select box select one server's instance 6. Click OK button 7. Right-Click on the root node of your application 8. Choose Run Project
RESULT:
Your application should deploy on selected server
2
Change relative URL
1. Go to the Projects tab 2. Select the root node of your web project 3. From contextual menu choose Properties item 4. Go to Run - Running Project node 5. Into Relative URL text box type second page's relative URL, e.g. index2.jsp 6. Click OK button 7. Run project
RESULT:
Output window must display correct URL: http://localhost:port/$CONTEXT/Relative URL.
Purpose: Test web module project dependencies on CVS
Setup: Use any of SJS appserver installations mentioned above.Create new web project and new versioned directory
#
Test case
Description
1
Change context path
1. Go to Files tab 2. Select project node and Add project into CVS tree 3. Right-click on project node 4. On Project Properties Panel change context path 5. Run project 6. Commit project into CVS 7. Close Project 8. Go to Versioning tab and Check Out created project 9. Open project and Run
RESULT:
After running Project ,external browser shall load project with correct context path.
2
Change relative URL
1. Go to Files tab 2. Select project node and Add project into CVS tree 3. Right-click on project node 4. On Project Properties Panel change target server 5. Run project 6. Commit project into CVS 7. Close Project 8. Go to Versioning tab and Check Out created project 9. Open project and Run
RESULT:
After running Project ,external browser shall load source found on Full URL.
