You are here: Browser/Composer front-end QA > front-end test plans > OJI Test Plan
Client QA Component Test Plan: Seamonkey Project
OJI
Written by : Shrirang KhanzodeEmail shrir@netscape.com
1. COMPONENT
- Description
- Component Features
- Related Areas
- Undocumented Features
4. APPROACH
- Strategy
- Automation
- Acceptance Testing
- Functional Testing
- Usability Testing
- Stress Testing
- Regression Testing
5. RESOURCES
- Software
- Hardware
- Data
- Lab Time
- Other Tools
- Network
- Remote Connection
- Off-line
- Schedule link
- Specifications link
- Supported Platforms link
- Automation
Document Change History:
| Date | Change Description | Revision | Updated By |
|---|---|---|---|
| June 07, 2000 | initial draft | 1.0 | S. Khanzode |
| Dec 18, 2000 | Updates and minor additions | 1.1 | S. Khanzode |
1.Component
Description
The Open JVM Integration project (OJI) is working to extend the browser to allow Java virtual machines to be plugged into Mozilla. OJI will allow the applet, embed and object tags to show Java applets on a page and support LiveConnect (the bridge between Java and JavaScript). Most of the OJI project involves extending the existing Plug-in API to define what is called the Open JVM Plug-in API.
What does this mean for end-users? :
- Applets and LiveConnect running in Mozilla,
- a choice of Java virtual machines in Netscape 6.0,
- backward compatibility with previous Communicator Releases,
- a chance to migrate to JVMs supporting Java 1.2 and future versions.
For Java developers, this means:
- ability to write Java code depending on newer versions of Java and AWT,
- backward compatibility for Java code between Communicator Releases,
- choice of JVMs when deploying Java-based browser applications.
And for Java VM providers:
- a vehicle for delivering their Java virtual machine to the web user community,
- opportunity to continue to enhance Java support in Mozilla and Communicator
OJI currently supports windows and macintosh platforms. There is no java support on linux at this moment.
2.Areas To Be Tested
Component Features
- Java Applets in web Browser
3.What Will Not Be Tested
4.Approach
Strategy
Various applets on the Sun Java site should be run and tested to test java functionality. Testcases that cover the HTML tags, mainly, APPLET, EMBED and OBJECT should be constructed. The lifecycle of an applet should also be tested by creating testcase applets consisting of the init(), start(), stop() and destroy() methods. Liveconnect functionality also needs to be tested. This would cover testing of Java to Javascript and Javascript to Java calls. One important thing to be noted is that since most of the java applets on the internet are JDK 1.0 or 1.1.x based, which means that they are actually compiled with old java compilers, such applets might not work in Netscape6 (which has JRE 1.3). To avoid this problem , all the old java applets will need to be compiled using the latest JDK ie JDK1.3 and then run in Netscape6 to test them.
Automation
At present, no automation is being used for testing purposes.
Acceptance Testing
Acceptance tests should basically cover the following:
- java.sun.com webpage applet should load fine
- Applet within <APPLET> tag should load fine
Functional and Usability Testing
The functional areas and features/functions to be tested for OJI /Java are as follows:
- Tags
- Lifecycle of an applet
- Liveconnect functionality
HTML tags would basically be the APPLET, EMBED and OBJECT tags. All the testcases covering the above mentioned features can be found here.
In addition to these tests, sample java applets on the sun java site should be run and tested in Netscape6. They are available here. Also, web sites with embedded java applets should be visited. java.sun.com , gamelan.com are a good starting point.
Stress, Regression Testing
- Loading applets in a quick succession
- Reloading applets on a webpage
- Loading multiple applets in multiple browser windows
- Loading very large sized applets and checking memory performance
Reviewing previously written bug submissions and creating a suite of test cases to correspond to those submissions will be of great value in ensuring that previous issues have not been reintroduced.
5.RESOURCES
Software
OS/ System Software
Please see the Seamonkey Platforms link at http://client/seamonkey/prd/seamonkey_platforms.html for a description of the hardware/software to be used in testing.
Hardware
Computers
Please see the Seamonkey Platforms link at http://client/seamonkey/prd/seamonkey_platforms.html for a description of the hardware/software to be used in testing
Data
n/a
Lab Time
n/a
Other Tools n/a
- Network
- Remote Connection
- Off-line
6.CONTINGENCIES
Loss of Test Machine Resources
While highly unlikely there is the possibility that Test Machines could break down. Planning should be done, by each component area to ensure there are reserves of equipment to be drawn upon.
Bugs
If outstanding bug counts do not drop and cannot be mitigated between QA, Engineering, and Marketing there is the potential that the project schedule may have to slip. The time increment will be agreed to by the project leads.
Builds
There is the potential for build crisises to arise (tree spammage, etc.) which can impact QA and Engineering getting code to use for their work, and therefore adversely affect the schedule. Some planning should be done in this area in anticipation of the most probable things that could go wrong.
7.SIGNOFF APPROVAL
Name Date
QA Lead ________________________ / /
Eng Lead ________________________ / /
Automation Lead ________________________ / /
Project Manager ________________________ / /
Product Manager ________________________ / /
Dir. of Engineering ________________________ / /
Dir. of Quality Assurance ________________________ / /