ISTQB Practice Questions

What statement about expected outcomes is FALSE

Options are :

  • expected outcomes are defined by the software's behavior
  • expected outcomes are derived from a specification, not from the code
  • expected outcomes include outputs to a screen and changes to files and databases
  • expected outcomes should be predicted before a test is run

Answer : expected outcomes are defined by the software's behavior

Explanation Note that they are looking for the FALSE answer. the software behavior is what the developer wrote , and this could be totally wrong ... we don't test the software based on the actual behavior of the software but upon the planned behavior of the software which can be found in the specification

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

Options are :

  • Test coverage criteria can be measured in terms of items exercised by a test suite.
  • A measure of test coverage criteria is the percentage of user requirements covered.
  • A measure of test coverage criteria is the percentage of faults found.
  • Test coverage criteria are often used when specifying test completion criteria.

Answer : A measure of test coverage criteria is the percentage of faults found.

Explanation "A measure of test coverage criteria is the percentage of faults found." is the correct answer Test coverage in general means how much our test cases covered the actual content of the software. so we can test the our coverage to the code or requrements and it can be used as an exit creiteria.

Which of the following is NOT part of system testing

  • a) business process-based testing
  • b) performance, load and stress testing
  • c) requirements-based testing
  • d) usability testing
  • e) top-down integration testing
Exclusive use of white box testing in a test-phase will:

Options are :

  • Ensure the test item is adequately tested.
  • Make the need for black-box testing redundant.
  • Run the risk that the requirements are not satisfied.
  • Suffices for the unit testing phase.

Answer : Run the risk that the requirements are not satisfied.

Explanation black and white testing should be complementary.. we shouldn't use one of them and leave the other so white box testing alone will Run the risk that the requirements are not satisfied. Answer "Run the risk that the requirements are not satisfied." is correct

A test engineer is testing a Video Player (VCR), and logs the following report: 

Title: Fast Forward stops after 2 minutes. 

It happens every time Expected result: Fast forward continues till the end of the tape 

Severity: High 

Priority: Urgent 

What important information did the engineer leave out?

Options are :

  • Identification (Software and hardware) of the VCR
  • Actual result
  • History of the report
  • Ideas for the test case improvement

Answer : Identification (Software and hardware) of the VCR

Explanation " Ideas for the test case improvement " should not be included in the report "History of the report" is not important especially if it is a new report Correct answer is "Identification (Software and hardware) of the VCR" "Actual result" is already included

What statement about expected outcomes is FALSE

  • a) expected outcomes are defined by the software’s behaviour
  • b) expected outcomes are derived from a specification, not from the code
  • c) expected outcomes include outputs to a screen and changes to files and databases
  • d) expected outcomes should be predicted before a test is run
  • e) expected outcomes may include timing constraints such as response times

Which of the following would TYPICALLY be carried out by a test leader and which by a tester?

a. Creation of a test strategy.

b. Creation of a test specification.

c. Raising of an incident report.

d. Write a test summary report.

Options are :

  • a and d would be carried out by a test leader, whilst b and c would be carried out by a tester
  • a and b would be carried out by a test leader, whilst c and d would be carried out by a tester
  • b and c would be carried out by a test leader, whilst a and d would be carried out by a tester
  • a and c would be carried out by a test leader, whilst b and d would be carried out by a tester

Answer : a and d would be carried out by a test leader, whilst b and c would be carried out by a tester

Explanation Tester leaders create test strategies and write summary reports while testers create test specification and raise incident reports

The standard that gives definitions of testing terms is

  • a) ISO/IEC 12207
  • b) BS7925-1
  • c) BS7925-2
  • d) ANSI/IEEE 829
  • e) ANSI/IEEE 729

Which of the following is determined by the level of product risk identified?

Options are :

  • Extent of testing
  • Scope for the use of test automation.
  • Size of the test team.
  • Requirement for regression testing

Answer : Extent of testing

Explanation correct answer is "Extent of testing". if the risks in the product high then we increase the testing to lower the risk level and vise versa. part of increasing the extent of testing might be "but not necessary" increasing the test team size.

Which of the following is NOT true of incidents?

Options are :

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

Answer : Incident resolution is the responsibility of the author of the software under test

Explanation This is a little tricky as all of the answers seem true. But if we look more closely at "Incident resolution is the responsibility of the author of the software under test." we can say that any developer can solve an incident and not necessarily the author of the software under test. Also don't forget that incidents don't need to be bugs, they can be questions or suggestions.

The cost of fixing a fault

  • a) Is not important
  • b) Increases as we move the product towards live use
  • c) Decreases as we move the product towards live use
  • d) Is more expensive if found in requirements than functional design
  • e) Can never be determined
In a REACTIVE approach to testing when would you expect the bulk of the test design work to be begun?

Options are :

  • After the software or system has been produced.
  • During development.
  • As early as possible.
  • During requirements analysis.

Answer : After the software or system has been produced.

Explanation from it's name reactive testing means that our testing will be based on whatever happens around us. so I "After the software or system has been produced" would be a correct answer because we will test after the the developmenent of the software and see what will happen then

Which of the following is NOT part of a high level test plan?

Options are :

  • Functions not to be tested.
  • Environmental requirements.
  • Analysis of Specifications.
  • Entry and Exit criteria.

Answer : Analysis of Specifications.

Explanation analysis of the specifications is done to create the test conditions and hence test cases. and done by the tester so it's not part of the test paln. So correct answer is "Analysis of Specifications."

Error guessing is best used

  • a) As the first approach to deriving test cases
  • b) After more formal techniques have been applied
  • c) By inexperienced testers
  • d) After the system has gone live
  • e) Only by end users
The following list contains risks that have been identified for a software product to be developed. Which of these risks is an example of a product risk?

Options are :

  • Not enough qualified testers to complete the planned tests
  • Software delivery is behind schedule
  • Threat to a patient's life
  • 3rd party supplier does not supply as stipulated

Answer : Threat to a patient's life

Explanation If the risk happens at development organzation then it's a project risk and if it occurs at the customer site then it is a product risk. "Threat t a paiient's life" could happen when running the software at the customer's site, so it is a product risk. So Schedule, team staffing and 3rd party issues are all project risk.

Which of the following is NOT included in the Test Plan document of the Test Documentation Standard

  • a) Test items (i.e. software versions)
  • b) What is not to be tested
  • c) Test environments
  • d) Quality plans
  • e) Schedules and deadlines
Which of the following is likely to benefit most from the use of test tools providing capture and replay facilities?

Options are :

  • Regression testing
  • integration testing
  • System testing
  • user acceptance testing

Answer : Regression testing

Explanation Correct answer is "Regression Testing" Generally speaking, automation testing tools (or in this case capture-replay tools) MAIN PURPOSE is for regression testing. saying that capture-replay tools are good for exploratory testing is a specific case that ISTQB mentioned but the main purpose is for regression testing.

In regression testing, we run many test cases to make sure nothing is broken. so if we could automate that, it would save us huge amount of time. So execution testing tools (and capture-replay tools as part of execution testing tools) are good for regression testing.

Which of the following is not considered as a benefit of testing tools?

Options are :

  • Ability to detect tiny changes that a human could not
  • Easy to implement and maintain
  • Test assets are more consistent
  • Ease of measurement of software quality

Answer : Easy to implement and maintain

Explanation Test tools are actually hard to implement and maintain. Takes time, effort, training to get used it.

From the list below, select the recommended principles for introducing a chosen test tool in an organization? 

1. Roll the tool out to the entire organization at the same time. 

2. Start with a pilot project. 

3. Adapt and improve processes to fit the use of the tool. 

4. Provide training and coaching for new users. 

5. Let each team decide their own standard ways of using the tool. 

6. Monitor that costs do not exceed initial acquisition cost. 

7. Gather lessons learned from all teams.

Options are :

  • 1, 2 , 3, 5
  • 1, 4, 6, 7
  • 2, 3, 4, 7
  • 3, 4, 5, 6

Answer : 2, 3, 4, 7

Explanation It is recommended to start with a pilot project and not roll out the tool to the entire organization at the same time. Also it is recommended to standardize the process to use the tool across the organizaton

Could reviews or inspections be considered part of testing

  • a) No, because they apply to development documentation
  • b) No, because they are normally applied before testing
  • c) No, because they do not apply to the test documentation
  • d) Yes, because both help detect faults and improve quality
  • e) Yes, because testing includes all non-constructive activities
The _________ may facilitate the testing of components or part of a system by simulating the environment in which the test object will run

Options are :

  • Test Design tool
  • Test data preparation tool
  • Test execution tool
  • Test harness

Answer : Test harness

Explanation The Test harness may facilitate the testing of components or part of a system by simulating the environment in which the test object will run.

When a new testing tool is purchased, it should be used first by:

Options are :

  • A small team to establish the best way to use the tool
  • Everyone who may eventually have some use for the tool
  • The independent testing team
  • The managers to see what projects it should be used in

Answer : A small team to establish the best way to use the tool

Explanation "A small team to establish the best way to use the tool" is the correct answer because we need to have a pilot project to assess the tool, establish the best way to use the tool, adopt our existing processes to use the tool and more. We can't do all these with a large number of people, it will be a waste of time and effort.

What is the difference between use case and test case

Options are :

  • There is no difference, they are the same, except that Use case is built by a Business User, and a test case is built by a tester.
  • Use case is related to usability testing and test cases are related to functional testing
  • A use case is a description of a system's behavior as it responds to a request that originates from outside of that system and a test case consists of input values, execution preconditions, developed for a particular objective or test condition to verify compliance to a specific requirement
  • Use case to test case is a one to many relationship

Answer : A use case is a description of a system's behavior as it responds to a request that originates from outside of that system and a test case consists of input values, execution preconditions, developed for a particular objective or test condition to verify compliance to a specific requirement

Explanation A use case is a description of a system's behavior as it responds to a request that originates from outside of that system and a test case consists of input values, execution preconditions, developed for a particular objective or test condition to verify compliance to a specific requirement

Which of the following is not part of performance testing

  • a) Measuring response time
  • b) Measuring transaction rates
  • c) Recovery testing
  • d) Simulating many users
  • e) Generating many transactions


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