Exam program: Software testing and quality assurance (QA)
IAE-EXAM-QA · version 1.0
Sections, format, sample tasks and scoring rubric of the IAE written exam in the field "Software testing and quality assurance (QA)".
01. Who is the exam for?
For QA engineers and software testers, test automation engineers, test managers, performance engineers and quality analysts in product teams. Admission requires a bachelor's degree or higher and at least 3 years of experience in the field (without a degree, at least 5 years). The exam tests calculations and decisions based on testing data: choosing the scope of testing by risk and estimating the effort, designing tests from requirements, the automated test suite in the build pipeline and its stability, load test results and latency requirements, defect handling and the release decision. Knowledge of a particular testing tool or framework is not tested: code and test scripts in answers may be written in any widely used language or in pseudocode, and the latency thresholds and the team's release rules needed for the solution are given in the task. Application programming and software system architecture are covered by the "Software and data" program, cloud infrastructure and software delivery by the "Cloud and DevOps" program, penetration testing and information protection by the "Information security and risk management" program, and statistical process control in manufacturing by the "Quality management and Lean Six Sigma" program.
02. Format
- 5 questions, one per section, 10 minutes each.
- 2 cases of 25 minutes from two different sections: test strategy and planning, test design, test automation and testing in the build pipeline, non-functional testing. The cases require calculations with the candidate's own data: the testing effort by risk level and the share of requirements covered by tests, the number of tests for the fields and rules in the requirements, the payback of automation and the share of tests that fail on the same code, latency percentiles and requests per second from load test results, the outcome of checking a build against the team's release rules.
- 1 question about the project from the candidate's questionnaire, 10 minutes.
- Up to 2 hours in total, in one sitting. Pasting is disabled, and each candidate gets their own case data.
03. Sections and weights
- Test strategy and planning - 20 %: risk-based testing (rating how often a function may fail and the damage from a failure on the scale given in the task, allocating effort by risk level), the test plan and its scope, entry and exit criteria (the conditions for starting and finishing testing), the coverage of requirements by tests and the table linking requirements to tests, estimating the effort for preparing and running tests and for retesting fixes, test levels and their share in the plan, test environments and their shortage.
- Test design - 20 %: equivalence partitions (groups of input values that the program handles the same way) and boundary values, decision tables for rules with several conditions, state transitions and invalid transitions, pairwise testing (a set of tests in which every combination of values of any two parameters occurs at least once), the number of tests for full enumeration and for a reduced set, preparing and anonymizing test data, time-boxed exploratory testing with a charter.
- Test automation and testing in the build pipeline - 20 %: the test pyramid (the ratio of unit, integration and end-to-end tests by number and run time), choosing which tests to automate, the payback of automation as a comparison of the cost of developing and maintaining tests with the hours of manual runs saved, flaky tests (tests that pass and fail on the same code), their share and quarantine until they are fixed, the run time of the test suite and parallel runs, quality gates before deployment (thresholds for failed tests, code coverage, open defects and latency that a build must meet to move further down the pipeline), stubs in place of external services.
- Non-functional testing - 20 %: the load profile based on data on how the system is used, load tests and stress tests, latency percentiles, including p95 (the latency that 95 % of requests do not exceed), throughput (requests per second at an acceptable latency) and the error rate under load, comparing the result with the requirement and with the previous release, reliability checks during a long run under load and when an external service fails, accessibility of the user interface for people with disabilities as a check against the criteria given in the task, compatibility with browsers and devices and choosing the configurations to test by user shares.
- Professional practice - 20 %: a defect report from which the defect can be reproduced, severity (how much the defect hinders the user) and priority (the order of fixing), retesting fixes and regression testing, the escaped defect rate (the number of defects found by users after a release divided by all defects of that release), defect density (the number of defects per thousand lines of code or per another unit of size given in the task), the release decision under the team's rules, the test report to the team and the customer, honest reporting of results, the candidate's own project.
04. Sample tasks
Question. The "Transfer amount" field in a banking app accepts whole numbers. Under the requirements, an amount below 100 or above 50,000 is rejected with an error message, an amount of at least 100 and at most 15,000 goes through at once, and an amount above 15,000 requires confirmation with a code sent by SMS. A transfer can be made from one of three account types. Identify the equivalence partitions for the amount and the boundary values, if at each boundary the last value of one partition and the first value of the next are tested. Calculate the number of tests in two variants: each boundary value is tested with each account type; invalid amounts are tested with one account type only. Name the inputs that need to be tested beyond the amount ranges, and explain why one value from the middle of each partition is not enough.
Case. A team is preparing release 4.2 of an online store, and the customer's product owner decides on Friday whether it goes out. Under the team's release rules, a release goes out if there are no open defects of critical severity, all failed automated tests have been analyzed, the p95 latency of the checkout page is at most 300 ms and the error rate under load is at most 1 %. The regression suite has 1,200 automated tests, and 54 of them failed in the last run. According to the run history for 30 days, 36 tests of the suite (3 %) are flaky, and on average each of them fails in 15 % of runs. Of the 54 failed tests, 21 are flaky, and the other 33 had not failed once in 30 days; 27 of these 33 test the checkout and fail because the wait for a response timed out. A load test at 400 requests per second showed a p95 latency of 340 ms for the checkout page (220 ms in release 4.1) and an error rate of 0.4 %. There is 1 open defect of critical severity: an order paid with a gift card is not created, and gift cards are used to pay for 2 % of the 8,000 orders a day. There are also 3 major and 10 minor open defects. Calculate the share of failed tests in the whole suite and among the tests that are not listed as flaky, and compare the number of failed flaky tests with their usual number in one run. Compare the load test result with the requirement and with release 4.1, and assess whether the increase in latency is linked to the failures of the checkout tests. Decide whether to release 4.2 on Friday, on what conditions, and what to check before the decision. Write a message to the product owner: what is known in figures, your proposal, the risks and the date of the next check.
The figures and circumstances of the cases are different for each candidate.
05. Scoring rubric
Each task is scored on four criteria, and the total is converted to 100 points taking the section weights into account.
- Correctness of the solution - 40 %.
- Reasoning behind decisions - 25 %.
- Risks and constraints - 20 %.
- Clarity of the answer - 15 %: structure and precise wording. Grammar and style do not reduce the score if the meaning is clear.
06. Result
- Pass mark - 70 of 100.
- Result in 5 business days. Those who pass receive an IAE Certified Professional certificate in the field "Software testing and quality assurance (QA)", valid for 3 years; scores by section are in a separate report.
- The certificate confirms that the candidate passed the written exam under this program. It is not a license or an accreditation and does not replace the software testing certificates of other organizations. Employers and authorities make hiring and other decisions about the candidate under their own rules.
- Retake 30 days after the first failed attempt and 60 days after the second, with no more than 3 attempts in 12 months.
- Full terms: the Exam terms page.
- The Credentialing Council reviews the program at least once a year.
07. What is not covered?
- The IAE exam is not an exam of organizations that certify software testers or of other organizations, is not affiliated with them and does not replace their exams. The topics and tasks of the IAE exam do not repeat the syllabi of those exams. The names of certifications and organizations belong to their owners.
- Application programming and software system architecture are covered by the "Software and data" program. In this exam, code is written for tests, and the quality of the application's own code is not assessed.
- Cloud infrastructure and the design of the build and delivery pipeline are covered by the "Cloud and DevOps" program. In this exam, the pipeline is assessed for its test suite and quality gates before deployment; the number of servers and the scaling settings for a load test are given in the task.
- Penetration testing and information protection are covered by the "Information security and risk management" program.
- Statistical process control in manufacturing and Six Sigma projects are covered by the "Quality management and Lean Six Sigma" program. In this exam, software quality is measured with the defect and test metrics given in the task.
- Knowledge of testing standards and of the accessibility requirements of a particular country by heart is not required. Accessibility criteria and latency thresholds are given in the task as the customer's requirements or the team's rules. The exam does not test the legal assessment of whether an interface complies with accessibility laws.
- Particular testing tools and frameworks, their functions and parameters are not tested. Code and test scripts in answers may be written in any widely used language or in pseudocode, and calculations are done by hand or on a calculator.
08. Preparation
- The practice exam runs in the same interface: 2 questions from different sections, a 15-minute case and a project question.
- Review the calculations: the risk level on the scale given in the task and the allocation of testing hours by risk level, the share of requirements covered by tests, the effort for preparing and running tests and for retesting fixes; equivalence partitions and boundary values, the number of rules in a decision table, the number of tests for full enumeration and for pairwise testing; the payback of automation from the hours of a manual run, the number of runs and the cost of maintenance, the share of flaky tests and failed runs, the run time of the test suite with parallel runs; latency percentiles from load test results, throughput and the error rate, the change against the previous release; the escaped defect rate, defect density and the average time to fix.
- Formulas are given in the task when needed, as are latency thresholds and the team's release rules. A calculator is enough for the calculations, and reference materials may be used.
- Answer by the points of the task: the method or formula, the calculation on your own figures, the decision, risks and what needs to be checked. Pasting is disabled, so the answer is typed.
- Prepare the project description for the questionnaire: your role, the product and the team, the testing task, measures before and after (for example, the escaped defect rate or the run time of the test suite), the decisions taken, the result in figures. Do not include confidential employer data (source code, internal defect reports, figures the company does not publish) or users' personal data: the result can be given as a percentage of the starting level. The project question is based on this description.
- Text from AI services and help from other people are not allowed.
Exam
Book the exam
The questionnaire takes 15 minutes. Admission decision in 1 business day.

