Manual testing involves manually testing software by playing the role of an end user and using test cases to ensure correct behavior. It is important early in development when automation is not possible and for testing visual elements. A test plan is a document that outlines test objectives, workflows and processes while a test case specifies conditions to determine if a feature works as intended. Both exploratory and black/white box testing have pros and cons for finding bugs. Bugzilla is a bug tracking system that helps developers manage issues.

1. Manual Testing
Ayah Soufan
Quality Assurance Engineer

2. What ?
❖ Manual Testing is the process of manually testing
software for defects.
❖ It requires a tester to play the role of an end user.
❖ Use most of the features of the application to ensure
correct behavior.

3. How ?
❖ Follow a written test plan
that leads testers through
a set of important test
cases.

4. Why?
● The one and only option during the initial
stage of the application.
● When the application is in the regression phase
and it’s stable,then the user can automate the
basic functions.
● Automated tools can’t test for visual
considerations like gestures, image color or
font size

5. When?
❖ When flexibility is needed
❖ When short-term projects are active
❖ When usability is being tested

6. What is Test Plan? ❖A document detailing the
objectives, target market,
internal beta team, and
processes
❖For a specific test for a
software or hardware product.
❖The plan typically contains a
detailed understanding of the
eventual workflow

7. Test Plan Example
https://wiki.mozilla.org/Marketplace/Late_Customization/Testplan

8. What is Test Case?
❖ A set of conditions
❖ To determine whether a software system or one
of its features is working as it was originally
established to do.

9. Exercises 1

10. Exercises 2

11. Exploratory testing
❖ Seeks to find out how the software actually works
❖ The quality of the testing is dependent on the
tester's skill of inventing test cases and
finding defects

12. EXPLORATORY TESTING
Pros:
❖ No need for long preparation
❖ More intellectual approach
❖ Quick detection of bugs
❖ Does not require documentation

13. EXPLORATORY TESTING
Cons:
❖ Requires a certain mindset
❖ Its unstructured nature makes it easy to lose focus
❖ Due to performing ‘on-the-fly’ it can sometimes be
difficult to define exactly which tests were run
and hard to repeat certain cases if necessary

14. White Box Testing
❖ Testing the application at the level of the
source code.
❖ Internal perspective of the system.

15. Black Box Testing
❖ Specific knowledge of the application's code is
not required
❖ The tester is aware of what the software is
supposed to do
❖ The tester is not aware of how it does it

16. Stages
Unit testing
Integration testing
System Testing
User Acceptance testing
Release or Deployment Testing

17. What is Bugzilla?
❖ Is a bug or issue-tracking
system.
❖ Bug-tracking systems allow
individual or group
developers to effectively
keep track of outstanding
problems with their product.

18. Get Involved in Mozilla QA
https://quality.mozilla.org/get-involved/