1/86
Name | Mastery | Learn | Test | Matching | Spaced |
|---|
No study sessions yet.
What is Quality Assurance (QA)?
Process-focused activities that ensure quality is built into the development process.
What is Quality Control (QC)?
Product-focused activities that identify defects in the actual product being developed.
What is a Defect/Bug?
A flaw in software that causes incorrect or unexpected results, or prevents it from functioning as specified.
What is the Defect Life Cycle?
The stages a defect goes through: New → Assigned → Open → Fixed → Retest → Verified/Closed (or Reopened if not fixed).
What is Defect Severity?
The degree of impact a defect has on a system's functionality (Critical, High, Medium, Low).
What is Defect Priority?
The urgency with which a defect should be fixed (Immediate, High, Medium, Low).
What is a Blocker Defect?
A critical defect that prevents testing from continuing or blocks major functionality.
What is a Showstopper Defect?
A critical defect that prevents a software release and must be fixed immediately.
What is a Defect Report?
A document describing a defect with details like steps to reproduce, expected/actual results, severity, and screenshots.
What is Defect Triage?
The process of reviewing, prioritizing, and assigning defects to appropriate team members.
What is Root Cause Analysis?
An investigation to identify the underlying reason a defect occurred to prevent similar issues.
What is Retesting?
Testing a specific defect fix to verify the issue has been resolved.
What is Regression Testing?
Re-testing existing functionality after changes to ensure no new defects were introduced.
What is Manual Testing?
Testing performed by humans executing test cases without automation tools or scripts.
What is Unit Testing?
Testing individual components or functions in isolation, typically performed by developers.
What is Integration Testing?
Testing combined modules or components to verify they work together correctly as a group.
What is System Testing?
Testing the complete integrated system to verify it meets specified requirements.
What is User Acceptance Testing (UAT)?
The final testing phase where end-users validate that the system meets business requirements and is ready for production.
What is Smoke Testing?
Quick, shallow testing of critical functionality to verify basic system stability before deeper testing.
What is Sanity Testing?
Narrow, focused testing of specific functionality or bug fixes to verify rational behavior.
What is Functional Testing?
Testing that verifies software functions according to specified requirements.
What is Non-Functional Testing?
Testing of system attributes like performance, security, usability, and reliability.
What is End-to-End Testing?
Testing complete workflows from start to finish to verify the entire application flow works as expected.
What is Positive Testing?
Testing with valid inputs to verify the system behaves as expected.
What is Negative Testing?
Testing with invalid inputs to verify the system handles errors gracefully.
What is Usability Testing?
Testing that evaluates how user-friendly and intuitive the application is for end-users.
What is Compatibility Testing?
Testing to verify software works correctly across different browsers, devices, OS, and configurations.
What is Performance Testing?
Testing that evaluates system speed, responsiveness, and stability under various workloads.
What is a Test Plan?
A document that defines test scope, objectives, resources, schedule, deliverables, and entry/exit criteria.
What is a Test Strategy?
A high-level document defining the testing approach, levels, types, and resources for a project.
What is a Test Case?
A set of conditions, inputs, and expected results designed to verify a specific requirement or functionality.
What is a Test Suite?
A collection of test cases grouped together for execution, typically organized by functionality or test type.
What is a Requirements Traceability Matrix (RTM)?
A document that maps requirements to test cases, ensuring each requirement has corresponding test coverage.
What is a Test Summary Report?
A document summarizing testing activities, results, defect metrics, and quality assessment.
What is Black Box Testing?
Testing without knowledge of internal code structure, focusing on inputs and outputs.
What is White Box Testing?
Testing with knowledge of internal code structure, logic, and implementation.
What is Gray Box Testing?
Testing with partial knowledge of internal structures, combining black and white box approaches.
What is Boundary Value Analysis?
A test design technique that tests values at boundaries (minimum, maximum, just inside, just outside).
What is Equivalence Partitioning?
A test design technique that divides inputs into groups expected to behave similarly, testing one value from each group.
What is Exploratory Testing?
Informal testing where testers actively explore the application without predefined test cases.
What is Ad-hoc Testing?
Unstructured testing without formal test cases, performed randomly to find defects through intuition and experience.
What is SDLC?
Software Development Life Cycle - a structured process framework with defined phases for planning, creating, testing, and deploying software systems.
What are the main SDLC phases?
Requirements, Design, Development/Implementation, Testing, Deployment, and Maintenance.
What is Waterfall Model?
A sequential SDLC model where each phase must be completed before the next phase begins.
What is Agile Methodology?
An iterative SDLC approach with short development cycles (sprints) and continuous feedback.
What is a Sprint?
A fixed time period (usually 1-4 weeks) in Agile where specific work is completed and ready for review.
What is a User Story?
A short, simple description of a feature from an end-user perspective in Agile (As a [user], I want [goal], so that [benefit]).
What are Acceptance Criteria?
Specific conditions that must be met for a feature or user story to be considered complete and accepted.
What is a Stand-up Meeting?
A short daily Agile meeting where team members share progress, plans, and blockers.
What is a Sprint Retrospective?
An Agile meeting where the team reflects on the sprint to identify improvements for future sprints.
What is a Product Backlog?
A prioritized list of features, enhancements, and fixes to be developed in Agile.
What is a Sprint Backlog?
The subset of product backlog items selected for completion during a specific sprint.
What is a Definition of Done (DoD)?
A checklist of criteria that must be met for a user story or task to be considered complete.
What are Entry Criteria?
Conditions that must be met before testing can begin (e.g., test environment ready, test data available).
What are Exit Criteria?
Conditions that must be met to complete testing (e.g., all critical defects resolved, test coverage achieved).
What is a Test Environment?
The hardware, software, network, and data setup where testing is conducted.
What is a Build?
A compiled version of software code that is ready for testing or deployment.
What is a Release?
A version of software made available to users, containing specific features and fixes.
What is Test Execution?
The process of running test cases and comparing actual results with expected results.
What is Test Coverage?
A measure of how much of the application (requirements, code, features) has been tested.
What is Static Testing?
Testing that examines code, requirements, or design documents without executing the software.
What is Dynamic Testing?
Testing that involves executing the software with test inputs and observing behavior.
What is Risk-Based Testing?
A testing approach that prioritizes testing based on the risk and impact of potential failures.
What is Alpha Testing?
Internal testing performed by the development organization before releasing to external users.
What is Beta Testing?
Testing performed by a limited group of external users in a real environment before full release.
What is a Stub?
A temporary replacement for a called module that returns controlled data during integration testing.
What is a Driver?
A temporary module that calls the module being tested during integration testing