Client QA Component Test Plan: Seamonkey Project
OJIWritten by : Shrirang Khanzode
- Component Features
- Related Areas
- Undocumented Features
- Acceptance Testing
- Functional Testing
- Usability Testing
- Stress Testing
- Regression Testing
- Lab Time
- Other Tools
- Remote Connection
- Schedule link
- Specifications link
- Supported Platforms link
|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|
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.
- Java Applets in web Browser
At present, no automation is being used for testing purposes.
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:
- 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.
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.
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
Other Tools n/a
- Remote Connection
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.
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.
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.
QA Lead ________________________ / /
Eng Lead ________________________ / /
Automation Lead ________________________ / /
Project Manager ________________________ / /
Product Manager ________________________ / /
Dir. of Engineering ________________________ / /
Dir. of Quality Assurance ________________________ / /