OpenPortal^? WSRP V2.0 Test Plan

1.0 Introduction

The scope of OASIS WSRPv2.0 testing is to test the major versions of v2 specification along with a successful backward compatilibility of WSRP v1 specification.

The WSRPv2.0 will be integrated and tested with Porltet Container 2.0 (PC2.0) of Beta Quality. The Portlet Container comes with the Portlet Container Driver which acts as a minimalistic portal and is used to test the WSRP.

2.0 Resource Requirements

2.1 Hardwares to be tested

• Solaris 10 SPARC
• Solaris 10 X86
• Linux 4
• Win XP Professional
• Win Vista Business
• Mac Intel

2.2 Softwares to be tested:

2.3 Hardware Not Tested:

• Win 2003
• Mac PPC

2.4 Staffing

• QA1 Bharanidharan Anantharaman

3.0 Features to be tested

3.1 WSRP - SDK Installation

• 3.1.1 Installation and Deployment of Portlet Container on Appserver/Glasfish V2

3.2 WSRP Functionality

• 3.2.1 Create WSRP Producer
  • 3.2.1.1 The WSRP Producer implementation would support both v1 and v2 version of the protocol.
  • 3.2.1.2 The Producer would generate both v1 and v2 service in a single WSDL.
  • 3.2.1.3 The WSRP resources (like registrationHandle) will be shared across v1 and v2 services.

• 3.2.2 Create WSRP Consumer
  • 3.2.2.1 Would provide a consumer implementation to support a WSRP v1 Producer
  • 3.2.2.2 Would provide a consumer implementation to support a WSRP v2 Producer.
  • 3.2.2.3 Incase the WSRP producer implementation provides both v1 and v2 service, in a single WSDL, The consumer will provide a option to use either of the service to the user/administrator.
  • 3.2.2.4 The WSRP consumer MAY provide a option to switch a v1 consumer to a v2 consumer provided if the producer exports both v1 and v2 services in a single WSDL.

• 3.2.3 Features of WSRP v2.0 Specifition to be tested both in Consumer and Producer
  • 3.2.3.1 Eventing
    • 3.2.3.1.1 A local portlet should be able to throw a event to a remote portle
    • 3.2.3.1.2 A remote portlet should be able to throw a event to local portlet
    • 3.2.3.1.3 A remote portlet should be able to throw a event to another remote portlet (from a different Producer)
  • 3.2.3.2 Shared Render Parameters
    • 3.2.3.2.1 A local portlet should be able to share a public render parameter to a remote portlet
    • 3.2.3.2.2 A remote portlet should be able to share a public render parameter to local portlet
    • 3.2.3.2.3 A remote portlet should be able to share a public render parameter to another remote portlet (from a different Producer)
  • 3.2.3.3 Resource Sharing
  • 3.2.3.4 Caching * 3.2.3.5 Support for the following features (optional)
    • 3.2.3.5.1 Support import and export of portlets implementation
    • 3.2.3.5.2 Support for CC/PP headers
• 3.2.4 Adding of remote portlet in a Channel
• 3.2.5 Testing the remote portlet

4.0 Features not to be Tested

• 4.1 User Behaviour Tracking
• 4.2 Parallel Rendering
• 4.3 Cookies and Header information

5.0 Testing Approach

Tested manually . Near future plan to automate using Selenium a open source test tool.

5.1 Topologies to be tested.

5.2 Test deliverables

• Test Plan
• Test Cases
• Test Reports
• Metrics

6.0 Dependencies / Risks:

• Performance not tested.
• Limitation on resources . There is only one dedicated resource available.
• Regression: Any regression arising in the later stage might cause a problem and schedule slippage.
• Bug fixes coming in later stages adds to the risks.

7.0 References:

• Open Source WSRPv2.0 - https://wsrp.dev.java.net
• Project Schedule - https://wsrp.dev.java.net/public/releases/wsrpv2/index.html
• Product Concept Document http://wiki.java.net/bin/view/OpenPortal/WSRPv2
• Product Plans and Functional Specification http://wiki.java.net/bin/view/OpenPortal/WSRPv2FSD

8.0 Reviews and Approvals

9.0 Revision History

-- Main.t_rajesh - 20 Mar 2008