Sqa

Question 1

Acceptance Testing

Answer 1

Validates the software against user requirements and ensures it is ready for delivery.

Example sentence: The acceptance testing phase confirmed that the software met all specified user requirements.

Question 2

Agile Development

Answer 2

An iterative and incremental approach to software development with a focus on collaboration, customer feedback, and small, rapid releases.

Additional information: Agile development emphasizes adaptability and flexibility in response to changing requirements.

Question 3

Analysis

Answer 3

The process of examining requirements, design, and code to understand and improve software quality.

Example sentence: Thorough analysis of the software architecture revealed opportunities for optimization.

Question 4

Audit

Answer 4

A formal examination of software processes, documentation, and products to ensure compliance with standards.

Example sentence: The audit identified areas where the software development process did not align with industry best practices.

Question 5

Automated Testing

Answer 5

Using software tools to execute tests automatically, reducing manual effort and improving consistency.

Additional information: Automated testing is essential for regression testing and ensuring rapid feedback on code changes.

Question 6

Backtracking

Answer 6

A debugging technique where you go back through the code to find the source of a defect.

Example sentence: Backtracking helped pinpoint the error in the algorithm implementation.

Question 7

Bench Testing

Answer 7

Testing software in a controlled environment to isolate and identify defects.

Example sentence: Bench testing revealed memory leaks in the software under stress conditions.

Question 8

Black-box Testing

Answer 8

Testing based on input and output without knowledge of the internal code structure.

Example sentence: Black-box testing focuses on the software’s functionality rather than its implementation details.

Question 9

Bottom-Up Testing

Answer 9

Testing begins with lower-level components and progresses to higher-level components.

Example sentence: Bottom-up testing ensures that individual modules work correctly before integrating them into the larger system.

Question 10

Boundary Value Analysis

Answer 10

Testing the boundaries between partitions to identify defects at the edges of input ranges.

Example sentence: Boundary value analysis helped uncover edge cases that caused unexpected behavior in the software.

Question 11

Buddy Check

Answer 11

Informal code review where two colleagues review each other’s code.

Example sentence: The buddy check process improved code quality and knowledge sharing among team members.

Question 12

Bug Record

Answer 12

A detailed log of defects found during testing, including steps to reproduce, severity, and status.

Example sentence: The bug record provided valuable insights into recurring issues and their impact on software quality.

Question 13

Cause-Effect Graphing

Answer 13

A technique to identify and test the relationships between causes (inputs) and effects (outputs).

Example sentence: Cause-effect graphing helped prioritize testing efforts by focusing on critical paths in the software.

Question 14

Circulation Review

Answer 14

A method where documents are circulated among reviewers for feedback and approval.

Example sentence: The circulation review process ensured that multiple stakeholders provided input on the software requirements.

Question 15

CMMI (Capability Maturity Model Integration)

Answer 15

A framework for improving and assessing the maturity of software development processes.

Example sentence: Adhering to CMMI practices can lead to more predictable and efficient software development outcomes.

Question 16

Code Inspection

Answer 16

A formal review of source code to identify defects and ensure coding standards.

Example sentence: Code inspection revealed inconsistencies in coding practices and potential security vulnerabilities.

Question 17

Comparison

Answer 17

Evaluating software against predefined criteria or comparing two versions to identify differences.

Example sentence: The comparison of the new software release with the previous version highlighted performance improvements.

Question 18

Component Testing

Answer 18

Testing individual components of software in isolation.

Example sentence: Component testing is crucial for verifying the functionality and behavior of each software module.

Question 19

Condition Coverage

Answer 19

Ensuring each boolean condition in the code is tested for true and false outcomes.

Example sentence: Condition coverage testing identified logical errors that occurred when specific conditions were not properly evaluated.

Question 20

Debugging

Answer 20

The process of finding and fixing defects in the software.

Example sentence: Debugging is an iterative and problem-solving process that improves software reliability.

Question 21

Debugging by Backtracking

Answer 21

Tracing back through the code to find the source of a defect.

Example sentence: Debugging by backtracking helped identify the incorrect variable assignment that caused the software crash.

Question 22

Debugging by Brute Force

Answer 22

Using extensive and often repetitive testing to locate a defect.

Example sentence: Debugging by brute force involved exhaustive testing to identify the root cause of the memory leak.

Question 23

Debugging by Deduction

Answer 23

Using logical reasoning to identify the cause of a defect.

Example sentence: Debugging by deduction narrowed down the possible sources of the software error based on the observed behavior.

Question 24

Debugging by Induction

Answer 24

Making observations and forming hypotheses to find the source of a defect.

Example sentence: Debugging by induction involved analyzing patterns in the software behavior to infer the likely causes of the defect.

Question 25

Debugging by Testing

Answer 25

Running tests to identify and isolate defects in the software. ## Footnote Example sentence: Debugging by testing involved creating test cases to reproduce the reported software issues.

Question 26

Decision/Condition Coverage

Answer 26

Ensures all decision points and conditions are tested. ## Footnote Example sentence: Decision/condition coverage testing confirmed that all possible logic branches in the software were exercised during testing.

Question 27

Demonstration

Answer 27

Showing the software’s functionality to stakeholders to confirm it meets requirements. ## Footnote Example sentence: The demonstration of the software features to stakeholders validated that the product aligned with user expectations.

Question 28

Equivalence Partitioning

Answer 28

Dividing input data into partitions that are expected to produce similar behavior. ## Footnote Example sentence: Equivalence partitioning reduced the number of test cases needed to cover different data ranges in the software.

Question 29

Error Analysis

Answer 29

Examining defects to understand their root causes and prevent future occurrences. ## Footnote Example sentence: Error analysis identified common patterns in software defects that led to the implementation of preventive measures.

Question 30

Error Checklist

Answer 30

A list of common errors to check for during reviews and testing. ## Footnote Example sentence: The error checklist served as a reference guide for identifying known software issues during quality assurance activities.

Question 31

Error Guessing

Answer 31

Using experience and intuition to identify likely areas of the software where defects may exist. ## Footnote Example sentence: Error guessing helped prioritize testing efforts by focusing on high-risk areas of the software.

Question 32

Extreme Program Testing

Answer 32

Testing software with extreme values or conditions to ensure robustness. ## Footnote Example sentence: Extreme program testing simulated edge conditions to assess the software's resilience under extreme scenarios.

Question 33

Factory Testing

Answer 33

Testing performed in a controlled environment before deployment to the production environment. ## Footnote Example sentence: Factory testing ensured that the software components were functional and stable before release.

Question 34

First Article Qualification

Answer 34

Verifying that the first produced unit meets all specifications and requirements. ## Footnote Example sentence: First article qualification confirmed that the initial production unit met the design and quality standards.

Question 35

Function Testing

Answer 35

Validating individual functions of the software to ensure they work as intended. ## Footnote Example sentence: Function testing verified that each software function performed the expected operations accurately.

Question 36

Functional Testing

Answer 36

Testing based on the software’s functional requirements and specifications. ## Footnote Example sentence: Functional testing validated that the software features functioned according to the specified requirements.

Question 37

Grey-box Testing

Answer 37

Combines black-box and white-box testing techniques, using limited knowledge of the internal code. ## Footnote Example sentence: Grey-box testing provided insights into the software functionality while also verifying internal code paths.

Question 38

Hallway Intercept

Answer 38

Informal usability testing where random people in a public space are asked to use the software and provide feedback. ## Footnote Example sentence: Hallway intercept testing gathered user feedback from diverse individuals to improve software usability.

Question 39

Higher-Order Testing

Answer 39

Advanced testing techniques that go beyond basic testing methods. ## Footnote Example sentence: Higher-order testing involved complex scenarios and performance testing to evaluate the software under realistic conditions.

Question 40

Incremental Testing

Answer 40

Testing in stages, where parts of the system are integrated and tested incrementally. ## Footnote Example sentence: Incremental testing allowed for early detection of integration issues and ensured a smoother software development process.

Question 41

Inspection

Answer 41

A formal review process where a work product is examined in detail to identify defects. ## Footnote Example sentence: Inspection uncovered design flaws in the software architecture that required immediate corrective action.

Question 42

Inspection Agenda

Answer 42

A planned schedule for conducting inspections, including objectives and steps to be followed. ## Footnote Example sentence: The inspection agenda outlined the review process and criteria for evaluating the software design.

Question 43

Inspection Team

Answer 43

A group of people conducting a formal inspection of a software product. ## Footnote Example sentence: The inspection team consisted of domain experts and developers to ensure comprehensive review coverage.

Question 44

Installation Testing

Answer 44

Ensures software installs correctly and functions as expected in its intended environment. ## Footnote Example sentence: Installation testing verified that the software installation process was seamless across different operating systems.

Question 45

Integration Testing

Answer 45

Tests the interaction between integrated units/modules to detect interface defects. ## Footnote Example sentence: Integration testing revealed communication issues between software components that required resolution.

Question 46

Load Testing

Answer 46

Evaluates software performance under expected user loads to identify bottlenecks and limits. ## Footnote Example sentence: Load testing helped optimize server capacity to handle peak user traffic without performance degradation.

Question 47

Logic (Statement) Coverage Testing

Answer 47

Measures the extent to which the source code statements have been executed. ## Footnote Example sentence: Logic coverage testing assessed the code paths that were executed during testing to ensure comprehensive code coverage.

Question 48

Milestone Reviews

Answer 48

Evaluates the project's progress at specific points to ensure it meets the planned objectives. ## Footnote Example sentence: Milestone reviews identified project delays and risks early on, enabling proactive risk mitigation strategies.

Question 49

Mitigation

Answer 49

Implementing strategies to reduce or eliminate risks in software development. ## Footnote Example sentence: Mitigation measures were implemented to address security vulnerabilities identified during threat analysis.

Question 50

Module (Unit) Testing

Answer 50

Tests individual components or modules of a software separately. ## Footnote Example sentence: Module testing verified the functionality of each software unit in isolation before integration with other modules.

Question 51

Multiple Condition Coverage

Answer 51

Ensures all possible combinations of conditions in a decision are tested. ## Footnote Example sentence: Multiple condition coverage testing examined all logical pathways through the software to detect potential defects.

Question 52

Non-incremental (Big-Bang) Testing

Answer 52

Combines all modules together at once and tests the system as a whole. ## Footnote Example sentence: Non-incremental testing detected integration issues that resulted from combining all software modules simultaneously.

Question 53

Milestone Reviews

Answer 53

Evaluates the project's progress at specific points to ensure it meets the planned objectives. ## Footnote Example: Milestone reviews are conducted at the end of each development phase.

Question 54

Mitigation

Answer 54

Implementing strategies to reduce or eliminate risks in software development. ## Footnote Mitigation techniques include risk avoidance and risk transfer.

Question 55

Module (Unit) Testing

Answer 55

Tests individual components or modules of a software separately. ## Footnote Module testing is often automated to ensure thorough coverage.

Question 56

Multiple Condition Coverage

Answer 56

Ensures all possible combinations of conditions in a decision are tested. ## Footnote This testing technique helps uncover complex logic errors.

Question 57

Non-incremental (Big-Bang) Testing

Answer 57

Combines all modules together at once and tests the system as a whole. ## Footnote Big-Bang testing can be risky due to limited visibility into individual module performance.

Question 58

Observation

Answer 58

Monitoring and recording behavior of a software system during testing. ## Footnote Observation is crucial for identifying unexpected system behaviors.

Question 59

Operational Scenario Testing

Answer 59

Validates the software against real-world scenarios and usage conditions. ## Footnote Operational scenario testing helps ensure software reliability in practical situations.

Question 60

Packaging and Delivery

Answer 60

The process of preparing software for distribution and delivering it to the end users. ## Footnote Packaging and delivery involve creating installation packages and deployment procedures.

Question 61

Path Coverage Testing

Answer 61

Ensures all possible paths through the code are executed. ## Footnote Path coverage testing helps identify untested code paths.

Question 62

Peer Rating

Answer 62

A method where peers evaluate the performance or quality of a product or process. ## Footnote Peer rating can provide valuable insights from a different perspective.

Question 63

Peer Review

Answer 63

Examination of software work products by colleagues to identify defects and improvements. ## Footnote Peer reviews are commonly conducted before code merges.

Question 64

Performance Testing

Answer 64

Measures software's responsiveness, stability, and scalability under load. ## Footnote Performance testing helps ensure software meets performance requirements.

Question 65

Product Integration

Answer 65

Combining components or systems into a larger product and ensuring they work together. ## Footnote Product integration testing verifies interactions between integrated components.

Question 66

Project Manager Review

Answer 66

An assessment by the project manager to ensure project alignment with goals and requirements. ## Footnote Project manager reviews help maintain project focus and direction.

Question 67

Qualification Testing

Answer 67

Verifies if a system meets specified requirements and performs correctly in its intended environment. ## Footnote Qualification testing is often part of the final acceptance process.

Question 68

Regression Testing

Answer 68

Re-running previously completed tests to ensure changes haven't introduced new defects. ## Footnote Regression testing is important after software updates or modifications.

Question 69

Review

Answer 69

A process of examining software work products to identify defects and improvements. ## Footnote Review processes can include code reviews, design reviews, and document reviews.

Question 70

Scrum

Answer 70

An agile framework for managing complex software development involving iterative progress through sprints. ## Footnote Scrum emphasizes collaboration, adaptation, and continuous improvement.

Question 71

Simulation

Answer 71

Using models to replicate the behavior of a system for testing purposes. ## Footnote Simulation can help predict system behavior under different conditions.

Question 72

Statement Coverage

Answer 72

Ensures every statement in the code is executed at least once during testing. ## Footnote Statement coverage is a basic metric for code coverage analysis.

Question 73

Stress Testing

Answer 73

Evaluates software stability and reliability under extreme conditions. ## Footnote Stress testing helps uncover system weaknesses under high load.

Question 74

Structured Walkthrough

Answer 74

A detailed review of a software product guided by a set procedure. ## Footnote Structured walkthroughs help identify issues early in the development process.

Question 75

System Testing

Answer 75

Validates the complete and integrated software system to ensure it meets requirements. ## Footnote System testing verifies end-to-end functionality and performance.

Question 76

Technical Review

Answer 76

Analyzing a software product to ensure it meets technical standards and requirements. ## Footnote Technical reviews focus on software architecture, design, and implementation.

Question 77

Testing

Answer 77

The process of executing a program with the intent of finding errors. ## Footnote Testing is an essential part of the software development life cycle.

Question 78

Top-Down Testing

Answer 78

Starts with the highest-level modules and progressively integrates and tests lower-level modules. ## Footnote Top-down testing can help identify integration issues early in development.

Question 79

Unit Testing

Answer 79

Verifying the functionality of individual units/components of software. ## Footnote Unit testing is often automated and performed by developers.

Question 80

Usability Questionnaire

Answer 80

A survey used to collect user feedback on the software's usability. ## Footnote Usability questionnaires help gather user perspectives on software usability.

Question 81

Usability Testing

Answer 81

Evaluates how easy and user-friendly the software is for end-users. ## Footnote Usability testing often involves real users performing tasks with the software.

Question 82

Validation

Answer 82

Ensures the software meets user needs and requirements. ## Footnote Validation confirms that the software satisfies its intended purpose.

Question 83

Verification

Answer 83

Ensures the software correctly implements specified functions. ## Footnote Verification focuses on verifying that the software meets specified requirements.

Question 84

Walkthrough

Answer 84

A step-by-step presentation of a process or system by its creator to gather feedback. ## Footnote Walkthroughs can help identify potential issues early in the development process.

Question 85

White-box Testing

Answer 85

Testing based on an analysis of the internal workings and structure of the software. ## Footnote White-box testing is also known as clear box or glass box testing.