Getting Started in QAClint Talbert

Mozilla Corporation

Why?

Why?

• Testing is always needed

Why?

• Testing is always needed

• Gives you a good overview of the codebase

Why?

• Testing is always needed

• Gives you a good overview of the codebase

• Chance to understand use cases

Why?

• Testing is always needed

• Gives you a good overview of the codebase

• Chance to understand use cases

• It’s easy to make a big difference

Laws of QA

These laws of QA were penned by Ronni Eloff: http://www.sqablogs.com/LunaticFringe/

Laws of QA

• Observation

These laws of QA were penned by Ronni Eloff: http://www.sqablogs.com/LunaticFringe/

Laws of QA

• Observation

• Duplication

These laws of QA were penned by Ronni Eloff: http://www.sqablogs.com/LunaticFringe/

Laws of QA

• Observation

• Duplication

• Expectation

These laws of QA were penned by Ronni Eloff: http://www.sqablogs.com/LunaticFringe/

Observation

Duplication

Expectation

Expectation

Expectation

Expectation

Getting Comfortable

Learn to Float

http://www.flickr.com/photos/mikebaird/398077070/

Watch for Pigeonholes

http://www.flickr.com/photos/decor8/2372303921/in/photostream/

Testing

http://www.flickr.com/photos/jurvetson/180431947/

• White box testing• Black box testing

3 R’s of Automation

http://www.flickr.com/photos/ajturner/415882452/

• Reliable• Readable• Reportable

Building Community

http://www.flickr.com/photos/chunyang/800589975/http://www.flickr.com/photos/design-dog/1322023178/

Building Community

http://www.flickr.com/photos/chunyang/800589975/http://www.flickr.com/photos/design-dog/1322023178/

In a Nutshell

• Observation

• Duplication

• Expectation

Laws of QA

• Preparation

• Proposing your path

• Follow-through

• Recruiting

Being Effective

Thank youctalbert@mozilla.com

IRC: ctalbert

Questions?