ISTQB Practice Questions

A configuration management system would NOT normally provide

  • a) linkage of customer requirements to version numbers.
  • b) facilities to compare test results with expected results.
  • c) the precise differences in versions of software component source code.
  • d) restricted access to the source code library.
When test cases are designed early in the lifecycle, verifying the test basis via the test design, which common test objective is being achieved?

Options are :

  • Preventing defects
  • Providing information for decision making
  • Gaining confidence
  • Finding defects

Answer : Preventing defects

Explanation When verifying test basis, you're preventing defects from being created in the software. The other three are achieved primarily by doing dynamic testing.

This is a tricky one because you are very likely to find defects while doing this analysis and this may lead to either gaining or destroying confidence and needing to supply information to the decision makers.

However, the wording of the question matches the wording in the syllabus that defines preventing defects.

We split testing into distinct stages primarily because

  • a) Each test stage has a different purpose.
  • b) It is easier to manage testing in stages.
  • c) We can run different tests in different environments.
  • d) The more stages we have, the better the testing.

What is typically the MOST important reason to use risk to drive testing efforts?

Options are :

  • Because testing everything is not feasible.
  • Because risk-based testing is the most efficient approach to finding bugs.
  • Because risk-based testing is the most effective way to show value.
  • Because software is inherently risky.

Answer : Because testing everything is not feasible.

Explanation when we use risk to drive testing efforts that means we are using risk based testing the main objective to of risk based testing is to minimize the product risk that would happen at the customer.

Risk based testing helps us to choose what to test first what to test most and what not to test. all the answers looks OK, but answer A seems more correct as it is conforms with the testing principle "Exhaustive testing is not possible" so we need a method to select what we can test.

As we use risk based testing helps us to choose what to test first what to test most and what not to test because we can not test everything

Which one of the following describes the major benefit of verification early in the life cycle?

Options are :

  • It allows the identification of changes in user requirements.
  • It facilitates timely set up of the test environment.
  • It reduces defect multiplication.
  • It allows testers to become involved early in the project.

Answer : It reduces defect multiplication.

Explanation All the answers might same correct but let us think of the real benefit of "Early testing". Of course finding the defects early will make it cheaper to solve it but it will also help in avoiding of accumalting the defects over time.

Faulty requirements will produce faulty design will produce faulty code. So one of the greatest benefits of "Early testing" is " It reduces defect multiplication"

Which of the following is likely to benefit most from the use of test tools providing test capture and replay facilities?

  • a) Regression testing
  • b) Integration testing
  • c) System testing
  • d) User acceptance testing
Which of the following statements is true?

Options are :

  • Testing cannot prove that software is incorrect.
  • Testing can prove that software is either correct or incorrect.
  • Testing cannot prove that software is correct.
  • Testing can prove that software is correct.

Answer : Testing cannot prove that software is correct.

Explanation Correct here means "has no bugs" The first testing principle : testing shows presence of defects means that (i) testing can prove that the software is incorrect and (ii) it can not prove that the software is correct.

so "Testing cannot prove that software is incorrect." is wrong because it can prove that the software is incorrect "Testing can prove that software is either correct or incorrect." is wrong because it can't prove that the software is correct "Testing can prove that software is correct." is wrong because it can't prove the software is correct hence C is correct accrding to (ii)

which of the following statements is true?

Options are :

  • Faults in program specifications are the most expensive to fix.
  • Faults in code are the most expensive to fix.
  • Faults in requirements are the most expensive to fix
  • Faults in designs are the most expensive to fix.

Answer : Faults in requirements are the most expensive to fix

Explanation correct answer is "Faults in requirements are the most expensive to fix" Notice here that we are usually talking about defects found during system testing. the older the fault, the most costly it will be if discovered during system testing. So the most expensive fault will be requirement, then specification, ten design then last code

Which of the following statements is NOT correct?

  • a) A minimal test set that achieves 100% LCSAJ coverage will also achieve 100% branch coverage.
  • b) A minimal test set that achieves 100% path coverage will also achieve 100% statement coverage.
  • c) A minimal test set that achieves 100% path coverage will generally detect more faults than one that achieves 100% statement coverage.
  • d) A minimal test set that achieves 100% statement coverage will generally detect more faults than one that achieves 100% branch coverage.

Which of the following requirements is testable?

  • a) The system shall be user friendly.
  • b) The safety-critical parts of the system shall contain 0 faults.
  • c) The response time shall be less than one second for the specified design load.
  • d) The system shall be built to be portable.

Though activities in the Fundamental test process may overlap or occur concurrently, identify the logical sequential process. 

(i) Test Implementation and Execution 

(ii) Test Closure activities 

(iii) Evaluating exit criteria and reporting 

(iv) Test Planning and Control 

(v) Test Analysis and Design

Options are :

  • iv – v – iii – ii – i
  • v – i – iii – ii – iv
  • iv – v – i – iii – ii
  • v – ii – iii – i – iv

Answer : iv – v – i – iii – ii

Explanation The sequential steps in fundamental test process are Test Planning and Control Test Analysis and Design Test Implementation and Execution Evaluating exit criteria and reporting Test Closure activities

Which of the following is a MAJOR task of evaluating exit criteria and reporting?

Options are :

  • Writing a test summary report for stakeholders
  • Logging the outcome of test execution
  • Repeating test activities as a result of action taken for each discrepancy.
  • Evaluating testability of the requirements and system

Answer : Writing a test summary report for stakeholders

Explanation Correct answer is "Writing a test summary report for stakeholders" as part of "evaluating exit criteria and reporting" "Evaluating testability of the requirements and system" is part of "Analysis and Design", "Logging the outcome of test execution" is part of "Implementation and Execution" and "Repeating test activities as a result of action taken for each discrepancy." is part of "Test Control"

Error guessing

  • a) supplements formal test design techniques.
  • b) can only be used in component, integration and system testing.
  • c) is only performed in user acceptance testing.
  • d) is not repeatable and should not be used.
A software model that can not be used in functional testing

Options are :

  • Menu structure model
  • Process flow model
  • State transaction model
  • Plain language specification model

Answer : Menu structure model

Explanation First, notice the NOT in the body of the question. To do functional testing, you need something (test basis) that will explain to you how the software should work and how it should behave.

"Menu Structure Model" is the correct answer .. because knowing the menu items in the menu bar of the software DOES NOT tell you how it should behave. In all the options, try to imagine which one will tell you the expected behavior of the software.

Which of the following is NOT true of test coverage criteria?

  • a) Test coverage criteria can be measured in terms of items exercised by a test suite.
  • b) A measure of test coverage criteria is the percentage of user requirements covered.
  • c) A measure of test coverage criteria is the percentage of faults found.
  • d) Test coverage criteria are often used when specifying test completion criteria.
The main focus of acceptance testing is:

Options are :

  • testing for a business perspective
  • finding faults in the system
  • ensuring that the system is acceptable to all users
  • testing the system with other systems

Answer : testing for a business perspective

Explanation The main focus of acceptance testing is to ACCEPT the system. the user will try to system to see if it fits his needs. you might think "ensuring that the system is acceptable to all users" is correct .. but to get ALL users to accept the system is not realistic. and a good tip ...always doubt an answer with the words "all" or "only" in it

which of the following statements is not true

Options are :

  • Verification activities should not involve testers (reviews, inspections etc.)
  • performance testing can be done during unit testing as well as during the testing of whole system
  • The acceptance test does not necessarily include a regression test
  • Test environments should be as similar to production environments as possible.

Answer : Verification activities should not involve testers (reviews, inspections etc.)

Explanation All test types can be done during all test levels. Hence options " performance testing can be done during unit testing as well as during the testing of whole system" and "The acceptance test does not necessarily include a regression test" are correct options.

option "Test environments should be as similar to production environments as possible" is definitely true. So the correct false option is "Verification activities should not involve testers (reviews, inspections etc.)" as testers can be involved in such activities.

In prioritising what to test, the most important objective is to

  • a) find as many faults as possible.
  • b) test high risk areas.
  • c) obtain good test coverage.
  • d) test whatever is easiest to test.
Which of the following are true of software development models? a) Component Integration testing is present in all good development models. b) Acceptance testing can take place before system testing starts. c) Acceptance testing should only start when system testing is complete. d) There may be fewer than four test levels in a V-model.

Options are :

  • b and d
  • a and b
  • b and c
  • c and d

Answer : b and d

Explanation Acceptance testing can happen at any time in the project .. so c is wrong. Some software models don't have the four test levels and many the "components integration testing" is combined or integrated with the components testing. So option d is correct which also means option a is incorrect so the correct answer is b and d

Which one of the following statements about system testing is NOT true?

  • a) System tests are often performed by independent teams.
  • b) Functional testing is used more than structural testing.
  • c) Faults found during system tests can be very expensive to fix.
  • d) End-users should be involved in system tests.
What is the main purpose of impact analysis for testers?

Options are :

  • To determine the programming effort needed to make the changes.
  • To determine what proportion of the changes need to be tested.
  • To determine how much the planned changes will affect users.
  • To determine how the existing system may be affected by changes.

Answer : To determine how the existing system may be affected by changes.

Explanation impact analysis is done when we do maintenance testing and we do it to determine how the existing system may be affected by changes. In maintenance testing, we test all the changes not just a propotion of the changes. Also the question is asking about the testers, so the programming effort is not what we are looking for.

A number of critical bugs are fixed in software. All the bugs are in one module, related to reports. The test manager decides to do regression testing only on the reports module.

Options are :

  • The test manager should do only automated regression testing.
  • The test manager is justified in her decision because no bug has been fixed in other modules
  • The test manager should only do confirmation testing. There is no need to do regression testing
  • Regression testing should be done on other modules as well because fixing one module may affect other modules

Answer : Regression testing should be done on other modules as well because fixing one module may affect other modules

Explanation It is most likely that when a developer fixes a defect in one module that another bug could created any where in the application. So the manager is wrong in her decision and Regression testing should be done on other modules as well because fixing one module may affect other modules.

Which of the following is false?

  • a) Incidents should always be fixed.
  • b) An incident occurs when expected and actual results differ.
  • c) Incidents can be analysed to assist in test process improvement.
  • d) An incident can be raised against documentation.
What can static analysis NOT find?

Options are :

  • Whether the value stored in a variable is correct
  • The use of a variable before it has been defined
  • Unreachable (“dead?) code
  • The re-definition of a variable before it has been used

Answer : Whether the value stored in a variable is correct

Explanation I like to think what compilers can do when thinking of static analysis tools. try to imagine what could find WITHOUT running the system.

you will see that it can do all the option except "Whether the value stored in a variable is correct" .. how would a tool know if a value is correct or not... we need the requirements to check if it is correct or not ... we need to run the system to do that too so correct answer "Whether the value stored in a variable is correct"

Enough testing has been performed when

  • a) time runs out.
  • b) the required level of confidence has been achieved.
  • c) no more faults are found.
  • d) the users won’t find any serious faults.
Which of the following activities differentiate a walkthrough from a formal review?

Options are :

  • A walkthrough does not follow a defined process
  • For a walkthrough individual preparation by the reviewers is optional
  • A walkthrough requires meeting
  • A walkthrough finds the causes of failures, while formal review finds the failures

Answer : For a walkthrough individual preparation by the reviewers is optional

Explanation walkthrough follows the steps of the review process ... yes some of the steps are optional ...but we can not say that the process is not defined.

Also formal review and walkthrough both share having a meeting. Also both finds the causes of failures and non of them finds failures (dynamic testing does) So the correct answer is "For a walkthrough individual preparation by the reviewers is optional"

In formal review, Rework: fixing defects found typically done by _________

Options are :

  • Moderator
  • Author
  • Reviewer
  • Recorder

Answer : Author

Explanation In formal review, Rework: fixing defects found typically done by the author

Which of the following is NOT true of incidents?

  • a) Incident resolution is the responsibility of the author of the software under test.
  • b) Incidents may be raised against user requirements.
  • c) Incidents require investigation and/or correction.
  • d) Incidents are raised when expected and actual results differ.

Which of the following statements describe why experience-based test design techniques are useful? 

a. They can help derive test cases based on analysis of specification documents. 

b. They can identify tests not easily captured by formal techniques. 

c. They make good use of tester's knowledge, intuition and experience. 

d. They are an effective alternative to formal test design techniques.

Options are :

  • a and b
  • b and d
  • c and d
  • b and c

Answer : b and c

Explanation option "a" is not correct because experience based testing doesn't depend on specification documents but rather or the tester's experience.

Option "d" is not correct because formal test design techniques and experience based test design techniques are complementary not alternatives. So correct answer is "b and c"

If a candidate is given an exam of 40 questions, should get 25 marks to pass (61%) and should get 80% for distinction, what set of values are from the same equivalence class.

Options are :

  • 23, 24, 25
  • 32,37,40
  • 0, 12, 25
  • 30, 36, 39

Answer : 32,37,40

Explanation Notice here that they are asking for values from the SAME equivalence class/partition. Partitions are 0->24, 25->31, 32->40 take very good care when you decide the boundaries of each partition. Looking at the answer options, the only answer that has values from the SAME partition is "32, 37, 40"

Which of the following is not described in a unit test standard?

  • a) syntax testing
  • b) equivalence partitioning
  • c) stress testing
  • d) modified condition/decision coverage
An input field takes the year of birth between 1900 and 2004. The boundary values for testing this field are:

Options are :

  • 0, 1900, 2004, 2005
  • 1900, 2004
  • 1899, 1900, 2004, 2005
  • 1899, 1900, 1901, 2003, 2004, 2005

Answer : 1899, 1900, 2004, 2005

Explanation We have 3 partitions from negative infinity to 1989 from 1990 to 2004 from 2005 to positive infinity as we are looking for all valid and invalid boundaries then the answer "1899, 1900, 2004, 2005" is the correct answer

Which of the following is false?

  • a) In a system two different failures may have different severities.
  • b) A system is necessarily more reliable after debugging for the removal of a fault.
  • c) A fault need not affect the reliability of a system.
  • d) Undetected errors may lead to faults and eventually to incorrect behaviour.


ISTQB Questions
ISTQB Questions 1
ISTQB Questions 2
ISTQB Questions 3
ISTQB Questions 4
ISTQB Questions 5
ISTQB Questions 6
ISTQB Questions 7
Comment / Suggestion Section
Point our Mistakes and Post Your Suggestions

Protractor Training

new tutorial I am starting new Protractor training batch on Weekends. It is two days course from 01-june-2019 to 02-june-2019 based on class room (BANGALORE)

Interested people can confirm the seat by calling to +91 8971673487 or whatsapp to +91 9003381224

Find the course content : View Content