ASQ Certified Software Quality Engineer Examination Practice Test
The ASQ Certified Software Quality Engineer Examination (CSQE) covers quality practices across software development and maintenance. Relevant work includes defining testable requirements, evaluating software quality attributes, controlling changes to project artifacts, and using defect and process data to guide improvement. The practice bank samples decisions involving acceptance testing, usability, maintainability, effort estimation, and recurring defects.
Exam overview
About the ASQ Certified Software Quality Engineer Examination Exam
Software quality engineering connects lifecycle activities with evidence that a product and its development processes meet defined needs. A software quality engineer may help distinguish acceptance criteria from test procedures, select representative workflows for migration testing, and assess whether users can complete tasks successfully. The work also involves configuration control for approved documents, measures such as defect density, and estimation methods that gather and refine judgments from multiple experts. When defects recur across releases, causal analysis and corrective action address systemic contributors rather than isolated fixes. Quality measures need clear definitions and suitable data before they are used to compare teams or support decisions; quality-attribute evaluation also considers whether components remain safe to modify as requirements change.
Sample Practice Questions
Review a selection from this exam's published US Practice Tests practice bank.
A team is planning acceptance testing for a feature. Which statement best distinguishes acceptance criteria from detailed test steps?
Show answer
Correct answer: AAcceptance criteria state observable conditions that must be met for a feature or deliverable to be accepted. Test steps provide a procedure for checking whether those conditions hold.
A team finds that the same category of defects repeatedly appears in several releases. Which activity is most likely to reduce recurrence rather than merely fix individual instances?
Show answer
Correct answer: ARoot cause analysis looks beyond individual symptoms to identify underlying causes. Corrective process or control changes can prevent similar defects from recurring across future work.
A project team wants to prevent unauthorized changes to its approved process documents. Which control is most appropriate?
Show answer
Correct answer: AControlled access helps prevent unauthorized edits, while revision history supports accountability and recovery of prior versions. Broad distribution or removing identifying information does not control changes.
A team wants to assess whether a software product can be used successfully by people with a range of abilities. Which evaluation approach is most appropriate?
Show answer
Correct answer: AUsability testing with representative users can reveal barriers to understanding and completing tasks, including accessibility obstacles. Code coverage, load testing, and deployment reviews address different quality concerns.
A team wants to estimate the number of defects likely to remain after testing. Which measure most directly expresses defects found per unit of software size?
Show answer
Correct answer: ADefect density normalizes defect counts by a size measure such as lines of code or function points, supporting comparisons across components of different sizes.
A team must decide which older application features to include in a migration test. They want to select a small set that represents the most common user workflows. Which evidence is most useful for choosing those workflows?
Show answer
Correct answer: AUsage data helps identify representative, frequently exercised workflows and supports a test set grounded in actual use. Code size, document age, and team size do not directly indicate how users exercise the application.
A team is choosing a method to estimate software project effort before detailed design is complete. Which approach uses estimates from multiple knowledgeable participants and repeated rounds of feedback to build consensus?
Show answer
Correct answer: AThe Delphi technique gathers estimates independently from experts over multiple rounds, sharing summarized feedback between rounds to move toward a reasoned consensus while limiting the influence of any one participant.
How to use this practice test
Access is free. The published bank contains 50 questions; each practice session presents up to 20 random questions and displays results afterward. Use a session to test your reasoning on software-quality scenarios, then review missed items by decision type—for example, test planning, change control, measurement, or defect prevention.
Preparation tips
- For acceptance-testing scenarios, write the user-visible condition that defines success separately from the sequence of test actions used to verify it.
- Compare corrective action with root-cause analysis: identify evidence of a recurring defect pattern, investigate process contributors, and select an action that can prevent recurrence.
- Practice choosing software measures by matching each measure to its purpose; distinguish defect density from defect counts and check whether definitions and data support comparisons.
- For usability questions, separate expert inspection from studies that observe representative users attempting critical tasks, and identify what evidence each approach can provide.
- Review estimation and migration-testing scenarios by selecting methods that fit the evidence available, such as repeated expert feedback for consensus estimates or usage data for representative workflows.