Enhance Your Learning with Software Quality Assurance Flash Cards for quick learning
The process of ensuring that software meets specified quality standards and requirements.
Different approaches and techniques used to test software for defects and ensure its quality.
Established guidelines and procedures that define the quality requirements and processes for software development and testing.
The process of creating a test plan, defining test cases, and executing them to verify the functionality and quality of software.
The process of identifying, tracking, and resolving defects or issues found during software testing.
The use of software tools and scripts to automate the execution of test cases, increasing efficiency and accuracy.
Testing the performance and responsiveness of software under different load and stress conditions to ensure its stability and scalability.
Testing the security features and vulnerabilities of software to protect it from unauthorized access and data breaches.
Testing the user-friendliness and ease of use of software to ensure a positive user experience.
Repeating previously executed test cases to ensure that changes or updates to software have not introduced new defects or issues.
Testing practices and techniques used in Agile software development methodologies, focusing on frequent feedback and collaboration.
The practice of regularly integrating and delivering software changes to ensure its stability and quality throughout the development process.
Collecting and analyzing data to measure the effectiveness and quality of software testing, and generating reports for stakeholders.
Proven approaches and strategies that help improve the quality and efficiency of software development and testing processes.
Software applications and frameworks used to support and automate various aspects of software quality assurance and testing.
A set of conditions or steps to be followed to verify the functionality and quality of software.
The hardware, software, and network setup used to execute test cases and simulate real-world conditions.
The input values and conditions used in test cases to validate the behavior and functionality of software.
Testing the software's behavior at the boundaries of input values or conditions to ensure it handles them correctly.
Testing the functionality and behavior of software without knowledge of its internal structure or implementation.
Testing the internal structure and implementation of software to ensure its correctness and adherence to specifications.
Testing the software with partial knowledge of its internal structure or implementation, combining elements of black box and white box testing.
A quick and basic test to ensure that the critical functionalities of software are working before conducting more comprehensive testing.
A subset of regression testing to quickly verify that the recent changes or fixes in software have not introduced major issues.
Testing the interaction and compatibility of different software components or modules to ensure they work together correctly.
Testing the entire system or software application as a whole to verify its functionality, performance, and quality.
Testing the software to determine if it meets the specified requirements and is ready for deployment or release.
Testing the software in a controlled environment by a group of users before its release to gather feedback and identify issues.
Testing the software in a real-world environment by a group of external users to gather feedback and identify issues before its final release.
Testing the software's performance and behavior under expected or anticipated load conditions to ensure its stability and responsiveness.
Testing the software's performance and behavior under extreme load conditions to determine its breaking point or limitations.
Testing the software's compatibility with different hardware, software, and network configurations to ensure its proper functioning.
Testing the software's accessibility features and compliance with accessibility standards to ensure it can be used by people with disabilities.
The impact or seriousness of a defect on the functionality or quality of software, ranging from low to critical.
The importance or urgency of fixing a defect based on its impact and the project's priorities, ranging from low to high.
A software development approach where tests are written before the actual code, driving the design and implementation process.
The practice of regularly integrating and testing code changes to ensure their compatibility and stability in a shared repository.
The practice of automating the software release process to ensure that changes can be deployed to production quickly and reliably.
A metric that measures the percentage of code lines or statements covered by tests, indicating the effectiveness of test coverage.
Testing the software without executing it, focusing on reviewing code, requirements, and design to identify defects and improve quality.
Testing the software by executing it, focusing on verifying its behavior, functionality, and performance.
A process where colleagues or team members review and provide feedback on each other's work, such as code, documents, or test cases.
A problem-solving technique used to identify the underlying cause or source of defects or issues in software.
The process of ensuring that software meets specified quality standards and requirements.
The process of inspecting and testing software to identify defects or issues and ensure its quality.
An error, flaw, or defect in software that causes it to behave unexpectedly or not as intended.
A small software update or fix that addresses specific issues or vulnerabilities in software.