Intro to Manual Testing
- 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
- 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/
Editor's Notes
- #3: A key step in the process is, testing the software for correct behavior prior to release to end users.