Functional Testing · Interview questions · Updated November 2026
Functional testing interview questions check whether you can test what a system should do: design test cases from requirements, choose the right boundary values, write clear defect reports and tell confirmation testing from regression testing. This guide explains each topic in the terms of the ISTQB Certified Tester Foundation Level (CTFL) v4.0 syllabus and adds the Selenium, Playwright and Postman questions asked in mixed manual and automation roles. It also sets out what junior, mid-level and senior candidates are expected to know, with a 2–3 week preparation plan. Then try 10 free functional testing practice questions with answers.
At a glance
| Free in this post | 10 questions with answers |
| Role levels | Junior, mid-level, senior |
| Core topics | Test design, defects, regression, automation |
| Terminology | ISTQB CTFL v4.0 |
| Exametics set | 6 practice tests, 635 questions |
| Exam Mode | Timed test included |
- For manual and automation testers, QA engineers and job seekers preparing for functional testing interviews.
- Every technical point is checked against the official ISTQB syllabus and the Selenium, Playwright, Postman and HTTP (RFC 9110) documentation.
Source: ISTQB Certified Tester Foundation Level syllabus (v4.0.1). Checked on 9 November 2026.
What interviewers test in functional testing interviews
Functional testing interviews test four things: whether you know what functional testing is, whether you can apply test design techniques to a real requirement, whether you handle defects and changes in a disciplined way, and, for many roles, whether you can automate UI and API checks.
The ISTQB CTFL syllabus defines functional testing as testing that “evaluates the functions that a component or system should perform”: the “what” of the system. Non-functional testing checks “how well the system behaves”.
Fundamentals: definitions, levels and principles
Expect opening questions on functional vs non-functional and black-box vs white-box testing:
| Term | What it means in the ISTQB CTFL syllabus |
|---|---|
| Functional testing | What the system should do: functional completeness, correctness and appropriateness |
| Non-functional testing | How well the system behaves: performance efficiency, compatibility, usability, reliability, security, maintainability, portability and safety (ISO/IEC 25010) |
| Black-box testing | Specification-based: checks behaviour against the specifications |
| White-box testing | Structure-based: derives tests from the code or internal structure |
Functional testing is often specification-based (black-box), but the syllabus says every test type can be applied at every test level.
The five test levels in the syllabus are component (unit) testing, component integration testing, system testing, system integration testing and acceptance testing. System testing often includes functional testing of end-to-end tasks, while acceptance testing focuses on validation and readiness for deployment.
Know the error–defect–failure chain too. In the syllabus wording, people make errors (mistakes), which produce defects (faults, bugs), which may in turn result in failures.
The seven testing principles come up often in junior interviews. One that candidates often leave out is “Tests wear out”: if the same tests are repeated many times, they become less effective at finding new defects, so tests and test data need to be changed and new tests written.
Test design techniques: the core of the interview
Black-box test techniques get the most interview time because they show whether you can design tests, not just run them. The syllabus covers four:
- Equivalence partitioning (EP): split data into partitions that should be processed the same way, then test at least one value from each partition, including invalid partitions.
- Boundary value analysis (BVA): test the edges of ordered partitions. In 2-value BVA you test each boundary and its closest neighbour in the next partition; in 3-value BVA you test each boundary and both its neighbours.
- Decision table testing: record combinations of conditions and the resulting actions, such as business rules. Each column is one rule, and full coverage means exercising every feasible column.
- State transition testing: model states and the events that move the system between them. Coverage can be all states, valid transitions (0-switch) or all transitions.
Expect an example such as “a field accepts 1 to 10: which values would you test?” The syllabus notes that 3-value BVA is more rigorous: if “x ≤ 10” is wrongly coded as “x = 10”, the 2-value tests 10 and 11 pass, but 9 from 3-value BVA is likely to catch it.
Experience-based techniques also appear: error guessing, exploratory testing and checklist-based testing. In exploratory testing, tests are designed, executed and evaluated at the same time while you learn about the system, often in time-boxed sessions guided by a test charter.
Change, defects and collaboration
Confirmation testing confirms that an original defect has been fixed. Regression testing confirms that a change, including a fix, has not caused adverse effects elsewhere.
The syllabus lists what a defect report contains, including steps to reproduce, expected and actual results, severity (the degree of impact) and priority to fix. Be ready to explain why severity and priority can differ.
For Agile teams, expect questions on acceptance criteria and test-first approaches. The syllabus describes two formats for acceptance criteria: scenario-oriented, such as the Given/When/Then format used in behaviour-driven development (BDD), and rule-oriented, such as a checklist. In acceptance test-driven development (ATDD), test cases are written before the user story is implemented.
Automation and API checks for functional testers
Many functional testing roles include some automation, so expect questions on how UI tools wait for elements and how API tests check results.
For Selenium, know the waiting strategies in the Selenium documentation. An implicit wait is a global setting for every element lookup in the session, with a default of 0. An explicit wait polls for a specific condition. The documentation warns not to mix implicit and explicit waits, because it can cause unpredictable wait times.
For Playwright, know that it auto-waits. The Playwright actionability documentation says it runs actionability checks first; before a click, the element must be visible, stable, enabled and able to receive events.
For API testing, know how to write a basic assertion. The Postman test scripts documentation shows tests written in the Scripts > Post-response tab with pm.test and an assertion such as pm.response.to.have.status(200). You should also know common HTTP rules from RFC 9110 (HTTP Semantics), such as which methods are idempotent and what 201 Created means.
The test pyramid ties this together. The syllabus explains that tests in the bottom layer are small, isolated and fast, so you usually need many of them, while higher layers have lower isolation and longer execution times.
Exametics practice tests
Functional Testing interview practice tests
- 6 practice tests of about 106 questions each (635 in total), including a timed Exam Mode test
- Every question explains why the right answer is right and why the others are wrong, with a hint
- Each question is tagged with one of eleven topic areas; terminology follows ISTQB CTFL v4.0
- Lifetime access
30-day refund. Instant access after payment.
Functional testing interview expectations by level
Every level is asked about the same core topics; what changes is the depth. Juniors define and apply, mid-level candidates justify, and seniors plan and lead.
| Level | Expected to | Typical task |
|---|---|---|
| Junior | Define terms and apply them to small examples | Write test cases for a sign-up form; write a defect report |
| Mid-level | Choose a technique and justify it | Build a decision table; choose regression tests after a change |
| Senior / lead | Plan the approach and agree it with stakeholders | Split checks across unit, API and UI layers; set exit criteria |
Junior and graduate testers
Given a login page or registration form, show that you think in partitions and boundaries, cover invalid as well as valid input, and write an expected result for every test. A defect report needs a clear title, numbered steps, expected and actual results, and the environment.
Mid-level testers
You may get a business rule to turn into a decision table, or an order lifecycle and a question about which transitions you would test. When choosing regression tests, mention risk, the areas the change touches and the existing automated suite.
Senior and lead testers
Expect questions on testing a new feature under a tight deadline. Use the absence-of-defects fallacy: testing every specified requirement and fixing every defect can still produce a system that does not meet users’ needs, so validation with real users matters as well as verification.
Next on your testing interview path
- Manual Testing Interview Questions and Answers practice tests: 591 questions on test cases, bug reports and the testing life cycle for manual roles.
- QA Automation Interview Questions practice tests: the next step if the job advert asks for automation or SDET skills.
- ISTQB Foundation Level (CTFL v4.0) practice tests: if you also want the certification whose terminology interviewers use.
If you are deciding between the certificate and interview preparation, our guides on ISTQB CTFL practice tests for people new to testing and choosing an ISTQB certification path explain where the Foundation Level fits.
How to prepare for a functional testing interview in 2–3 weeks
Two to three weeks of focused practice is enough for most candidates who already work in IT or have studied testing. Spend most of it on test design, then finish with timed practice tests.
- Days 1–3: Core vocabulary Read the fundamentals and test-types sections of the ISTQB CTFL syllabus. Write one-line definitions of functional vs non-functional testing, the five test levels, error vs defect vs failure, and the seven principles.
- Days 4–8: Test design by hand Pick three real forms or workflows (sign-up, checkout, password reset). For each, write EP and BVA test cases, one decision table and one state transition model, and state the coverage you reach.
- Days 9–11: Defects and change Write three defect reports from bugs on a public demo site. Explain severity vs priority, and confirmation vs regression testing, out loud in under a minute each.
- Days 12–15: Tools and APIs Automate two checks in Selenium or Playwright with proper waits, and write a Postman test for a status code and a response field.
- Days 16–21: Timed practice and review Take the Functional Testing interview practice tests one at a time, read every explanation, list your weak topic areas, then finish with the timed Exam Mode test.
Tip
Answer test design questions out loud as “partitions, then boundaries, then expected results”. Saying your method first stops you missing invalid partitions.
Planning more than one exam?
Job interviews rarely test one topic in isolation. If manual testing, QA automation or ISTQB Foundation Level questions are on your list too, the All-Access Pass covers every practice test on Exametics, including all 58 interview question sets and new exams as they are added, with lifetime access. It costs less than buying about six single practice tests.
Free functional testing interview questions (10 with answers)
Try these 10 free practice questions to check your readiness; the full Exametics Functional Testing practice tests have 635 more. Exametics wrote these sample questions for this post in ISTQB CTFL v4.0 terms. Answer all 10 before you open “Show answer”; each answer explains every option.
Practice question 1 · Testing fundamentals
Which of these checks is a functional test of an online shop?
- A. The search results page loads within two seconds under normal load
- B. A screen reader user can complete the checkout
- C. Applying a valid 10% discount code reduces the order total by 10%
- D. The app installs and runs on the latest version of the operating system
Show answer
Answer: C. Functional testing checks what the system should do, and applying a discount correctly is a function of the shop. A checks how fast the system responds, which is performance efficiency. B checks usability (accessibility), and D checks portability; all three are non-functional quality characteristics in ISO/IEC 25010.
Practice question 2 · Black-box techniques
A sign-up form accepts whole-number ages from 18 to 65 inclusive. Considering only three partitions (below 18, 18 to 65, above 65), what is the minimum number of test cases needed for 100% equivalence partitioning coverage?
- A. 2
- B. 3
- C. 4
- D. 6
Show answer
Answer: B. EP coverage needs each partition, including invalid ones, to be exercised at least once, and one age value can only fall into one partition, so three partitions need three test cases. Two (A) would leave one partition untested. Four (C) adds a redundant test. Six (D) adds values from partitions that are already covered, which adds no EP coverage.
Practice question 3 · Black-box techniques
A quantity field accepts whole numbers from 1 to 10 inclusive. Which set of values gives 100% coverage using 2-value boundary value analysis?
- A. 1, 10
- B. 0, 1, 2, 9, 10, 11
- C. 0, 5, 11
- D. 0, 1, 10, 11
Show answer
Answer: D. The partitions are 0 and below, 1 to 10, and 11 and above, so the boundary values are 0, 1, 10 and 11. In 2-value BVA each boundary value is covered with its closest neighbour in the adjacent partition, which gives 0, 1, 10 and 11. A misses the invalid boundary values 0 and 11. B adds 2 and 9, which 2-value BVA does not need. C has one value per partition, which is equivalence partitioning rather than BVA.
Practice question 4 · Black-box techniques
For the same 1 to 10 quantity field, which set of values gives 100% coverage using 3-value boundary value analysis?
- A. -1, 0, 1, 2, 9, 10, 11, 12
- B. 0, 1, 2, 9, 10, 11
- C. 0, 1, 10, 11
- D. 1, 2, 9, 10
Show answer
Answer: A. In the CTFL syllabus the minimum and maximum of every partition are boundary values, so the boundary values are 0, 1, 10 and 11. 3-value BVA covers each boundary value and both its neighbours, which gives eight distinct values from -1 to 2 and from 9 to 12. B covers only the neighbours of 1 and 10 and misses -1 and 12. C is the 2-value set. D leaves out every invalid value.
Practice question 5 · Black-box techniques
A loan rule depends on three yes/no conditions: the applicant is employed, has a good credit score, and asks for less than a set limit. Every combination is feasible and the table is not minimised. How many columns does the full limited-entry decision table have?
- A. 3
- B. 6
- C. 8
- D. 9
Show answer
Answer: C. Each column is one unique combination of condition values. Three Boolean conditions give 2 × 2 × 2 = 8 combinations, so 8 columns, and 100% decision table coverage means exercising all 8. Three (A) is the number of conditions, which are rows, not columns. Six (B) is 3 × 2, which is not how combinations multiply. Nine (D) is 3², which would fit two conditions with three values each.
Practice question 6 · Experience-based testing
A tester runs a 60-minute session-based exploratory test of a new checkout page. According to the ISTQB CTFL syllabus, what guides the tester during the session?
- A. A scripted test case with an expected result for every step
- B. A test charter containing test objectives
- C. A decision table covering every combination of inputs
- D. A traceability matrix linking each requirement to a test
Show answer
Answer: B. In session-based exploratory testing the work happens within a defined time box, and the tester uses a test charter containing test objectives to guide it. Tests are designed, executed and evaluated at the same time. A describes scripted testing, where tests are designed before execution. C is a black-box technique, not the guide for an exploratory session. D links requirements to tests for coverage reporting; it does not steer the session.
Practice question 7 · Change-related testing
A developer fixes a bug where the “Forgot password” email was not sent. On the new build, the tester first runs the exact steps that reproduced the failure and checks the email now arrives. What is this first activity called?
- A. Regression testing
- B. Smoke testing
- C. Exploratory testing
- D. Confirmation testing
Show answer
Answer: D. Confirmation testing confirms that the original defect has been fixed, often by re-running the tests that failed because of it. Regression testing (A) comes next and checks that the change has not broken anything else. A smoke test (B) is a quick, broad check that a build is stable enough to test. Exploratory testing (C) designs new tests while learning the system.
Practice question 8 · Defect management
On launch day, the company’s name is misspelled in the home page banner. Every feature works correctly. How should this defect usually be classified?
- A. Low severity, high priority
- B. High severity, high priority
- C. High severity, low priority
- D. Low severity, low priority
Show answer
Answer: A. Severity is the degree of impact on the system or its users, and a spelling error blocks no function, so it is low. Priority is how soon it should be fixed, and a visible brand error on launch day needs fixing quickly, so it is high. B and C treat it as high severity, but nothing is broken. D ignores the business impact of a public, visible mistake.
Practice question 9 · API testing
You are writing API tests and want to retry a request after a network timeout without changing the outcome. According to RFC 9110, which of these HTTP methods is NOT defined as idempotent?
- A. GET
- B. PUT
- C. POST
- D. DELETE
Show answer
Answer: C. RFC 9110 defines PUT, DELETE and the safe methods as idempotent: sending the same request several times has the same intended effect as sending it once. POST is not, so repeating it can create a second order. GET (A) is a safe method and therefore idempotent. PUT (B) replaces a resource with the same state each time, and DELETE (D) leaves the resource deleted however often it is repeated.
Practice question 10 · UI test automation
A Selenium suite sets a 5-second implicit wait and also uses 20-second explicit waits on some elements. Tests sometimes take much longer than expected before failing. What is the best fix?
- A. Increase the implicit wait to 30 seconds
- B. Add a fixed sleep after every page action
- C. Set the implicit and explicit waits to the same value
- D. Remove the implicit wait and use explicit waits for the conditions you need
Show answer
Answer: D. The Selenium documentation says not to mix implicit and explicit waits because it can cause unpredictable wait times. Explicit waits poll for a specific condition, so they wait only as long as needed. A makes failures slower and keeps the mix. B adds fixed delays that slow every test and still fail on a slow page. C still mixes the two kinds of wait, so timing stays unpredictable.
How did you score?
8–10 correct: you are in good shape, so try a full timed practice test next. Under 8: note the topic of each miss and revise the weakest one first, especially boundary values and decision tables. The Functional Testing interview practice tests have 635 more questions like these, each with an explanation, a hint and its topic area.
Common mistakes in functional testing interviews
Most mistakes come from giving a definition when the interviewer wants a method, or from loose use of testing terms.
- Only testing valid input. EP coverage includes invalid partitions. Always say what happens with empty, too small, too large and wrong-type input.
- Getting boundaries slightly wrong. State whether the boundary is inclusive, then name the boundary and its neighbour.
- Mixing up confirmation and regression testing. Confirmation checks the fix; regression checks everything around it.
- Treating severity and priority as the same thing. Give one example where they differ.
- Calling every problem a “bug”. Use error, defect and failure correctly.
- Saying testing proves there are no bugs. The first testing principle says testing shows the presence, not the absence, of defects.
- Using fixed sleeps in automation. Explain explicit waits in Selenium or auto-waiting in Playwright instead.
Our guides to manual testing interview questions on test cases, bugs and the STLC and mobile app testing interview questions cover the neighbouring topics interviewers often combine with functional testing.
Functional testing interview questions: FAQs
What are the most common functional testing interview questions?
Functional testing interview questions usually ask you to explain functional vs non-functional testing, apply equivalence partitioning and boundary value analysis, build a decision table, tell confirmation from regression testing, and explain severity vs priority. Automation roles add Selenium waits, Playwright auto-waiting and Postman API tests.
Are there free functional testing practice questions?
Yes. This post includes 10 free functional testing sample questions with full answers, covering test design techniques, exploratory testing, defects, API testing and UI automation. The full Exametics Functional Testing practice tests add 635 more questions in the same style.
How many questions are in the Exametics functional testing practice tests?
The Exametics Functional Testing Interview Practice Tests contain 635 questions across 6 practice tests of about 106 questions each, including a timed Exam Mode test. Every question has an explanation, a hint and a topic area, and you get instant access and lifetime access.
What is the difference between functional and non-functional testing?
According to the ISTQB Foundation Level syllabus, functional testing evaluates what a system should do, while non-functional testing evaluates how well it behaves. Non-functional testing covers characteristics such as performance efficiency, usability, reliability and security.
Are functional testing interviews hard, and how long should I prepare?
Functional testing interviews are manageable if you can apply test design techniques rather than only define them. Two to three weeks of focused practice on equivalence partitioning, boundary values, decision tables, state transitions and defect reports is a sensible plan for most candidates with some IT background.
Should I study for ISTQB Foundation Level before a functional testing interview?
You do not need the certificate to answer functional testing interview questions, but the ISTQB CTFL v4.0 syllabus is a useful reference because it gives you standard, precise terms. If you also want the certificate, take the interview practice first and then move to ISTQB Foundation Level practice tests.
Which tools come up in functional testing interviews?
Interviews for mixed manual and automation roles often include Selenium or Playwright for UI checks and Postman for API checks. Know how Selenium explicit waits and Playwright auto-waiting work, and how to write a Postman test that checks a status code.
Official references: ISTQB Certified Tester Foundation Level (CTFL) v4.0, plus the Selenium, Playwright, Postman and RFC 9110 pages linked above. Checked on 9 November 2026.
Practise functional testing interview questions with full explanations
After the 10 free questions, move on to six full practice tests: 635 questions across eleven topic areas, each with an explanation and a hint.
✓ Every answer explained · ✓ Timed exam mode · ✓ 30-day refund