|
|
Browser Quality Assurance
maintained by Beth Epperson beppe@netscape.com
last modified 05/14/99 17:00:00
Contents
I Want To Help Test!
The Browser/Ender QA team wants you, right here, helping us make sure that
we release the best browser and editor on the market. We test a variety
of areas, from checking anchors, to XML, to menus and toolbars. We also
have existing test cases that need to be reviewed and automated - are you
a whiz at JavaScript or Perl? There are many areas where people can
help us out. What would you like to help out with?
Test Case Development:
Test case development and review is an area where we can always use help.
There are a wide variety of areas to cover and tasks to perform.
Here are some specifics:
-
Areas of Need
-
Different Hardware Configurations Testing
-
Test Case Automation
-
Test Case Development
-
Author new test cases using guidelines provided
-
External Web Page Testing
-
Use your own web pages to test the product. You probably already know how
to create web pages and know how to design effective, cutting edge pages.
Submit bugs that you find when viewing your web pages. If you use CSS,
XML, or the new HTML 4.0 elements on your pages, then you will provide us
with valuable information. So go for it, create some cutting edge pages
and see how we stack up to your expectations.
-
Ad hoc testing of other external web pages
-
Feedback
-
Test Cases - would you be willing to review existing test cases and tell
us what you think?
-
Specifications - if you are knowledgeable in a particular area, would you
be willing to convey to us what you know? For example, there are many areas
in the specs that are vague or incomplete, have you had experience in those
areas? Are you willing to be there for us with responsive and articulate
interpretations of those areas of the specs.
-
Submit bugs that are narrowed down and reproducible
-
Identify usability issues
-
Browser/Ender Areas of Responsibility
-
Window Controls
-
Menus (drop-down & contextual), tooltips and dialogs
-
Toolbars
-
Window resize and movement (minimize/maximize/zoom/close/exit)
-
Preferences
-
SmartBrowsing
-
PICS
-
Bookmarks
-
History, cache
-
Cookies
-
Notifications
-
Navigation, shortcuts, accelerators
-
HTML, CSS, XML support
-
Protocols
-
Application integration (copy&paste, drag&drop, clipboard)
-
Imaging (gif, jpeg, png)
-
Ender UI and preferences
-
Ender HTML, CSS, XML support
-
Client-side JavaScript
-
DOM
-
Parsers (CSS, HTML, XML)
-
Event Handling
-
RDF
If you'd like to help out, mail
your name, email address, and area(s) that you are interested in helping
with. Once we have received your note, we will contact you to further discuss
your interests and put together a plan to ensure the areas get covered..
We are not expecting you to commit or promise a lifetime of support.
We want you to feel comfortable in the amount of time and effort that you
would be committing to. We realize that you are volunteering your time and
we appreciate your willingness to jump in and help where the help is needed.
Your personal information will not be used for anything other than communicating
with you about your testing assistance. If you do take a role in the testing
process, your name and email information will be published to the QA
Contacts page.
Thanks for your interest!
Status of Testing
The Browser Basic Functional Test Cases are now posted and available. Any outstanding issues will be posted on the test case access page. Select this link if you are interested in running the Basic Functional Test Cases.
|
