Istqb1 - Fundamentals Of Testing
-
Deciding how much testing is enough should take into account:
- Level of Risk including Technical and Business product and project risk
- Project constraints such as time and budget
- Size of Testing Team
- Size of the Development Team
-
I, ii, iii are true and iv is false
-
I, iv are true and ii is false
-
I, ii are true and iii, iv are false
-
Ii, iii, iv are true and i is false
Test questions we went through during the sessions in all 3 groups
Quiz Preview
- 2.
Deliverables of test design phase include all the following except:
-
Test data
-
Test data plan
-
Test summary report
-
Test procedure plan
Correct Answer
A. Test summary reportExplanation
The deliverables of the test design phase typically include test data, test data plan, and test procedure plan. However, the test summary report is not a deliverable of the test design phase. The test summary report is usually generated at the end of the testing process to provide an overview of the testing activities, results, and any issues encountered. It summarizes the test execution and provides stakeholders with a comprehensive understanding of the testing performed.Rate this question:
-
- 3.
Typical defects that are easier to find in reviews than in dynamic testing are:
-
Deviations from standard
-
Requirement defects
-
Design defects
-
Insufficient maintainability and incorrect interface specifications
-
All of the above
Correct Answer
A. All of the aboveExplanation
The correct answer is "all of the above". This means that all of the mentioned defects (deviations from standard, requirement defects, design defects, insufficient maintainability, and incorrect interface specifications) are typically easier to find in reviews than in dynamic testing. Reviews allow for a thorough examination of the code, design, and requirements, making it easier to identify these types of defects compared to dynamic testing, which focuses on executing the software and observing its behavior.Rate this question:
-
- 4.
Which is not a testing principle?
-
Early testing
-
Defect clustering
-
Pesticide paradox
-
Exhaustive testing
Correct Answer
A. Exhaustive testingExplanation
Exhaustive testing is not a testing principle because it is not practical or feasible to test every possible combination or scenario in a system. It is time-consuming, expensive, and often unnecessary. Testing should be focused on identifying the most critical areas of the system and prioritizing the tests accordingly. Early testing, defect clustering, and the pesticide paradox are all recognized principles in software testing that emphasize the importance of testing early, focusing on high-risk areas, and regularly updating and diversifying test cases.Rate this question:
-
- 5.
A failure is:
-
Found in the SW, the result of an error
-
Departure from specified behaviour
-
An incorrect step, process or data definition in a computer program
-
A human action that produces an incorrect result
Correct Answer
A. Departure from specified behaviourExplanation
The correct answer is "departure from specified behaviour" because a failure refers to a situation where a system or component does not perform its intended function or does not conform to its specified behavior. It implies that there is a deviation or departure from the expected or desired behavior, which could be caused by errors, incorrect steps, or human actions. The other options mentioned, such as being found in the software or being a result of an error, are not comprehensive enough to encompass the concept of a failure.Rate this question:
-
- 6.
Which of the followings is not phase of the Fundamental Test Process?
-
Test planning and control
-
Test implementation and execution
-
Requirement analysis
-
Evaluating exit criteria and reportin
Correct Answer
A. Requirement analysisExplanation
Requirement analysis is not a phase of the Fundamental Test Process. The Fundamental Test Process consists of test planning and control, test implementation and execution, and evaluating exit criteria and reporting. Requirement analysis is a separate activity that is usually performed before the testing process begins. It involves understanding and analyzing the requirements of the system or software being developed in order to determine what needs to be tested.Rate this question:
-
- 7.
Test planning has which of the following major tasks? i. Determining the scope and risks, and identifying the objectives of testing ii. Determining the test approach (techniques, test items, coverage, identifying and interfacing the teams involved in testing, testware) iii. Reviewing the Test Basis (such as requirements, architecture, design, interface) iv. Determining the exit criteria
-
I, ii, iv are true and iii is false
-
I, iv are true and ii is false
-
I, ii are true and iii, iv are false
-
Ii, iii, iv are true and i is false
Correct Answer
A. I, ii, iv are true and iii is falseExplanation
The correct answer is i, ii, iv are true and iii is false. Test planning involves determining the scope and risks, identifying the objectives of testing, determining the test approach, reviewing the test basis, and determining the exit criteria. The statement iii is false because reviewing the test basis is a major task in test planning.Rate this question:
-
- 8.
Which of the following is not decided in the test-planning phase?
-
Schedules and deliverables
-
Hardware and software
-
Entry and exit criteria
-
Types of test cases
Correct Answer
A. Types of test casesExplanation
In the test-planning phase, various aspects of the testing process are determined, such as schedules, deliverables, entry and exit criteria. These factors help in organizing and structuring the testing activities. However, the types of test cases are not typically decided in the test-planning phase. Test cases are usually derived from the requirements and specifications of the system under test, and they are developed during the test design phase. Therefore, the types of test cases are not directly determined in the test-planning phase.Rate this question:
-
- 9.
Which is the best definition of complete testing:
-
You have discovered every bug in the program
-
You have tested every statement, branch, and combination of branches in the program
-
You have completed every test in the test plan
-
You have reached the scheduled ship date
Correct Answer
A. You have reached the scheduled ship dateExplanation
Complete testing refers to the process of testing a program thoroughly to ensure that it meets all the specified requirements and functions properly. It involves testing every statement, branch, and combination of branches in the program to identify any bugs or errors. However, reaching the scheduled ship date does not necessarily indicate complete testing, as it is possible to have missed some bugs or not covered all the required test cases. Therefore, the best definition of complete testing is when all the necessary tests have been conducted and the program meets the required quality standards, regardless of the ship date.Rate this question:
-
- 10.
Which of the following will be the best definition for Testing:
-
The goal/purpose of testing is to demonstrate that the program works
-
The purpose of testing is to demonstrate that the program is defect free
-
The purpose of testing is to demonstrate that the program does what it is supposed to do
-
Testing is executing Software for the purpose of finding defects
Correct Answer
A. Testing is executing Software for the purpose of finding defectsExplanation
The correct answer states that testing is executing software for the purpose of finding defects. This definition accurately captures the main objective of testing, which is to identify any flaws or errors in the software. By executing the software and actively searching for defects, testers can ensure that the program functions as intended and meets the required specifications. This definition emphasizes the importance of uncovering and addressing defects during the testing phase to improve the overall quality and reliability of the software.Rate this question:
-
- 11.
In prioritising what to test, the most important objective is to:
-
Find as many faults as possible
-
Test high risk areas
-
Obtain good test coverage
-
Test whatever is easiest to test
Correct Answer
A. Test high risk areasExplanation
In prioritizing what to test, the most important objective is to test high-risk areas. This is because high-risk areas are more likely to have critical defects that could impact the functionality or performance of the system. By focusing on these areas first, testers can identify and address potential issues that could have a significant impact on the quality of the software. Testing high-risk areas ensures that the most critical aspects of the system are thoroughly evaluated, reducing the risk of major failures in production.Rate this question:
-
- 12.
The most important thing about early test design is that it:
-
Makes test preparation easier
-
Means inspections are not required
-
Can prevent fault multiplication
-
Will find all faults
Correct Answer
A. Can prevent fault multiplicationExplanation
Early test design can prevent fault multiplication by identifying and addressing potential faults in the early stages of the development process. By designing tests early on, potential issues and faults can be identified and rectified before they have the chance to propagate and multiply throughout the system. This not only saves time and effort in the long run but also ensures that the final product is of higher quality and more reliable.Rate this question:
-
- 13.
Which of the following is a part of Test Closure Acitivities? i. Checking which planned deliverables have been delivered ii. Defect report analysis iii. Finalizing and archiving testware iv. Analyzing lessons
-
I, ii, iv are true and iii is false
-
I, ii, iii are true and iv is false
-
I, iii, iv are true and ii is false
-
All of above are true
Correct Answer
A. I, iii, iv are true and ii is falseExplanation
The correct answer is i, iii, iv are true and ii is false. In test closure activities, it is important to check which planned deliverables have been delivered to ensure that all the necessary items have been completed. Finalizing and archiving testware is also a part of test closure activities, as it involves organizing and storing all the test documentation and artifacts for future reference. Analyzing lessons is another important aspect of test closure activities, as it allows the team to identify areas for improvement and learn from the testing process. However, defect report analysis is not typically a part of test closure activities, as it is more related to defect management during the testing phase.Rate this question:
-
- 14.
Reviews, static analysis and dynamic testing have the same objectives:
-
Identifying defects
-
Fixing defects
-
A and b
-
None
Correct Answer
A. Identifying defectsExplanation
The objectives of reviews, static analysis, and dynamic testing are all focused on identifying defects. Reviews involve examining code or documentation to identify potential issues or errors. Static analysis involves analyzing code or software without executing it to find defects or vulnerabilities. Dynamic testing involves executing software and observing its behavior to uncover defects. Therefore, all three methods aim to identify defects rather than fixing them or any other objectives listed.Rate this question:
-
- 15.
Evaluating testability of the requirements and system are a part of which phase:
-
Test analysis and design
-
Test planning and control
-
Test implementation and execution
-
Evaluating exit criteria and reporting
Correct Answer
A. Test analysis and designExplanation
Evaluating testability of the requirements and system is a crucial step in the Test analysis and design phase. This phase involves analyzing the requirements and designing the test cases and test scenarios based on those requirements. Evaluating testability helps identify any potential issues or challenges in testing the system, ensuring that the testing process is efficient and effective. This phase sets the foundation for the entire testing process by determining what needs to be tested and how it will be tested.Rate this question:
-
- 16.
System testing should investigate:
-
Non-functional requirements only not functional requirements
-
Functional requirements only not non-functional requirements
-
Non-functional requirements and functional requirements
-
Non-functional requirements or functional requirements
Correct Answer
A. Non-functional requirements and functional requirementsExplanation
System testing should investigate both non-functional requirements and functional requirements. Non-functional requirements refer to the qualities and characteristics of the system, such as performance, reliability, security, usability, and maintainability. Functional requirements, on the other hand, specify the specific behavior and functionality of the system. By testing both types of requirements, system testers can ensure that the system not only meets the functional requirements but also performs well and meets the desired non-functional qualities.Rate this question:
-
- 17.
Which of the following should not normally be an objective for a test?
-
To find fault in the software
-
To assess whether the SW is ready for release
-
To demonstrate that the SW doesn't work
-
To prove that the SW is correct
Correct Answer
A. To prove that the SW is correctExplanation
The objective of a test is to identify faults or issues in the software, assess its readiness for release, or demonstrate that it doesn't work as expected. However, it is not the objective of a test to prove that the software is correct. Testing is meant to uncover errors and defects, and it is impossible to prove that software is completely error-free. Therefore, the objective of proving that the software is correct is not a realistic goal for testing.Rate this question:
-
- 18.
SW 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 cycleExplanation
SW testing activities should start as soon as possible in the development life cycle because it allows for early detection and resolution of defects, leading to better quality software. By starting testing early, potential issues can be identified and addressed before they become more difficult and costly to fix. Additionally, early testing helps to ensure that the software meets the specified requirements and is functioning as intended. This approach also helps in reducing the overall project risk and ensures that the software is delivered on time.Rate this question:
-
- 19.
When to stop testing?
-
Stop when scheduled time for testing expires
-
Stop if 75% of the pre-defined number of errors is detected
-
Stop when all the test cases execute with detecting few errors
-
None above
Correct Answer
A. Stop when scheduled time for testing expiresExplanation
The correct answer is to stop when the scheduled time for testing expires. This means that testing should be conducted within the allocated time frame, and once that time is up, the testing process should be concluded. This approach ensures that testing activities are efficiently managed and completed within the planned schedule.Rate this question:
-
- 20.
When do you stop testing?
-
When the specified number of faults are found
-
When the test completion criteria are met
-
When all high and medium priority tests are complete
-
When all statements have been executed
Correct Answer
A. When the test completion criteria are metExplanation
The correct answer is "When the test completion criteria are met." This means that testing should be stopped when the predetermined criteria for completing the testing process have been achieved. These criteria could include factors such as reaching a certain level of test coverage, achieving a desired level of reliability, or meeting specific performance targets. It is important to have clear test completion criteria in order to determine when testing can be considered finished and the product is ready for release.Rate this question:
-
- 21.
How much testing is enough?
-
This question is impossible to answer
-
This question is easy to answer
-
The answer depends on the risk for your industry, contract and special requirements
-
This answer depends on the maturity of your developers
Correct Answer
A. The answer depends on the risk for your industry, contract and special requirementsExplanation
The question of how much testing is enough cannot be answered definitively because it depends on various factors such as the level of risk in the industry, the contractual obligations, and any specific requirements that need to be met. Different industries may have different levels of risk tolerance, and contractual agreements may dictate certain testing standards. Additionally, special requirements or regulations may also impact the amount of testing required. Therefore, the answer to this question is subjective and dependent on these factors.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, 2023Quiz Edited by
ProProfs Editorial Team -
Oct 09, 2012Quiz Created by
Pkucerova
Back to top