ISTQB Foundation Sample Question Paper No. 3

Reviewed by Editorial Team
The ProProfs editorial team is comprised of experienced subject matter experts. They've collectively created over 10,000 quizzes and lessons, serving over 100 million users. Our team includes in-house content moderators and subject matter experts, as well as a global network of rigorously trained contributors. All adhere to our comprehensive editorial guidelines, ensuring the delivery of high-quality content.
Learn about Our Editorial Process
| By Devilbrand
D
Devilbrand
Community Contributor
Quizzes Created: 8 | Total Attempts: 11,498
| Attempts: 500
Quiz Flashcard
SettingsSettings
Please wait...
  • 1/40 Questions

    Acceptance test cases are based on what?

    • Requirements
    • Design
    • Code
    • Decision table
Please wait...
ISTQB Quizzes & Trivia
About This Quiz

ISTQB Foundation Sample Question Paper No. 3 assesses key competencies in software testing. It covers the initiation of testing activities, reasons for software faults, importance of pre-release testing, and prioritization of test execution. Essential for those preparing for ISTQB certification.

Quiz Preview

  • 2. 

    An incident logging system

    • Only records defects

    • Is of limited value

    • Is a valuable source of project information during testing if it contains all incidents

    • Should be used only by the test team

    Correct Answer
    A. Is a valuable source of project information during testing if it contains all incidents
    Explanation
    An incident logging system is a valuable source of project information during testing if it contains all incidents. This means that if the system accurately records all defects and incidents that occur during testing, it can provide valuable insights and data for the project. This information can be used to analyze trends, identify common issues, and make informed decisions to improve the overall quality of the project. However, if the system only records defects or is used exclusively by the test team, its value may be limited as it may not capture a comprehensive view of the project's performance and issues.

    Rate this question:

  • 3. 

    A common test technique during component test is

    • Statement and branch testing

    • Usability testing

    • Security testing

    • Performance testing

    Correct Answer
    A. Statement and branch testing
    Explanation
    Statement and branch testing is a common test technique during component testing. This technique involves testing all possible statements and branches within the component's code to ensure that they are functioning correctly. By testing each statement and branch, developers can identify any errors or flaws in the code and make necessary adjustments to improve the component's reliability and performance. This technique helps ensure that the component meets the desired functionality and behaves as expected in different scenarios.

    Rate this question:

  • 4. 

    Which of the following tools would be involved in the automation of regression test?

    • Data tester

    • Boundary tester

    • Capture/Playback

    • Output comparator

    Correct Answer
    A. Capture/Playback
    Explanation
    Capture/Playback is a tool that would be involved in the automation of regression testing. Regression testing involves retesting the previously tested functionalities to ensure that the changes or fixes made in the software have not introduced any new defects. Capture/Playback tools allow testers to record their actions while testing and then replay them later, automating the repetitive tasks. This helps in saving time and effort during regression testing, as the recorded actions can be replayed multiple times to ensure the stability of the software.

    Rate this question:

  • 5. 

    Which of the following is a black box design technique?

    • Statement testing

    • Equivalence partitioning

    • Error- guessing

    • Usability testing

    Correct Answer
    A. Equivalence partitioning
    Explanation
    Equivalence partitioning is a black box design technique where test cases are designed based on dividing the input domain into a set of equivalent classes. Each class represents a range of valid or invalid inputs that are expected to produce the same output. This technique helps in reducing the number of test cases while still ensuring adequate coverage of the input space. It focuses on testing representative values from each class rather than testing every possible input value.

    Rate this question:

  • 6. 

    Faults found by users are due to:

    • Poor quality software

    • Poor software and poor testing

    • Bad luck

    • Insufficient time for testing

    Correct Answer
    A. Poor software and poor testing
    Explanation
    The correct answer is "Poor software and poor testing." This suggests that the faults found by users are a result of both the software being of low quality and the testing process being inadequate. It implies that the software itself is flawed and the testing conducted on it is not thorough enough to identify and rectify these flaws.

    Rate this question:

  • 7. 

    Incorrect form of Logic coverage is:

    • Statement Coverage

    • Pole Coverage

    • Condition Coverage

    • Path Coverage

    Correct Answer
    A. Pole Coverage
  • 8. 

    To test a function, the programmer has to write a _________, which calls the function to be tested and passes it test data.

    • Stub

    • Driver

    • Proxy

    • None of the answers are correct

    Correct Answer
    A. Driver
    Explanation
    In order to test a function, the programmer needs to write a driver. A driver is a piece of code that calls the function to be tested and passes it test data. This allows the programmer to simulate the behavior of the function and verify its correctness. A driver is essential in the testing process as it helps ensure that the function performs as expected and produces the desired results.

    Rate this question:

  • 9. 

    In which order should tests be run?

    • The most important tests first

    • The most difficult tests first(to allow maximum time for fixing)

    • The easiest tests first(to give initial confidence)

    • The order they are thought of

    Correct Answer
    A. The most important tests first
    Explanation
    Running the most important tests first is the suggested order because it prioritizes the critical functionalities and ensures that they are thoroughly tested. By focusing on the most important tests, any major issues or bugs can be identified and addressed early in the testing process, reducing the risk of critical failures in the final product. This approach allows for efficient use of time and resources, ensuring that the essential features are validated before moving on to less critical tests.

    Rate this question:

  • 10. 

    Which of the following is true?

    • Component testing should be black box, system testing should be white box.

    • If you find a lot of bugs in testing, you should not be very confident about the quality of software

    • The fewer bugs you find,the better your testing was

    • The more tests you run, the more bugs you will find

    Correct Answer
    A. If you find a lot of bugs in testing, you should not be very confident about the quality of software
    Explanation
    If a lot of bugs are found during testing, it indicates that there may be more undiscovered bugs in the software. This suggests that the quality of the software may not be as high as expected. Therefore, finding a lot of bugs during testing should make one less confident about the overall quality of the software.

    Rate this question:

  • 11. 

    The later in the development life cycle a fault is discovered, the more expensive it is to fix. why?

    • The documentation is poor, so it takes longer to find out what the software is doing.

    • Wages are rising

    • The fault has been built into more documentation,code,tests, etc

    • None of the choices are correct

    Correct Answer
    A. The fault has been built into more documentation,code,tests, etc
    Explanation
    The later in the development life cycle a fault is discovered, the more expensive it is to fix because the fault has been built into more documentation, code, tests, etc. This means that the fault has had more time to propagate and affect various aspects of the software system. As a result, fixing the fault requires not only identifying and correcting the error itself but also addressing any ripple effects it may have caused. This can involve making changes to multiple components, retesting and revalidating the system, and potentially disrupting other functionality that relies on the faulty code. All of these factors contribute to the increased cost of fixing the fault.

    Rate this question:

  • 12. 

    A program with high cyclometic complexity is almost likely to be:

    • Large

    • Small

    • Difficult to write

    • Difficult to test

    Correct Answer
    A. Difficult to test
    Explanation
    A program with high cyclomatic complexity is difficult to test because it has a large number of possible paths and decision points. This complexity makes it challenging to create test cases that cover all possible scenarios and ensure adequate test coverage. The higher the cyclomatic complexity, the more complex the program becomes, leading to increased difficulty in identifying and fixing bugs or errors during testing.

    Rate this question:

  • 13. 

    Which is not true-The black box tester?

    • Should be able to understand a functional specification or requirements document

    • Should be able to understand the source code.

    • Is highly motivated to find faults

    • Is creative to find the system’s weaknesses

    Correct Answer
    A. Should be able to understand the source code.
    Explanation
    The black box tester is not required to understand the source code. Their role is to test the system's functionality without any knowledge of its internal workings. They focus on testing the system based on the functional specification or requirements document provided to them. They are highly motivated to find faults and are creative in identifying the system's weaknesses. However, understanding the source code is not a requirement for black box testing.

    Rate this question:

  • 14. 

    When should you stop testing?

    • When time for testing has run out

    • When all planned tests have been run

    • When the test completion criteria have been met

    • When no faults have been found by the tests run

    Correct Answer
    A. When the test completion criteria have been met
    Explanation
    The correct answer is when the test completion criteria have been met. This means that testing should stop when the predetermined goals and objectives of the testing process have been achieved. The test completion criteria define the conditions that must be fulfilled for testing to be considered complete. It ensures that all necessary tests have been executed and the desired level of quality has been achieved. This approach allows for a systematic and controlled testing process, ensuring that all requirements and specifications have been adequately validated.

    Rate this question:

  • 15. 

    Which of the following is a static test?

    • Code inspection

    • Coverage analysis

    • Usability assessment

    • Installation test

    Correct Answer
    A. Code inspection
    Explanation
    A code inspection is a static test because it involves reviewing the code without executing it. It is a manual process where developers or testers examine the code to identify defects, violations of coding standards, and potential issues. This type of test does not involve running the code or executing any functionality. Instead, it focuses on analyzing the code structure, logic, and quality to ensure that it meets the required standards and guidelines. Code inspections are typically conducted during the development phase to catch errors early and improve the overall code quality.

    Rate this question:

  • 16. 

    An input field takes the year of birth between 1900 and 2004. The boundary values for testing this field are:

    • 0,1900,2004,2005

    • 1900, 2004

    • 1899,1900,2004,2005

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

    Correct Answer
    A. 1899,1900,2004,2005
    Explanation
    The given answer suggests that the boundary values for testing the input field are 1899, 1900, 2004, and 2005. These values are chosen because they represent the minimum and maximum valid years of birth (1900 and 2004), as well as values outside of this range (1899 and 2005) to test the field's boundary conditions. By testing these values, we can ensure that the input field correctly accepts valid years within the specified range and rejects invalid years outside of it.

    Rate this question:

  • 17. 

    Testware (test cases, test dataset)

    • Needs configuration management just like requirements, design and code

    • Should be newly constructed for each new version of the software

    • Is needed only until the software is released into production or use

    • Does not need to be documented and commented, as it does not form part of the released software system

    Correct Answer
    A. Needs configuration management just like requirements, design and code
    Explanation
    Testware, which includes test cases and test datasets, needs configuration management just like requirements, design, and code. This is because testware is an essential component of the software development process and undergoes changes and updates throughout the software lifecycle. Configuration management ensures that the testware is properly versioned, controlled, and documented, allowing for traceability and reproducibility of tests. By managing the configuration of testware, organizations can effectively track changes, maintain consistency, and ensure the reliability and quality of the testing process.

    Rate this question:

  • 18. 

    Statement Coverage will not check for which of the following:

    • Missing Statements

    • Unused Branches

    • Dead Code

    • Unused Statement

    Correct Answer
    A. Missing Statements
    Explanation
    Statement coverage is a testing technique that ensures that each statement in the code has been executed at least once. It helps in identifying missing statements, unused branches, and dead code. However, it does not specifically check for missing statements, as it focuses on the execution of existing statements. Therefore, the correct answer is "Missing Statements".

    Rate this question:

  • 19. 

    Which of the following is NOT a standard related to testing?

    • IEEE829

    • IEEE610

    • BS7925-1

    • BS7925-2

    Correct Answer
    A. IEEE610
    Explanation
    IEEE610 is not a standard related to testing. The other options, IEEE829, BS7925-1, and BS7925-2, are all standards that pertain to testing.

    Rate this question:

  • 20. 

    A program validates a numeric field as follows: values less than 10 are rejected values between 10 and 21 are accepted values greater than or equal to 22 are rejected   Which of the following covers the MOST boundary values?

    • 9,10,11,22

    • 9,10,21,22

    • 10,11,21,22

    • 10,11,20,21

    Correct Answer
    A. 9,10,21,22
    Explanation
    The correct answer is 9,10,21,22. This answer covers the most boundary values because it includes the lowest value that is rejected (9), the lowest value that is accepted (10), the highest value that is accepted (21), and the lowest value that is rejected (22). This set of values covers all three ranges specified in the validation criteria.

    Rate this question:

  • 21. 

    When reporting faults found to developers, testers should be:

    • As polite, constructive and helpful as possible

    • Firm about insisting that a bug is not a “feature” if it should be fixed

    • Diplomatic, sensitive to the way they may react to criticism

    • All of the answers are correct

    Correct Answer
    A. All of the answers are correct
    Explanation
    Testers should be polite, constructive, and helpful when reporting faults to developers in order to maintain a positive and collaborative working relationship. They should also be firm in insisting that a bug is not a "feature" if it should be fixed, to ensure that the product meets the required standards. Additionally, testers should be diplomatic and sensitive to the way developers may react to criticism, as this can help foster a productive and respectful environment. Therefore, all of the given answers are correct as they highlight different aspects of effective communication and collaboration between testers and developers.

    Rate this question:

  • 22. 

    Increasing the quality of the software, by better development methods, will affect the time needed for testing (the test phases) by:

    • Reducing test time

    • No change

    • Increasing test time

    • Can’t say

    Correct Answer
    A. Reducing test time
    Explanation
    Improving the quality of the software through better development methods can lead to a decrease in the time required for testing. When the software is of higher quality, there are likely to be fewer defects and issues to address during the testing phase. This means that the testing team will spend less time identifying and fixing problems, resulting in a reduction in overall test time.

    Rate this question:

  • 23. 

    Which of the following is not a quality characteristic listed in ISO 9126 Standard?

    • Functionality

    • Usability

    • Supportability

    • Maintainability

    Correct Answer
    A. Supportability
    Explanation
    Supportability is not listed as a quality characteristic in the ISO 9126 Standard. ISO 9126 defines a set of quality characteristics for software products, including functionality, usability, and maintainability. Supportability refers to the ability of a software product to be supported, such as through helpdesk services or technical support, but it is not specifically listed as a quality characteristic in the ISO 9126 Standard.

    Rate this question:

  • 24. 

    What is the important criterion in deciding what testing technique to use?

    • How well you know a particular technique

    • The objective of the test

    • How appropriate the technique is for testing the application

    • Whether there is a tool to support the technique

    Correct Answer
    A. The objective of the test
    Explanation
    The important criterion in deciding what testing technique to use is the objective of the test. This means that the purpose or goal of the test should be considered when selecting a testing technique. The objective of the test will determine what needs to be tested and what aspects of the application need to be focused on. Therefore, the testing technique should align with the test objective in order to effectively and efficiently achieve the desired results.

    Rate this question:

  • 25. 

    A program validates a numeric field as follows: values less than 10 are rejected values between 10 and 21 are accepted values greater than or equal to 22 are rejected   Which of the following input values cover all of the equivalence partitions?

    • 10,11,21

    • 3,20,21

    • 3,10,22

    • 10,21,22

    Correct Answer
    A. 3,10,22
    Explanation
    The input values 3, 10, and 22 cover all of the equivalence partitions because they represent values that are rejected, accepted, and rejected respectively according to the given validation rules. A value less than 10 (3) is rejected, a value between 10 and 21 (10) is accepted, and a value greater than or equal to 22 (22) is rejected. Therefore, these input values cover all the possible scenarios based on the given validation rules.

    Rate this question:

  • 26. 

    Which one of the following are non-functional testing methods?

    • System testing

    • Usability testing

    • Performance testing

    • Performance testing & Usability testing

    Correct Answer
    A. Performance testing & Usability testing
    Explanation
    Performance testing and usability testing are both non-functional testing methods. Non-functional testing focuses on the performance, usability, reliability, and other non-functional aspects of a system, rather than its specific functionality. Performance testing is used to evaluate how well a system performs under different conditions, such as high user loads or stress. Usability testing, on the other hand, assesses how user-friendly and intuitive a system is, by observing users' interactions with it. Both of these methods are used to ensure that the system meets the non-functional requirements and provides a satisfactory user experience.

    Rate this question:

  • 27. 

    Which of the following statements is not true?

    • 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

    • Verification activities should not involve testers (reviews, inspections etc)

    • Test environments should be as similar to production environments as possible

    Correct Answer
    A. Verification activities should not involve testers (reviews, inspections etc)
    Explanation
    The statement "Verification activities should not involve testers (reviews, inspections etc)" is not true because verification activities, such as reviews and inspections, are often conducted by testers to ensure that the software meets the specified requirements and standards. Testers play a crucial role in identifying defects and ensuring the quality of the software through verification activities. Therefore, it is incorrect to say that verification activities should not involve testers.

    Rate this question:

  • 28. 

    Which of the following is NOT a type of non-functional test?

    • State-Transition

    • Usability

    • Performance

    • Security

    Correct Answer
    A. State-Transition
    Explanation
    See here for examples for examples of Functional and Non-Functional tests:
    http://reqtest.com/testing-blog/functional-vs-non-functional-testing/

    Rate this question:

  • 29. 

    Software testing activities should start

    • As soon as the code is written

    • During the design stage

    • When the requirements have been formally documented

    • As soon as possible in the development life cycle

    Correct Answer
    A. As soon as possible in the development life cycle
    Explanation
    Software testing activities should start as soon as possible in the development life cycle to ensure that any defects or issues in the code are identified and addressed early on. By starting testing early, potential problems can be identified and fixed before they have a chance to impact the overall quality of the software. This approach allows for more efficient and effective testing, as it allows for iterative testing and feedback throughout the development process. Additionally, starting testing early helps to minimize the cost and effort required to fix defects, as they are identified and addressed earlier in the development life cycle.

    Rate this question:

  • 30. 

    Coverage measurement

    • Is nothing to do with testing

    • Is a partial measure of test thoroughness

    • Branch coverage should be mandatory for all software

    • Can only be applied at unit or module testing, not at system testing

    Correct Answer
    A. Is a partial measure of test thoroughness
    Explanation
    The statement "Coverage measurement is a partial measure of test thoroughness" means that coverage measurement is a way to assess how much of the code or functionality has been tested. It indicates the extent to which the tests have covered the different parts or aspects of the software. However, it does not imply that coverage measurement is the only measure of test thoroughness or that it should be mandatory for all software. Additionally, coverage measurement can be applied at different levels of testing, including unit, module, and system testing.

    Rate this question:

  • 31. 

    A test design technique is

    • A process for selecting test cases

    • A process for determining expected outputs

    • A way to measure the quality of software

    • a way to measure in a test plan what has to be done

    Correct Answer
    A. A process for selecting test cases
    Explanation
    A test design technique refers to a systematic process that is used to select test cases. This technique helps in identifying the most appropriate test cases that need to be executed in order to effectively test the software. It involves various methods and strategies to ensure that the selected test cases cover all the relevant scenarios and functionalities of the software. By using a test design technique, testers can ensure that the testing process is efficient and thorough, leading to improved software quality.

    Rate this question:

  • 32. 

    If the pseudocode below were a programming language, how many tests are required to achieve 100% branch/decision coverage? If x=3 thenDisplay_messageX;If y=2 thenDisplay_messageY;ElseDisplay_messageZ;ElseDisplay_messageZ;

    • 1

    • 2

    • 3

    • 4

    Correct Answer
    A. 3
    Explanation
    There is a nested IF ELSE statement in this example

    Rate this question:

  • 33. 

    Which of the following tools would you use to detect a memory leak?

    • State analysis

    • Coverage analysis

    • Dynamic analysis

    • Memory analysis

    Correct Answer
    A. Dynamic analysis
    Explanation
    Dynamic analysis is the correct answer because it involves analyzing the program's behavior during runtime. It helps in detecting memory leaks by monitoring the allocation and deallocation of memory, tracking memory usage, and identifying any memory blocks that are not properly released. This analysis technique allows developers to identify and fix memory leaks by providing real-time information about memory allocation and deallocation patterns, helping to optimize memory usage and improve overall program performance.

    Rate this question:

  • 34. 

    If the pseudocode below were a programming language ,how many tests are required to achieve 100% statement coverage? If x=3 thenDisplay_messageX;If y=2 thenDisplay_messageY;ElseDisplay_messageZ;ElseDisplay_messageZ;

    • 1

    • 2

    • 3

    • 4

    Correct Answer
    A. 3
    Explanation
    There is a nested IF ELSE statement in this example

    Rate this question:

  • 35. 

    What is the main reason for testing software before releasing it?

    • To show that system will work after release

    • To decide when the software is of sufficient quality to release

    • To find as many bugs as possible before release

    • To give information for a risk based decision about release

    Correct Answer
    A. To give information for a risk based decision about release
    Explanation
    The main reason for testing software before releasing it is to give information for a risk-based decision about release. Testing helps identify any potential issues or bugs in the software, allowing the development team to assess the level of risk associated with releasing it. This information helps them make an informed decision on whether the software is ready for release or if further improvements are needed to ensure its quality and functionality.

    Rate this question:

  • 36. 

    Which of the following statements are true?

    • 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.

    Correct Answer
    A. Faults in requirements are the most expensive to fix.
    Explanation
    Faults in requirements are the most expensive to fix because they occur at the early stages of the software development process. When requirements are not properly defined or understood, it can lead to significant rework and changes in later stages of development. Fixing faults in requirements often involves revisiting the entire design and code, resulting in higher costs and time-consuming efforts. On the other hand, faults in code or designs can be relatively easier and less expensive to fix as they are identified and addressed during the implementation and testing phases.

    Rate this question:

  • 37. 

    Which of the following is not the integration strategy?

    • Design based

    • Big-bang

    • Bottom-up

    • Top-down

    Correct Answer
    A. Design based
    Explanation
    The integration strategy refers to the approach used to combine different components or subsystems of a system. Design based integration is not a commonly recognized integration strategy. The other options, such as big-bang, bottom-up, and top-down, are well-known integration strategies used in software development and system integration processes.

    Rate this question:

  • 38. 

    Which of the following is the component test standard?

    • IEEE 829

    • IEEE 610

    • BS7925-1

    • BS7925-2

    Correct Answer
    A. BS7925-2
    Explanation
    BS7925-2 is the correct answer because it is a recognized component test standard. IEEE 829 is a standard for software test documentation, IEEE 610 is a standard for software engineering, and BS7925-1 is a standard for software testing vocabulary. Therefore, BS7925-2 is the only option that specifically relates to component testing.

    Rate this question:

  • 39. 

    Which of the following is the odd one out?

    • White box

    • Glass box

    • Structural

    • Functional

    Correct Answer
    A. Glass box
    Explanation
    The odd one out is "glass box" because it is the only term that refers to a physical object, while the other options ("white box", "structural", "functional") are more abstract concepts or descriptions.

    Rate this question:

  • 40. 

    How many test cases are necessary to cover all the possible sequences of paths for the following program fragment?   if (Condition 1) then statement 1 else statement 2 endif if (Condition 2) then statement 3 endif

    • 1

    • 2

    • 3

    • 4

    Correct Answer
    A. 4
    Explanation
    The program fragment has two conditional statements. The first conditional statement has two possible outcomes, either statement 1 or statement 2. The second conditional statement also has two possible outcomes, either statement 3 or no statement. To cover all possible sequences of paths, we need to consider all combinations of outcomes from both conditional statements. Therefore, we would need 2 x 2 = 4 test cases.

    Rate this question:

Quiz Review Timeline (Updated): Mar 22, 2023 +

Our quizzes are rigorously reviewed, monitored and continuously updated by our expert board to maintain accuracy, relevance, and timeliness.

  • Current Version
  • Mar 22, 2023
    Quiz Edited by
    ProProfs Editorial Team
  • Jun 05, 2014
    Quiz Created by
    Devilbrand

Related Topics

Recent Quizzes

ISTQB- All Chapters Exam 17 ISTQB- All Chapters Exam 17
ISTQB- All Chapters Exam16 ISTQB- All Chapters Exam16
ISTQB- All Chapters Exam15 ISTQB- All Chapters Exam15
ISTQB Foundation Level Extension - Agile Tester. CTFL-AT: Chapter 2 ISTQB Foundation Level Extension - Agile Tester. CTFL-AT: Chapter 2
ISTQB- All Chapters Exam13 ISTQB- All Chapters Exam13
ISTQB- All Chapters Exam12 ISTQB- All Chapters Exam12
ISTQB- All Chapters Exam8 ISTQB- All Chapters Exam8
ISTQB- All Chapters Exam6 ISTQB- All Chapters Exam6
ISTQB-All Chapters Exam4 ISTQB-All Chapters Exam4
Back to Top Back to top
Advertisement
×

Wait!
Here's an interesting quiz for you.

We have other quizzes matching your interest.