Secret Mustache

Adventures of a Scruffy Nerf Herder

Mozillians Testplan

23 February 2013

Manual Testing

Welcome to the Mozillians project - A community phonebook to share, identify and communicate with other Mozillians in our community. If this is your first time working on a project at Mozilla or you're a seasoned veteran this is a great project to get involved on.

Mozillians.org homepage

Exploratory Testing

Exploratory testing is a great way to contribute to the Mozillians project. Many of our integration and functional tests have been automated, but automated tests are best at catching the bugs we can anticipate. Exploratory testing catches the truly interesting bugs -- the ones we haven’t imagined yet -- and gives testers an opportunity to learn about the Mozillians project and platform.

“The main advantage of exploratory testing is that less preparation is needed, important bugs are found quickly, and at execution time, the approach tends to be more intellectually stimulating than execution of scripted tests.” Wikipedia

There are several schools of thought on what exploratory testing is. For our purpose we’ll treat it as a testing approach where a tester through creativity and curiosity seeks to find out how the software works. An exploratory tester simply looks at and uses the software as a normal user might, and asks questions on behalf of the users. This approach reveals places where the software does not behave as expected -- in other words, bugs!

Audience

The Mozillians project targets several different types of users:

  • Community members who want to connect with others in the community in order to learn more about them and/or form groups around interests and skills
  • Community organizers who want to reach out to groups of people that identify with particular interests
  • Developers who want to use the API to power their own applications

Testing

Explore!

Your mission if you choose to accept is to creatively explore the Mozillians website, keeping in mind the users it is intended for. As you work through the different areas of the application, apply a critical eye to the design, layout, workflows, and different functionality of the site. If it helps you, keep notes about what you find, questions you may have, and thoughts about additional areas you’d like to test.

Here are few places to start:

  • Is the site behaving as you expect it to?
  • Does the site and user flow behave the same on different devices and web browsers?
  • What happens when you pass in unexpected values to the API?

To get started you’ll need:

Filing Bugs

On the Mozillians project all defects and feature requests are tracked in Bugzilla as bugs. Yes! We treat everything as a bug. Not all bugs describe problems in software; some bugs describe feature requests, and some ask for help. We simply use Bugzilla as a ticketing system that helps facilitate discussion.

Bugzilla

As you are testing, the types of bugs that you’ll discover will likely fall into three categories:

  1. Functional regressions in the application
  2. Usability problems,
  3. New feature suggestions.

Sometimes the issues are known or even deliberate. If a feature request has been turned down in the past and you feel it should be incorporated into the application, please file a bug (or ask that a closed one be reopened) and advocate for that feature.

A few tips for filing bugs:

  • Provide as much information as possible so the team (devs & other QA’s) understands the problem or suggested enhancement that you are making.
  • Do your best to find and provide clear steps to reproduce to problem, including what browser you used, what URL you were visiting, where you clicked, what you saw, etc. Sometimes a screenshot is a great help.
  • Try searching Bugzilla for the defects
  • Use this form to file new bugs

You can always ask us questions if you aren’t sure if what you found should be entered as a bug.

Please let me know how your testing went. I’d love to hear from you!

mbrandt@mozilla.com



This entry was tagged as mozilla

blog comments powered by Disqus