ISTQB Sample Exam Questions – Testing Fundamentals
This practice exam is designed to test your knowledge of Testing Fundamentals.
ISTQB - Sample Exam 1 (Testing Fundamentals)
Start Congratulations - you have completed ISTQB - Sample Exam 1 (Testing Fundamentals). You scored %%SCORE%% out of %%TOTAL%%. Your performance has been rated as %%RATING%%Your answers are highlighted below.
| Question 1 |
I. Record keeping
II. System design
III. Evaluation scheduling
IV. Error reporting
| I, II &III | |
| II, III &IV | |
| I, III &IV | |
| I, II & IV |
| Question 2 |
| is that the tests are reviewed by experienced testers. | |
| is that there is some existing system against which test output may be checked. | |
| is that the tester can routinely identify the correct outcome of a test. | |
| is that the tester knows everything about the software under test. |
| Question 3 |
| The response time shall be less than one second for the specified design load. | |
| The system shall be user friendly. | |
| The system shall be built to be portable. | |
| The safety-critical parts of the system shall contain 0 faults. |
| Question 4 |
| test planning | |
| test recording | |
| test configuration | |
| test specification |
| Question 5 |
| Is not important | |
| Decreases as we move the product towards live use | |
| Increases as we move the product towards live use | |
| Is more expensive if found in requirements than functional design | |
| Can never be determined |
| Question 6 |
| A test environment comprised of stubs and drives needed to conduct a test | |
| A distance set of test activities collected into a manageable phase of a project | |
| A high level document describing the principles, approach and major objectives of the organization regarding testing | |
| A set of several test cases for a component or system under test |
| Question 7 |
| Quality is job one | |
| Work as designed | |
| Zero defects | |
| Conformance to requirements |
| Question 8 |
| to give information for a risk based decision about release | |
| to find as many bugs as possible before release | |
| to decide when the software is of sufficient quality to release | |
| to show that system will work after release |
| Question 9 |
| Analysis and design | |
| Planning and control | |
| None | |
| Test closure activities |
| Question 10 |
| a defect | |
| an error | |
| a mistake | |
| a fault | |
| a failure |
| Question 11 |
| a way to measure in a test plan what has to be done | |
| a way to measure the quality of software | |
| a process for selecting test cases | |
| a process for determining expected outputs |
| Question 12 |
| makes test preparation easier. | |
| will find all faults. | |
| means inspections are not required. | |
| can prevent fault multiplication. |
| Question 13 |
| found in the software; the result of an error. | |
| a human action that produces an incorrect result. | |
| departure from specified behaviour. | |
| an incorrect step, process or data definition in a computer program. |
| Question 14 |
| Stub | |
| Proxy | |
| Driver | |
| None of the above |
| Question 15 |
| expected outcomes are defined by the software’s behaviour | |
| 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 may include timing constraints such as response times | |
| expected outcomes should be predicted before a test is run |
| Question 16 |
| Only Project risks | |
| Project risks and Product risks | |
| Only Product risks | |
| Project risks or Product risks |
| Question 17 |
| This question is impossible to answer | |
| This answer depends on the maturity of your developers | |
| This question is easy to answer | |
| The answer depends on the risk for your industry, contract and special requirements |
| Question 18 |
| Smoke testing | |
| Regression testing | |
| Sanity testing | |
| System testing |
| Question 19 |
| Both b & c | |
| Usability testing | |
| Performance testing | |
| System testing |
| Question 20 |
| Test environments should be as similar to production environments as possible | |
| 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) |
| Question 21 |
| when the environment has changed | |
| when the project manager says | |
| every week | |
| as often as possible | |
| after the software has changed |
| Question 22 |
| only important in system testing | |
| only used in component testing | |
| most useful when specified in advance | |
| derived from the code | |
| never specified in advance |
| Question 23 |
| To demonstrate that the software doesn’t work. | |
| To find faults in the software. | |
| To assess whether the software is ready for release. | |
| To prove that the software is correct. |
| Question 24 |
| The code | |
| The existing system (For a bench mark) | |
| User manual | |
| Individual’s knowledge |
| Question 25 |
| Done by the Developer | |
| Done by an Entity Outside the Project’s sphere of influence | |
| Done By Management | |
| Done by the Test Engineers |
| Question 26 |
| time runs out. | |
| the users won’t find any serious faults. | |
| no more faults are found. | |
| the required level of confidence has been achieved. |
| Question 27 |
I. Ease of use
II. Capacity for incremental implementation
III. Capability of evolving with the needs of a project
IV. Inclusion of advanced tools
| II, III &IV | |
| I, II &IV | |
| I, III &IV | |
| I, II &III |
| Question 28 |
| We can run different tests in different environments. | |
| It is easier to manage testing in stages. | |
| The more stages we have, the better the testing. | |
| Each test stage has a different purpose. |
| Question 29 |
| After the system has gone live | |
| Only by end users | |
| After more formal techniques have been applied | |
| By inexperienced testers | |
| As the first approach to deriving test cases |
| Question 30 |
i. early test design can prevent fault multiplication
ii. faults found during early test design are more expensive to fix
iii. early test design can find faults
iv. early test design can cause changes to the requirements
v. early test design takes more effort
| iii & iv are true. i, ii & v are false | |
| i, iii & iv are true. Ii & v are false | |
| i & iii are true, ii, iv & v are false | |
| i, iii, iv & v are true, ii us false | |
| iii is true, I, ii, iv & v are false |
| Question 31 |
| testing a system feature using only the software required for that action | |
| testing to see where the system does not function properly | |
| testing for functions that should not exist | |
| testing a system feature using only the software required for that function | |
| testing quality attributes of the system including performance and usability |
| Question 32 |
| all the planned tests have been run | |
| it depends on the risks for the system being tested | |
| time has run out | |
| all faults have been fixed correctly | |
| both a) and c) |
| Question 33 |
| Spiral Model | |
| Water Fall Model | |
| RAD Model | |
| V-Model |
| Question 34 |
| re-testing is done by developers, regression testing is done by independent testers | |
| re-testing is running a test again; regression testing looks for unexpected side effects | |
| re-testing looks for unexpected side effects; regression testing is repeating those tests | |
| re-testing uses different environments, regression testing uses the same environment | |
| re-testing is done after faults are fixed; regression testing is done earlier |
| Question 35 |
| It reduces defect multiplication. | |
| It allows testers to become involved early in the project. | |
| It allows the identification of changes in user requirements. | |
| It facilitates timely set up of the test environment. |
| Question 36 |
| Pesticide paradox | |
| Defect clustering | |
| Exhaustive testing | |
| Early testing |
| Question 37 |
| It states that modules are tested against user requirements. | |
| It specifies the test techniques to be used. | |
| It includes the verification of designs. | |
| It only models the testing phase. |
| Question 38 |
| Lack of training | |
| Lack of technical documentation | |
| Lack of test tools on the market for developers | |
| Lack of Objectivity |
| Question 39 |
| the order they are thought of | |
| the most important tests first | |
| the easiest tests first(to give initial confidence) | |
| the most difficult tests first(to allow maximum time for fixing) |
| Question 40 |
| Test planning | |
| Test execution | |
| Test management | |
| Test design |
Once you are finished, click the button below. Any items you have not completed will be marked incorrect.
Get Results
|
List
|
Return
Shaded items are complete.
Return
| 1 | 2 | 3 | 4 | 5 |
| 6 | 7 | 8 | 9 | 10 |
| 11 | 12 | 13 | 14 | 15 |
| 16 | 17 | 18 | 19 | 20 |
| 21 | 22 | 23 | 24 | 25 |
| 26 | 27 | 28 | 29 | 30 |
| 31 | 32 | 33 | 34 | 35 |
| 36 | 37 | 38 | 39 | 40 |
| End |
You have completed
questions
question
Your score is
Correct
Wrong
Partial-Credit
You have not finished your quiz. If you leave this page, your progress will be lost.
All doneNeed more practice!Keep trying!Just Passed!Good work!Perfect!
