Fundamentals of Quality Engineering
This article is designed to support as a tutorial for anyone interested in learning Quality engineering. My goal is to focus on the most important topics that must be understood while keeping the content concise. so go and get a coffee ☕ and read this article!
What is QA?
Monitor the quality of the software product and ensure that the final product meets the user’s requirements known as quality engineering.
Responsibilities of a QA Engineer
QA engineers should monitor all stages of software development to identify bugs/defects and resolve them to meet quality standards. Below are some of the notable responsibilities of QA engineers.
✦ Review Technical documents and provide feedback
✦ Create well-structured Test plans and Test cases
✦ Identity, record, and track bugs
✦ Stay up-to-date with new testing tools and test strategies
Difference between Bug vs Defect
A bug is a coding error and a defect is a requirement error. A defect could be a function that was not implemented but defined in the requirements of the software.
Types of software testing
Different types of testing can be done to ensure the quality of the software product.
Acceptance testing: Verifying whether the whole system works as intended.
Unit Testing: Testing each component of the software application.
Integration Testing: Checking the data flow between components.
Usability Testing: Checking the user-friendliness and efficiency of the application.
Compatibility Testing: Testing Software applications on different software/hardware platforms.
Testing Levels
There are four different levels of software testing.
- Unit Testing: Testing each component of the application.
- Integration Testing: Testing data flow between components.
- System Testing: Testing end-to-end flow of the application.
- Acceptance Testing: Evaluate whether the application works as per its requirements.
Testing Documentation
In software testing, we have various types of testing documents.
- Test plan: prepared by manager/test lead. consists of information such as objectives, scope, methods, schedule, etc.
- Test scenario: prepared to understand user flows of the application.
- Requirement traceability matrix: This document maps test cases with requirements and makes sure every scenario has been tested successfully.
- Bug report: This document includes a summary of all bugs.
Found it Interesting?
Please show your support by 👏.
