If you are new into QA, SQA, or want to refresh, I will list in here some basic concepts needed, so you can use as reference
QA (Quality Assurance): The process of ensuring that software products and processes meet the specified quality standards. It involves planning, executing, and monitoring activities to prevent defects and improve the overall quality of the software.
Test Case: A set of conditions or steps designed to assess a specific aspect of the software system. Test cases are created to verify that the software functions as intended and to detect any defects or issues.
Test Plan: A document that outlines the objectives, scope, approach, and resources required for testing a software application. It includes details about test strategies, test environments, test schedules, and test deliverables.
Test Suite: A collection of test cases organized into a meaningful group for efficient execution. Test suites help manage and execute tests systematically and enable better test coverage.
Test Execution: The process of running test cases and evaluating the software system's actual behavior against the expected results. Test execution involves recording test outcomes, identifying defects, and reporting the results.
Defect/Bug: An error, flaw, or deviation in the software system that causes it to behave incorrectly, produce incorrect results, or fail to meet specified requirements.
Test Coverage: A measure of the extent to which the software system or specific features have been tested. It helps assess the effectiveness and thoroughness of testing by determining which parts of the system have been exercised by the test cases.
Regression Testing: Testing performed to ensure that modifications or enhancements in the software system do not introduce new defects or inadvertently affect existing functionality. Regression testing helps maintain software quality after changes have been made.
Test Environment: The hardware and software configuration in which testing is performed. It includes the necessary infrastructure, tools, databases, operating systems, and other components required for executing test cases.
Test Report: A document that provides a summary of the test activities, test results, and other relevant information. Test reports help stakeholders understand the status of testing, identify trends, and make informed decisions about the software's quality and readiness.
Priority: Priority refers to the level of importance or urgency assigned to a defect or issue based on its impact on the software system and its stakeholders. It helps determine the order in which defects should be addressed and fixed
Priority Levels:
- High: Defects classified as high priority have a significant impact on the system or business operations, and their resolution is crucial for the software's functionality or success.
- Medium: Medium priority defects represent issues that have a moderate impact on the system or business operations. While they may not be as critical as high priority defects, they still require attention and resolution in a timely manner.
- Low: Low priority defects are typically minor issues or cosmetic in nature, causing minimal impact on the system's functionality or user experience. They may be addressed during later stages or in subsequent releases.
Severity: Severity refers to the degree of impact or seriousness of a defect or issue on the functionality or usability of the software system. It assesses the extent to which a defect affects the core functionality, performance, or user experience.
Common severity levels include:
- Critical: Defects classified as critical severity have the highest level of impact on the system's functionality or business operations. They may lead to system crashes, data corruption, security vulnerabilities, or severe financial loss.
- High: High severity issues represent significant problems that severely impact the system's functionality or user experience. They may cause major malfunctions, data loss, or critical errors that prevent users from accomplishing important tasks.
- Medium: Defects categorized as medium severity have a moderate impact on the system. They may hinder certain functionalities or cause inconveniences to users, but they do not completely prevent the system from functioning. These defects can often be worked around or have alternative solutions.
- Low: Low severity issues have minimal impact on system functionality or user experience. They are typically cosmetic or minor in nature, causing slight inconveniences or inconsistencies that do not significantly affect the core functionality of the software.