SJSAS 9.1 JMS/MQ Intergration

Test One Pager

Judy He
version 0.9

Oct 14, 2006

Sun Microsystems Propriety/Confidential Internal Use Only

1.0 Introduction
2.0 Objectives
3.0 Feature set covered by SQE
4.0 Feature set not covered by SQE
5.0 Schedule
6.0 Test Methodology
7.0 Compatibility
8.0 Assumptions/Risks
9.0 Approvals
10.0 References
11.0 Revision History

1.0 Introduction

1.1 Overview

Sun SJSAS9.1 JMS/MQ integration new features is about enabling tighter integration of Sun Java System Message Queue 4.1, especially in the areas of improving MSB/JMS performance and HA AS/MQ clusters.

This document simply describes the features, testing schedule and plan for certifying SJSAS9.1 JMS/MQ.

2.0 Objectives

The goals of the testing effort will be to ensure correctness of the implementation, find inconsistencies with respect to the SJS Application Server 9.1 EE JMS/MQ integration one pager and related MQ one pages. The main focus would be testing the interaction between appserver and MQ to ensure that the Application server 9.1 can support MQ 4.1 features in the AS core function area.

3.0 Features set covered by Core SQE

There are two new features in this release: 1) Direct Mode 2) Auto-clustering for the core area. Below outlines what test scenarios will be exercised

1) "Direct" AS/MQ integration Mode

Scenario-1:
Start PE with default MQ broker which is embedded MQ broker. Make sure the MDB/JMS semantics is working properly in this mode on Solaris, Linux and Windows platforms.

Scenario-2:
Start PE. Make sure all existing MDB/JMS tests are working fine without any regression.

Scenario-3:
Modify domain.xml "server.jms-service.type"=DIRECT "server-config.jms-service.type"=DIRECT". Make sure all MDB/JMS tests are working fine without any regression.

Scenario-4:
Modify domain.xml "server.jms-service.type"=DIRECT "server-config.jms-service.type"=DIRECT". Add new webclient test cases in addtion to appclient tese cases. Make sure all tests are passing.

Scenario-5:
Start PE with default embeded mode. Stop domain. Modify JMS mode. Start again and stop several times. Make sure appserver is working properly.

Automate above testing using ANT framework.

Scenario-6:
Start EE DAS with default embeded mode. Stop domain. Modify JMS mode to be DIRECT mode. Start again and stop several times. Make sure appserver is working properly and JMS tests are passing.

2) Auto-clustering of Non-HA AS/MQ clusters

Scenario-1:

Start AS remote AS instance, make sure MQ broker is working with AS properly and all JMS tests are passing without any regression. All AS and MQ semantics is working properly.

Scenario-2:

Start two AS cluster instances, make sure both AS instances are working localy with MQ brokers and MQ borkers are forming MQ cluster transaprently. The JMS cluster tests are passing without any failures. All AS and MQ semantics is working properly.

Scenario-3:

Start three AS cluster instances, make sure MQ brokera are working with AS properly and all JMS tests are passing without any failures. All AS and MQ semantics is working properly.

Scenario-4:

Start two AS cluster instances, make sure both AS instances are working localy with MQ brokers. Atop AS sinatances. Replace the local MQ brokers with remote brokers. Start AS instances. Run JMS cluster tests. Make sure all tests are passing without any failures.

4.0 Features set not covered by Core SQE or assumed to be tested by other groups

I18N
HA cluster support in AS EE

5.0 Schedule, Responsibilities, and Deliverables

5.1 Schedule

5.2 Responsibilities

SUB TEST COMPONENT	OWNER	COMPLETION DATE
"Direct" AS/MQ integration Mode	Judy He	Milestone 3
Auto-clustering of Non-HA AS/MQ clusters	Judy He	Milestone 3

5.3 Deliverables

Test One Pager
Automated Test suites
Bug reports based on testing of the features described above.

6.0 Test Methodology

A set of test cases will be developed/use the existing test applications to cover the identified scenarios. All these test applications will be automated using ant build scripts.

Nightly execution

Nightly EE execution under DAS mode is setup and maintained.
All JMS/MDB tests suites are freshly checkout daily and tested against nightly AS build to ensure JMS/MQ is functioning properly and bug can be identified early

Test environment

Single instance of server or cluster AS instances
Single or cluster MQ broker instances

Test Harness

Uses Ant based framework under the appserver-sqe workspace.

7.0 Compatibility

JMS/MDB test suites that work on AS9.0 PE should work without change in 9.1 EE both clustered and non clustered environments.
All previous developed 8.0, 8.1 JMS/MDB test suites will work automated and consistently on 9.1 EE without any changes.

8.0 Approvals/Reviewers

Reviewers	Function	Date Approved
Sivakumar Thyagarajan	Development Engineer
Srikanth Anandal	Development Manager
Geoffrey Halliwell	SQE Manager	9/28/06
Judy He	SQE Lead

9.0 References

Sun Java System Application Server 9.1 JMS/MQ Intergration One Pager
MQ one pages

10.0 Assumptions/Risks

1. Due to resource limitation with core team in the JMS/QM feature testing area, if there is any conflict in the schedule, priority will be given properly.
2.If there is a problem in test development due to bad build or blocking bug, the following measures will be taken to resume. It is understood that under certain circumstances this may cause a slip in the schedule.
3. Late integration of MQ functionality will also cause the slip in schedule or not enough time for testing.

11.0 Revision History


Editor	Version	Date	Comments
Judy He	0.5	9/8//2006	First draft of test plan
Judy He	0.6	9/15/06	added nightly execution section in test methdology
Judy He	0.9	9/27	added more content to the onepager scenarios based on Siva's feedback