What are the summer 2000 interns?

The Seamonkey (mozilla code-based)Project QA teams at Netscape Communications Corp. in Mountain View, CA have four summer 2000 intern positions available.  These positions are for 12-weeks in the May to September 2000 time frame.  We are open to accepting interns in Spring 2000 should you happen to be taking a semester off, or have just graduated in Fall 1999.  Please contact the indicated QA manager listed per the position descriptions below for:
Gecko Standards QA. Browser UE/UI QA, Mail/News QA, Daily Smoke Tester QA.

GECKO STANDARDS QA
Responsibilities

• Perform functional, stress and ad-hoc testing of CSS, XML and HTML support via automated and manual test methodologies
• Investigate failures, enter valid bugs, and report test results in a timely manner
• Create new test cases for the assigned areas, and maintain existing test suites
• Update test specifications and/or test case matrices for new test cases
• Participate on getting automation to run parser and layout test cases
• Test simple elements, attributes, properties or methods with valid data that triggers different Browser functionality
• Testing more complex functionality (test case scenarios from the real world)
• Testing with invalid data
• See the left column of this link, under White Box and DOM Level-0, for the features that need someone to develop and execute tests: http://marvin.mcom.com/testcasenav/indextestcasemarvin.html

Required Skills

• The successful candidate will have broad knowledge in several technical areas as follows:
• HTML, CSS, and XML
• JavaScript and DOM
• Perl and Web server setup
• Unix, Windows and/or Mac
• He/she will be expected to communicate clearly and effectively. The position calls for someone who can be an active team participant, who is capable of identifying complex problems and choosing appropriate solutions.

Contact QA Mgr:  Gerardo Kvaternik   gerardok@netscape.com

BROWSER UE/UI QA
Responsibilities

• Bug verification and pre-screening of external bugs submitted by mozilla.org testers
• We are currently overwhelmed by the sheer numbers of resolved bugs needing verification and new bugs requiring pre-screening to determine if they are in fact valid (checking for duplicates, reproducible test cases, different platforms, reproducibility, etc). An intern could help out greatly here, reducing this burden and allowing us to spend more time testing in our areas of responsibility.

• Coverage of features currently marked 'won't test'.
• As the product development for 5.0 continues, we are identifying certain areas that need more coverage than we initially planned for. These areas include (not an exhaustive list):
• Downloadable/Configurable Chrome is currently slated as 'won't test' due to lack of resources
• Windows Controls (restore, minimize, maximize, etc) is currently slated as 'won't test' due to lack of resources
• Also, other areas will undoubtedly arise as outside developers continue contributing to the mozilla.org project.

• Automation
• We have been tasked to investigate automation opportunities to alleviate some of our manual testing. Currently, we have no one slated to investigate this, much less implement this. An intern could contribute greatly here:

Required Skills

• Javascript and/or C programming skills to understand and then implement automation for front-end Browser and Composer areas
• Knowledge of WindowsNT/95/98, Macintosh, and Linux operating systems to ensure platform parity in automation
• Good communication skills

Contact QA Mgr:  Paul MacQuiddy   paulmac@netscape.com

MAIL/NEWS QA
Responsibilities

• General
• Execution of basic functional tests during milestone periods
• Verification of resolved bugs
• Execution of functional tests for areas including basic functionality, attachments, composition, layout of messages.  For a full listing, please contact me.
• Investigation of problems reported by external and internal users
• Coverage of new mail features submitted by mozilla.org contributors, etc
• We have a few new features which were not planned when we allocated headcount/resources.  We'd like to have these features covered in our group.
• See this link for the features that need someone to write/modify tests and execute them:  http://www.mozilla.org/quality/mailnews/tests/
• We have quite a few "Help Wanted" bugs that may get implemented between now and when 5.0 will ship.  See here for a list of all our HELP WANTED bugs:  http://www.mozilla.org/mailnews/jobs.html
• Coverage of features that require more in-depth coverage than initially planned
• As the product development for 5.0 continues, we are identifying certain areas that need more coverage than we initially planned for. These areas include (not an exhaustive list):
• Profile Migration - we discovered that the coverage for this by the installation group only "touches" the mail preferences.  We decided that more coverage was needed to be devoted to mail migration.
• Mail Performance - this is turning out to be time-consuming, especially if we want to run once a week.  We've worked a bit with development on this and input is to get standard deviations of several runs.  We'd like to be able to enhance our input further by helping out and using Quantify to give even more valuable data.  The person running this is also performing API testing.
• Mail Memory Leak coverage - this is turning out to be very valuable for the mail team.  We've been running this once a week on basic mail functionalities and would like to expand this testing to other mail features.  The person running this is also performing API testing.
• User scenarios - we'd like to have coverage of the basic and advanced user scenarios which our customer-base are likely to run into. This type of testing is more integration testing.  The person working on this area also is covering Account Setup which is turning out to be a large new feature of 5.0.
• Coverage of lab maintenance
• We have machines to recycle and clean up in our lab that can be a time-consuming task.
• We have servers to upgrade.  Need someone to investigate and find the current versions and install them on our machines with minimal downtime.
• We have operating systems to upgrade.

Required Skills

• Organizational - Know where to look for information and resources.  Ability to complete tasks in a timely manner.
• Troubleshooting - Possess methodical troubleshooting techniques to narrow down problems encountered.
• Technical - Unix (Linux), Mac, and Windows skills.  Be knowledgeable with administering and setting up servers including mail and news servers.  Ability to grasp and understand new concepts and features of the product with minimal supervision.
• Communication - excellent written and verbal communication skills.   Ability to report bugs clearly and concisely.   Analyze bug reports reported by external users and ask appropriate questions to narrow problems down.

Contact QA Mgr:  Lisa Chiang   lchiang@netscape.com

DAILY SMOKE TESTER QA
Responsibilities

Run manual smoke test each morning for Win32, Mac and Linux - both the mozilla and commercial bits.

Send out daily report and act as point person for the stability of daily builds.

Review Quality Feedback reports for top crasher bugs and ensure submissiona and follow through for fix via Bugzilla.

Run daily/weekly performance tests on launch, page load, usability perception, composer speed, etc.

Assist with new bug overload in all QA areas as needed.

Assist in testcase execution in all QA areas as needed.

Assist in HW/SW set yp/upgrades within in QA labs as needed.

Assist the QA net community in standardized processes.

Required Skills

Technical - Unix (Linux), Mac, and Windows skills.  Be knowledgeable with setting up OS and application upgrades.  Ability to grasp and understand new concepts and features of the product with minimal supervision.

Organizational - Know where to look for information and resources.  Ability to complete tasks in a timely manner withour much direct supervision.

Troubleshooting - Possess methodical troubleshooting techniques to narrow down problems encountered.

Communication - excellent written and verbal communication skills.   Ability to report bugs clearly and concisely.   Analyze bug reports reported by external users and ask appropriate questions to narrow problems down.

Contact QA Mgr:  Jan Leger   leger@netscape.com