There are many things you can do to help out with the Mozilla project in the QA department, and all of them don't require being able to code. A few of them don't even require knowing any HTML or other web technologies. If you are interested in helping us out with testing and other QA activities, you should first see quality.mozilla.org.
- Bug writing guidelines
- The more effectively a bug is reported, the more likely that an engineer will actually fix it. By following these guidelines, you can help ensure that your bugs stay at the top of the Mozilla engineers' heap, and get fixed.
- Confirming unconfirmed bugs
- Identify useful bug reports from end-users and close the rest.
- How to screen out duplicate bug reports
- Help get bugs fixed faster by avoiding filing duplicate reports, or by screen incoming reports for duplicates.
- Reducing testcases
- Improve bug reports by turning broken web pages into simple testcases, which can help developers understand the bug and can also be used for creating automated tests.
- Developing tests
- Ensure that future changes to Mozilla don't break things that currently work correctly.
- Avoiding intermittent oranges
- Suggestions for ways to make your tests more reliable, thereby helping to avoid random, intermittent test failures.