QA/Contribute/QA 101/Black Box Testing: Difference between revisions
< QA | Contribute | QA 101
Jump to navigation
Jump to search
| Line 15: | Line 15: | ||
* What to do when the script isn't specific enough | * What to do when the script isn't specific enough | ||
* Related: how to write good scripts, known as 'test cases.' | * Related: how to write good scripts, known as 'test cases.' | ||
** https://developer.mozilla.org/en-US/docs/Mozilla/QA/Test_Case_Writing_Primer | |||
== Exploratory testing == | == Exploratory testing == | ||
Revision as of 16:07, 6 March 2015
What is black box testing?
Testing with no knowledge of what's going on inside the device/system under test.
Basic black-box testing techniques
As much emphasis as possible should be placed on interactive exercises here.
Testing from a script
- Introduce MozTrap?
- What to do when the script isn't specific enough
- Related: how to write good scripts, known as 'test cases.'
Exploratory testing
This is the 'test a Coke machine' exercise. https://oneanddone.mozilla.org/en-US/tasks/12/
Details on how to do exploratory testing: https://quality.mozilla.org/2012/11/exploratory-testing-on-moztrap-job-board-posting-1/
https://oneanddone.mozilla.org/en-US/tasks/10/
What is a regression?
A regression is when a defect re-appears after it went on vacation for a while.
Documenting your process
- Starting from a known state
- Notebooks
- Text files
- Screenshots
- Screencasts!
- Bring this back to test scripts and test cases.