HOME > Community > Projects > qa

JBoss 4 Application Server integration Test Specification

Author: Jaroslav Pospisil
Version: 1.0
Last update: 12-th September 2005
Introduction: JBoss plugin is one of new features in NB5.0 .
Its functionality is the simplified one to the previously introduced functionality of Sun Java System Appserver 8
and along with BEA Weblogic 9.0 Diablo plugin it enable basic interface for starting server,stopping it and
deployment/debug actions.Both plugins are part of NB5 build and works with local server installation.

You have to install JBoss 4 on your computer before start testing.
Latest version you can found here

1. Server registry
2. Server manager
3. JBoss server instance
4. Web modules
5. JBoss deployment descriptor

Test suite 1: Server registry

Purpose: To verify a JBoss server instance can be easily added/removed and used within the IDE.
Setup: Install the JBoss 4 server on your computer.

# Test case Description

1 Add a JBoss server installation

1. Perform 'Add New Server...' action on Servers node.
2. In the opened dialog choose server "JBoss Application Server 4.0. and click "Next"
3. In the next screen fill the JBoss server's Location and click "Next"
4. On the next page you click on "Finish".

RESULT: A new subnode representing newly added JBoss server should appear under the Server registry node.

2 Remove JBoss server instance

1. Perform 'Remove' action on the JBoss server installation node

RESULT: The node should disappear and the server should be stopped.

3 Check properties of the JBoss 4 server installation

1. Select the JBoss 4 server node and check its properties.

RESULT: Server manager should appear with JBoss 4 server selected.You could check the properties of this server

Teardown:

Test suite 2: Server Manager

Purpose: To verify if Server Manager if is working propertly with a JBoss server instance and all its actions and properties do what they are supposed to do.
Setup: Install the JBoss 4 server on your computer.

Test case

Description

Add JBoss server

1.Open Tools/Server Manager
2.Click on Add Server
3. In the opened dialog choose server "JBoss Application Server 4.0" and click "Next"
4. In the next screen fill the App server's Location,user name and password
5. Click on "Finish".

RESULT: A new subnode representing the JBoss server should appear under the Server manager list and corresponding properties should be displayed.

Remove JBoss server

1. Open Tools/Server Manager
2. Select "JBoss Application Server 4.0".
Click on Remove.

RESULT: The server name should disappear from list and the server should be stopped.

Teardown:

Test suite 3: JBoss 4 server instance

Purpose: To verify a JBoss 4 server instance is working propertly and all its actions and properties do what they are supposed to do.
Setup: Install the JBoss 4 server on your computer.d for both command sets.

# Test case Description

1 Start JBoss 4 server

1. Perform 'Start' action on the JBoss server instance node.

RESULT: The server should be successfully started. Check if there are startup messages in a output window. Verify if server node icon in Runtime tab changed responding to new status of server.Verify if in output window are on the left side displayed correct command icons(they represent the commands from context menu for server node),Start icon should be disabled .

2 Stop JBoss server

1. Perform 'Stop' action on the JBoss server instance node.

RESULT: The server should be successfully stopped. You can verify it by opening server URL in your browser (e.g. http://localhost:4848. The browser shouldn't be able to connect.Command icons in Output window should respond by disabling Stop and enabling Start.

3 Restart JBoss server

1. Perform 'Restart' action on the JBoss instance node.

RESULT: The server should be successfully restarted. Check if there are startup messages in a output window. Verify if server node icon in Runtime tab changed responding to new status of server.Verify if in output window are on the left side displayed correct command icons(they represent the commands from context menu for server node),Start icon should be disabled .

4 Start JBoss server debug

1. Perform 'Start in Debug Mode' action on the JBoss instance node.

RESULT: The server should be successfully started. Check if there are startup messages in a output window. Verify if server node icon in Runtime tab changed responding to new status of server.Verify if in output window are on the left side displayed correct command icons(they represent the commands from context menu for server node),Start icon should be disabled .

5 Refresh server status

1. Perform 'Refresh' action on the JBoss instance node.

RESULT: Server status shoul be refreshed responding to all changes done,even those done outside the IDE.

6 Test command icons in Output window

1. Perform all previous actions from command interface in Output window.

RESULT: Should be the same as previously.

7 View JBoss server Admin console

1. Start JBoss server .
2. Perform 'View Admin console' action on the instance node.

RESULT: 1.The Admin console should be opened in the browser.

Teardown:

Test suite 4: Web modules

Purpose: To verify that the JBoss 4 server contexts management works properly.
Setup: Install the JBoss 4 server on your computer.

# Test case Description

1 Deploy a new webmodule

1. Create web module on JBoss 4 server.
2. Perform 'Run Project' or 'Deploy project' action on web project's node on Projects tab.

RESULT: Module should be deployed(verify it in JBoss Admin console) and index.jsp opened in web browser.

2 Debug a new webmodule

1. Create web module on JBoss 4 server.
2. Perform 'Debug project' action on web project's node on Projects tab.

RESULT: Module should be deployed(verify it in JBoss Admin console) and index.jsp opened in web browser.Debugger window should appear in IDE.

Teardown:

Test suite 5: JBoss deployment descriptor

Purpose: To verify that the JBoss 4 server generates proper server specific descriptor file.
Setup: Install the JBoss 4 server on your computer.

# Test case Description

1 Check JBoss deployment descriptor

1. Create web module on JBoss 4 server.
2. Go to Files tab and unpack "YourWebModule/web/WEB-INF" node.

RESULT: Check if there ic correctly created file "jboss-web.xml" and inside is correctly set context path of your web module.Try to change it in Project properties nad check if it reflects the changes.

Teardown: