Testing Knowledge ISTQB 1

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 Indianou
I
Indianou
Community Contributor
Quizzes Created: 4 | Total Attempts: 2,209
| Attempts: 234
Quiz Flashcard
SettingsSettings
Please wait...
  • 1/100 Questions

    One Key reason why developers have difficulty testing their own work is :

    • Lack of technical documentation
    • Lack of test tools on the market for developers
    • Lack of training
    • Lack of Objectivity
Please wait...
ISTQB Quizzes & Trivia
About This Quiz

Explore the 'Testing knowledge ISTQB 1' quiz, designed to assess key competencies in software testing and quality assurance. Topics include boundary value testing, non-functional testing methods, and automation of regression tests, aligning with ISTQB standards.

Quiz Preview

  • 2. 

    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 requirements
    Explanation
    The question asks about the amount of testing that is enough, and the correct answer states that it depends on various factors such as the risk involved in the industry, the contract specifications, and any special requirements. This implies that the level of testing needed can vary based on these factors, suggesting that there is no fixed or universal answer to the question.

    Rate this question:

  • 3. 

    In case of Large Systems

    • Only few tests should be run

    • Testing should be on the basis of Risk

    • Only Good Test Cases should be executed

    • Test Cases written by good test engineers should be executed

    Correct Answer
    A. Testing should be on the basis of Risk
    Explanation
    In large systems, it is not feasible to run all possible tests due to time and resource constraints. Therefore, it is important to prioritize testing based on the level of risk associated with different components or functionalities of the system. By focusing on high-risk areas, the testing effort can be optimized to ensure that critical defects are identified and addressed. This approach allows for efficient allocation of resources and helps in delivering a reliable and robust system.

    Rate this question:

  • 4. 

    Which of the following is not part of performance testing?

    • Measuring response times

    • Recovery testing

    • Simulating many users

    • Generating many transactions

    Correct Answer
    A. Recovery testing
    Explanation
    Recovery testing is not part of performance testing. Performance testing focuses on measuring response times, simulating many users, and generating many transactions to evaluate the system's performance under different conditions. Recovery testing, on the other hand, is a type of testing that assesses how well the system recovers from failures or interruptions. While it is an important type of testing, it is not directly related to evaluating the performance of the system.

    Rate this question:

  • 5. 

    Non-functional system testing includes:

    • Testing to see where the system does not function correctly

    • Testing quality attributes of the system including performance and usability

    • Testing a system function using only the software required for that function

    • Testing for functions that should not exist

    Correct Answer
    A. Testing quality attributes of the system including performance and usability
    Explanation
    Non-functional system testing focuses on evaluating the quality attributes of the system, such as its performance and usability. This type of testing aims to assess how well the system performs under different conditions and how user-friendly it is. It involves testing aspects that are not directly related to the system's functional requirements, but rather its overall performance, reliability, scalability, and other non-functional aspects. By conducting non-functional system testing, organizations can ensure that their systems meet the desired quality standards and provide a satisfactory user experience.

    Rate this question:

  • 6. 

    What are the key features to be concentrated upon when doing a testing for world wide web sites

    • Interaction between html pages

    • Performance on the client side

    • Security aspects

    • All of the above

    Correct Answer
    A. All of the above
    Explanation
    When testing worldwide web sites, it is important to concentrate on the interaction between HTML pages, as this ensures smooth navigation and seamless user experience. Additionally, performance on the client side should be tested to ensure that the website loads quickly and functions efficiently. Lastly, security aspects should be thoroughly tested to protect against potential vulnerabilities or unauthorized access. Therefore, all of the mentioned features should be concentrated upon when testing worldwide web sites.

    Rate this question:

  • 7. 

    Boundary value testing

    • Is the same as equivalence partitioning tests

    • Test boundary conditions on, below and above the edges of input and output equivalence classes

    • Tests combinations of input circumstances

    • Is used in white box testing strategy

    Correct Answer
    A. Test boundary conditions on, below and above the edges of input and output equivalence classes
    Explanation
    Boundary value testing is a technique used to test the boundary conditions of input and output equivalence classes. It involves testing values that are on, below, and above the edges of these classes. By focusing on these boundary values, it helps to uncover any errors or issues that may occur at the boundaries. This technique is commonly used in white box testing strategy to ensure thorough test coverage.

    Rate this question:

  • 8. 

    Acceptance test cases are based on what?

    • Requirements

    • Design

    • Code

    • Decision table

    Correct Answer
    A. Requirements
    Explanation
    Acceptance test cases are based on requirements. This means that the test cases are designed to ensure that the system meets the specified requirements and functions as intended. By testing against the requirements, it helps to validate that the system is able to perform the necessary tasks and meet the expectations of the stakeholders. This is an important step in the software development lifecycle to ensure that the final product meets the desired functionality and quality standards.

    Rate this question:

  • 9. 

    One of the fields on a form contains a text box which accepts alphabets in lower or upper case. Indentify the invalid Equivalance class value.

    • CLASS

    • CLASS

    • CLass

    • CLa01ss

    Correct Answer
    A. CLa01ss
    Explanation
    The invalid equivalence class value in this case is "CLa01ss". This is because the form specifies that only alphabets in lower or upper case are accepted, but "CLa01ss" contains a number and is therefore not a valid input.

    Rate this question:

  • 10. 

    ________________ testing is performed at the developing organization’s site

    • Unit testing

    • Regression testing

    • Alpha testing

    • Integration testing

    Correct Answer
    A. Alpha testing
    Explanation
    Alpha testing is performed at the developing organization's site. It is a type of testing where a limited version of the software is made available to a group of users within the organization to evaluate its functionality, usability, and overall performance. This testing is done before the software is released to the external users or customers. It helps in identifying any potential issues or bugs in the software before it is deployed to a wider audience.

    Rate this question:

  • 11. 

    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 is commonly used in the automation of regression tests. This tool allows testers to record user actions and then play them back as test scripts. By doing so, it eliminates the need for manual execution of repetitive test cases, saving time and effort. Capture/Playback also ensures consistency in test execution and reduces the chances of human error. Therefore, it is a crucial tool in automating regression tests.

    Rate this question:

  • 12. 

    Pick the best definition of quality

    • Quality is job one

    • Zero defects

    • Conformance to requirements

    • Work as designed

    Correct Answer
    A. Conformance to requirements
    Explanation
    The best definition of quality is conformance to requirements. This means that a product or service is considered to have high quality if it meets all the specified requirements and standards. This definition emphasizes the importance of meeting customer expectations and delivering a product or service that fulfills its intended purpose. It implies that quality is not subjective, but rather objective and measurable based on the established requirements.

    Rate this question:

  • 13. 

    ‘X’ has given a data on a person age, which should be between 1 to 99. Using BVA which is the appropriate one

    • 0,1,2,99

    • 1, 99, 100, 98

    • 0, 1, 99, 100

    • –1, 0, 1, 99

    Correct Answer
    A. 0, 1, 99, 100
    Explanation
    Using Boundary Value Analysis (BVA), the appropriate values to test for a person's age, which should be between 1 to 99, would be the minimum value (0), the minimum valid value (1), the maximum valid value (99), and the maximum value (100). This is because BVA focuses on testing the boundaries and values just outside of them to ensure that the system handles them correctly. By including these specific values, we can verify if the system properly handles the age limits and any potential edge cases.

    Rate this question:

  • 14. 

    When should testing be stopped?

    • When all the planned tests have been run

    • When time has run out

    • When all faults have been fixed correctly

    • It depends on the risks for the system being tested

    Correct Answer
    A. It depends on the risks for the system being tested
    Explanation
    Testing should be stopped based on the risks associated with the system being tested. The decision to stop testing should not solely depend on whether all planned tests have been executed or if all faults have been fixed correctly. It is important to consider the risks involved in the system and evaluate if further testing is necessary to mitigate those risks. The decision to stop testing should be based on a comprehensive assessment of the system's quality and the potential impact of any remaining risks.

    Rate this question:

  • 15. 

    Beta testing is:

    • Performed by customers at their own site

    • Performed by customers at the software developer's site

    • Performed by an Independent Test Team

    • Performed as early as possible in the lifecycle

    Correct Answer
    A. Performed by customers at their own site
    Explanation
    Beta testing is performed by customers at their own site. This means that the customers who will be using the software in real-world conditions are given the opportunity to test it in their own environment. This allows for the identification of any issues or bugs that may arise during actual usage. By involving customers in the testing process, developers can gather valuable feedback and make necessary improvements before the software is released to the wider market.

    Rate this question:

  • 16. 

    Which of the following is not part of performance testing?

    • Measuring response times

    • Recovery testing

    • Simulating many users

    • Generating many transactions

    Correct Answer
    A. Recovery testing
    Explanation
    Recovery testing is not part of performance testing. Performance testing focuses on measuring response times, simulating many users, and generating many transactions to assess the system's performance under different loads. Recovery testing, on the other hand, is a type of testing that evaluates how well a system can recover from failures or disruptions. While both types of testing are important, recovery testing specifically assesses the system's ability to recover, rather than its performance under normal conditions.

    Rate this question:

  • 17. 

    Repeated Testing of an already tested program, after modification, to discover any defects introduced or uncovered as a result of the changes in the software being tested or in another related or unrelated software component:

    • ReTesting

    • Confirmation Testing

    • Regression Testing

    • Negative Testing

    Correct Answer
    A. Regression Testing
    Explanation
    Regression testing is the process of retesting a modified program to identify any defects that may have been introduced or uncovered as a result of the changes made in the software being tested or in other related or unrelated software components. It ensures that the modifications or updates do not have any adverse effects on the existing functionality of the software. Regression testing is important to ensure the overall stability and reliability of the software system.

    Rate this question:

  • 18. 

    During the software development process, at what point can the test process start?

    • When the code is complete.

    • When the design is complete.

    • When the software requirements have been approved.

    • When the first code module is ready for unit testing

    Correct Answer
    A. When the software requirements have been approved.
    Explanation
    The test process can start when the software requirements have been approved because it is essential to have a clear understanding of the desired functionality and behavior of the software before testing can begin. Once the requirements are approved, the testing team can start creating test plans, test cases, and test scripts based on those requirements. This ensures that the software is tested against the intended functionality and helps identify any deviations or defects early in the development process. Testing at this stage also helps in validating that the software meets the specified requirements and is ready for further testing and development phases.

    Rate this question:

  • 19. 

    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 of the code to ensure that they function correctly. It helps identify any errors or defects in the code's logic and ensures that all possible paths are tested. By testing both statements and branches, this technique provides comprehensive coverage and helps improve the overall quality and reliability of the component being tested.

    Rate this question:

  • 20. 

    Which of the following techniques is NOT a black box technique?

    • State transition testing

    • LCSAJ (Linear Code Sequence and Jump)

    • Syntax testing

    • Boundary value analysis

    Correct Answer
    A. LCSAJ (Linear Code Sequence and Jump)
    Explanation
    LCSAJ (Linear Code Sequence and Jump) is not a black box technique because it involves examining the internal structure of the code and requires knowledge of the code's implementation details. Black box testing techniques, on the other hand, focus on testing the functionality of a system without considering its internal workings. State transition testing, syntax testing, and boundary value analysis are all examples of black box techniques as they only require knowledge of the system's inputs and outputs, without considering the internal code structure.

    Rate this question:

  • 21. 

    Could reviews or inspections be considered part of testing?

    • No, because they apply to development documentation

    • No, because they are normally applied before testing

    • Yes, because both help detect faults and improve quality

    • Yes, because testing includes all non-constructive activities

    Correct Answer
    A. Yes, because both help detect faults and improve quality
    Explanation
    Reviews and inspections can be considered part of testing because they both help detect faults and improve the quality of the software being developed. Reviews and inspections involve examining the development documentation, code, or other artifacts to identify any potential issues or defects. This process helps in finding faults early in the development lifecycle, allowing for timely corrections and improvements. Therefore, reviews and inspections contribute to the overall testing effort by ensuring that the software meets the required quality standards.

    Rate this question:

  • 22. 

    The difference between re-testing and regression testing is:

    • Re-testing ensures the original fault has been removed; regression testing looks for unexpected side-effects

    • Re-testing looks for unexpected side-effects; regression testing ensures the original fault has been removed

    • Re-testing is done after faults are fixed; regression testing is done earlier

    • Re-testing is done by developers; regression testing is done by independent testers

    Correct Answer
    A. Re-testing ensures the original fault has been removed; regression testing looks for unexpected side-effects
    Explanation
    Re-testing is the process of testing an already tested functionality to ensure that the original fault has been fixed or removed. On the other hand, regression testing is performed to ensure that fixing a particular fault or adding new features has not caused any unintended side-effects in the existing functionality. Therefore, the given answer correctly explains that re-testing focuses on removing the original fault, while regression testing focuses on identifying unexpected side-effects.

    Rate this question:

  • 23. 

    Enough testing has been performed when:

    • Time runs out.

    • The required level of confidence has been achieved.

    • No more faults are found.

    • The users won?t find any serious faults.

    Correct Answer
    A. The required level of confidence has been achieved.
    Explanation
    Enough testing has been performed when the required level of confidence has been achieved. This means that the testing process has been thorough enough to ensure that the system or product meets the desired level of quality and reliability. It implies that all necessary tests have been conducted and the results have provided enough confidence in the system's performance, functionality, and stability. It does not necessarily mean that all faults have been found or that the testing process has reached its time limit.

    Rate this question:

  • 24. 

    Code Coverage is used as a measure of what ?

    • Defects

    • Trends analysis

    • Test Effectiveness

    • Time Spent Testing

    Correct Answer
    A. Test Effectiveness
    Explanation
    Code coverage is used as a measure of test effectiveness. It determines the extent to which the source code of a program has been tested by a set of test cases. A higher code coverage indicates that more parts of the code have been executed during testing, increasing the confidence in the quality of the software. Therefore, code coverage is a valuable metric in assessing the effectiveness of the testing process.

    Rate this question:

  • 25. 

    Functional system testing is:

    • Testing that the system functions with other systems

    • Testing that the components that comprise the system function together

    • Testing the end to end functionality of the system as a whole

    • Testing the system performs functions within specified response times

    Correct Answer
    A. Testing the end to end functionality of the system as a whole
    Explanation
    Functional system testing is the process of testing the end to end functionality of the system as a whole. This means that all the components and systems within the overall system are tested to ensure that they work together and perform their intended functions. It is a comprehensive testing approach that focuses on validating the system's functionality, including its integration with other systems and the fulfillment of specified response times.

    Rate this question:

  • 26. 

    A deviation from the specified or expected behavior that is visible to end-users is called:

    • An error

    • A fault

    • A failure

    • A defect

    Correct Answer
    A. A failure
    Explanation
    A deviation from the specified or expected behavior that is visible to end-users is called a failure. This means that the system or software is not functioning as intended and is not meeting the user's requirements or expectations. It could be a result of errors, faults, or defects in the system, but the key point is that it is noticeable and impacts the user's experience.

    Rate this question:

  • 27. 

    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 requirements
    Explanation
    System testing should investigate both non-functional requirements and functional requirements. Non-functional requirements refer to the aspects of the system that are not directly related to its functionality, such as performance, usability, reliability, and security. Functional requirements, on the other hand, define the specific tasks and functions that the system should be able to perform. By testing both types of requirements, system testing ensures that the system not only meets the functional requirements but also performs well in terms of non-functional aspects. This comprehensive testing approach helps to ensure the overall quality and effectiveness of the system.

    Rate this question:

  • 28. 

    Purpose of test design technique is

    • Identifying test conditions only, not Identifying test cases

    • Not Identifying test conditions, Identifying test cases only

    • Identifying test conditions and Identifying test cases

    • Identifying test conditions or Identifying test cases

    Correct Answer
    A. Identifying test conditions and Identifying test cases
    Explanation
    The purpose of a test design technique is to identify both test conditions and test cases. Test conditions refer to the specific aspects or features of the system that need to be tested, while test cases are the specific inputs, actions, or events that are used to verify those conditions. By using a test design technique, testers can systematically identify all the relevant test conditions and derive test cases that cover those conditions, ensuring comprehensive test coverage and effective testing.

    Rate this question:

  • 29. 

    Functional system testing is:

    • Testing that the system functions with other systems

    • Testing that the components that comprise the system function together

    • Testing the end to end functionality of the system as a whole

    • Testing the system performs functions within specified response times

    Correct Answer
    A. Testing the end to end functionality of the system as a whole
    Explanation
    Functional system testing is the process of testing the end-to-end functionality of the system as a whole. This means that all components and subsystems are tested together to ensure that they function properly and meet the specified requirements. It focuses on testing the system's behavior and functionality from the user's perspective, ensuring that it performs as expected and meets the desired outcomes. This type of testing helps identify any issues or defects that may arise when different components interact with each other, providing confidence in the system's overall functionality.

    Rate this question:

  • 30. 

    Regression testing should be performed: v) Every week w) After the software has changed x) As often as possible y) When the environment has changed z) When the project manager says

    • V & w are true, x, y & z are false

    • W, x & y are true, v & z are false

    • W & y are true, v, x & z are false

    • W is true, v, x, y & z are false

    Correct Answer
    A. W & y are true, v, x & z are false
    Explanation
    Regression testing should be performed after the software has changed and when the environment has changed. This is because regression testing is conducted to ensure that the changes made to the software do not introduce new bugs or issues and that the software still functions correctly in the updated environment. Performing regression testing every week or as often as possible may not be necessary or efficient, and relying solely on the project manager's decision may not be a reliable approach.

    Rate this question:

  • 31. 

    Expected results are:

    • Only important in system testing

    • Only used in component testing

    • Most useful when specified in advance

    • Derived from the code

    Correct Answer
    A. Most useful when specified in advance
    Explanation
    The expected results are most useful when specified in advance because having clearly defined expectations helps in planning and executing the testing process effectively. When the expected results are known beforehand, it becomes easier to design test cases, identify any deviations from the expected outcome, and assess the success of the testing. This also enables better communication and collaboration between testers, developers, and stakeholders, ensuring that everyone is aligned on the desired outcome.

    Rate this question:

  • 32. 

    Which of the following would NOT normally form part of a test plan?

    • Features to be tested

    • Incident reports

    • Risks

    • Schedule

    Correct Answer
    A. Incident reports
    Explanation
    Incident reports would not normally form part of a test plan because incident reports are typically used to document and track issues or problems that occur during testing or after the software has been released. They are not typically included in the initial test plan, which focuses on outlining the scope, objectives, approach, and schedule for the testing activities. Incident reports are more relevant to the defect tracking and resolution process rather than the planning phase of testing.

    Rate this question:

  • 33. 

    Incorrect form of Logic coverage is:

    • Statement Coverage

    • Pole Coverage

    • Condition Coverage

    • Path Coverage

    Correct Answer
    A. Pole Coverage
  • 34. 

    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 areas.
    Explanation
    The most important objective in prioritizing what to test is to focus on high-risk areas. This is because high-risk areas are more likely to contain critical defects that could have a significant impact on the system or business. By testing these areas first, it allows for early detection and mitigation of potential risks, ensuring that the most critical issues are addressed promptly. This approach helps in optimizing testing efforts and resources, ensuring that the testing process is effective and efficient in identifying and resolving potential problems.

    Rate this question:

  • 35. 

    Fault Masking is

    • Error condition hiding another error condition

    • Creating a test case which does not reveal a fault

    • Masking a fault by developer

    • Masking a fault by a tester

    Correct Answer
    A. Error condition hiding another error condition
    Explanation
    Fault masking refers to the situation where one error condition is hidden or overshadowed by another error condition. This means that when one error occurs, it prevents the detection or visibility of another error that may have occurred simultaneously or subsequently. In other words, the presence of one error condition masks or conceals the presence of another error condition, making it difficult to identify and address the underlying issues. This can lead to challenges in troubleshooting and resolving the errors effectively.

    Rate this question:

  • 36. 

    Given the following types of tool, which tools would typically be used by developers, and which by an independent system test team? i. Static analysis ii. Performance testing iii. Test management iv. Dynamic analysis

    • Developers would typically use i and iv; test team ii and iii

    • Developers would typically use i and iii; test team ii and iv

    • Developers would typically use ii and iv; test team i and iii

    • Developers would typically use i, iii and iv; test team ii

    Correct Answer
    A. Developers would typically use i and iv; test team ii and iii
    Explanation
    Developers typically use static analysis (i) and dynamic analysis (iv) tools to identify and fix code issues and vulnerabilities during the development process. These tools help developers ensure the quality and reliability of their code. On the other hand, an independent system test team typically uses performance testing (ii) tools to evaluate the system's performance under different conditions and test management (iii) tools to plan, organize, and track the testing process. This division of tool usage allows for a comprehensive approach to software development and testing, with each team focusing on their specific areas of expertise.

    Rate this question:

  • 37. 

    The selection of test cases for regression testing

    • Requires knowledge on the bug fixes and how it affect the system

    • Includes the area of frequent defects

    • Includes the area which has undergone many/recent code changes

    • All of the above

    Correct Answer
    A. All of the above
    Explanation
    The selection of test cases for regression testing requires knowledge on the bug fixes and how they affect the system because it helps in identifying the areas that need to be retested to ensure that the bug fixes have not introduced new issues. It also includes the area of frequent defects as these areas are more likely to have recurring issues that need to be tested. Additionally, it includes the area which has undergone many/recent code changes as these areas are more prone to introducing new bugs due to the changes made. Therefore, all of the above factors are considered when selecting test cases for regression testing.

    Rate this question:

  • 38. 

    Bug life cycle

    • Open, Assigned, Fixed, Closed

    • Open, Fixed, Assigned, Closed

    • Assigned, Open, Closed, Fixed

    • Assigned, Open, Fixed, Closed

    Correct Answer
    A. Open, Assigned, Fixed, Closed
    Explanation
    The correct answer is "Open, Assigned, Fixed, Closed." In the bug life cycle, the first step is to identify and report the bug, which is represented by the "Open" status. Once the bug is acknowledged and assigned to a developer, it moves to the "Assigned" status. The developer then works on fixing the bug, which leads to the "Fixed" status. Finally, after the bug is verified and confirmed to be resolved, it is marked as "Closed." This sequence represents the typical flow of a bug through its life cycle.

    Rate this question:

  • 39. 

    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 Design
    Explanation
    The correct answer is Test Analysis and Design. Evaluating the testability of the requirements and system is a crucial step in the Test Analysis and Design phase. This phase involves analyzing the requirements, identifying test conditions, designing test cases, and preparing the test environment. By evaluating the testability, testers can ensure that the requirements are clear, achievable, and measurable, and that the system is ready for testing. This helps in creating effective test cases and ensuring that the testing process is well-planned and controlled.

    Rate this question:

  • 40. 

    Which of the following statements about reviews is true?

    • Reviews cannot be performed on user requirements specifications.

    • Reviews are the least effective way of testing code.

    • Reviews are unlikely to find faults in test plans.

    • Reviews should be performed on specifications, code, and test plans.

    Correct Answer
    A. Reviews should be performed on specifications, code, and test plans.
    Explanation
    Reviews should be performed on specifications, code, and test plans. This statement is true because reviews are a critical part of the software development process and can help identify defects and improve the quality of the deliverables. By conducting reviews on specifications, code, and test plans, potential issues can be identified early on, leading to better overall quality and reducing the likelihood of costly errors. Reviews provide an opportunity for stakeholders to provide feedback, ensure compliance with standards, and verify that the deliverables meet the intended requirements.

    Rate this question:

  • 41. 

    What are the 2 major components taken into consideration with risk analysis?

    • The probability the negative event will occur

    • The potential loss or impact associated with the event

    • Both a and b

    • Neither a nor b

    Correct Answer
    A. Both a and b
    Explanation
    Risk analysis involves assessing the probability of a negative event occurring and evaluating the potential loss or impact associated with that event. By considering both factors, a comprehensive understanding of the risks involved can be obtained. Therefore, the correct answer is "Both a and b."

    Rate this question:

  • 42. 

    Use cases can be performed to test

    • Performance testing

    • Unit testing

    • Business scenarios

    • Static testing

    Correct Answer
    A. Business scenarios
    Explanation
    Use cases can be performed to test business scenarios. Use cases are a way of representing interactions between users and a system, and they are commonly used in software development to describe the expected behavior of a system in real-world situations. By testing business scenarios through use cases, developers can ensure that the system functions correctly and meets the requirements of the business. This type of testing helps identify any issues or gaps in the system's functionality and ensures that it aligns with the intended business processes.

    Rate this question:

  • 43. 

    Error guessing is best used:

    • After more formal techniques have been applied

    • As the first approach to deriving test cases

    • By inexperienced testers

    • After the system has gone live

    Correct Answer
    A. After more formal techniques have been applied
    Explanation
    Error guessing is best used after more formal techniques have been applied because formal techniques such as requirement analysis, test planning, and test design provide a structured approach to identifying and designing test cases based on specified requirements. Once these formal techniques have been applied, error guessing can be used to uncover additional defects or errors that may not have been identified through the formal techniques. This approach allows testers to use their experience and intuition to think creatively and anticipate potential issues that may have been missed.

    Rate this question:

  • 44. 

    We split testing into distinct stages primarily because:

    • Each test stage has a different purpose.

    • It is easier to manage testing in stages.

    • We can run different tests in different environments.

    • The more stages we have, the better the testing.

    Correct Answer
    A. Each test stage has a different purpose.
    Explanation
    We split testing into distinct stages primarily because each test stage has a different purpose. This allows us to focus on specific objectives and goals at each stage, ensuring that all aspects of the software or system are thoroughly tested. By dividing testing into stages, we can also allocate resources and manage the testing process more effectively. Additionally, it enables us to identify and address issues at different levels of complexity, leading to better overall testing and quality assurance.

    Rate this question:

  • 45. 

    What can static analysis NOT find?

    • The use of a variable before it has been defined

    • Unreachable (?dead?) code

    • Memory leaks

    • Array bound violations

    Correct Answer
    A. Memory leaks
    Explanation
    Static analysis is a method used to analyze code without actually executing it. It can identify various issues such as the use of a variable before it has been defined, unreachable code, and array bound violations. However, static analysis is unable to find memory leaks. Memory leaks occur when a program fails to release memory that is no longer needed, leading to a gradual loss of available memory. Since static analysis does not involve runtime execution, it cannot detect such runtime-specific issues.

    Rate this question:

  • 46. 

    Complete statement and branch coverage means:

    • That you have tested every statement in the program.

    • That you have tested every statement and every branch in the program.

    • That you have tested every IF statement in the program.

    • That you have tested every combination of values of IF statements in the program

    Correct Answer
    A. That you have tested every statement and every branch in the program.
    Explanation
    Complete statement and branch coverage means that you have tested every statement and every branch in the program. This includes testing all the individual statements in the program as well as testing all the different paths or branches that the program can take based on different conditions or decisions. By achieving complete statement and branch coverage, you can ensure that every part of the program has been executed and tested, increasing the likelihood of identifying any potential errors or bugs.

    Rate this question:

  • 47. 

    Which is not a testing principle

    • Early testing

    • Defect clustering

    • Pesticide paradox

    • Exhaustive testing

    Correct Answer
    A. Exhaustive testing
    Explanation
    Exhaustive testing is not a testing principle because it is practically impossible to test all possible combinations and inputs of a system. It is not feasible to test every single scenario due to time, resources, and budget constraints. Instead, testing efforts should be focused on critical areas and high-risk scenarios to ensure maximum coverage and effectiveness.

    Rate this question:

  • 48. 

    Which is the non-functional testing

    • Performance testing

    • Unit testing

    • Regression testing

    • Sanity testing

    Correct Answer
    A. Performance testing
    Explanation
    Performance testing is a type of non-functional testing that focuses on evaluating the system's performance under specific conditions. It involves measuring various aspects of the system's performance, such as response time, throughput, scalability, and resource usage. The purpose of performance testing is to identify any performance bottlenecks or issues that may affect the system's ability to handle a specific workload or user load. This type of testing helps ensure that the system meets the desired performance requirements and provides a satisfactory user experience.

    Rate this question:

  • 49. 

    Which of the following is NOT a reasonable test objective:

    • To find faults in the software

    • To prove that the software has no faults

    • To give confidence in the software

    • To find performance problems

    Correct Answer
    A. To prove that the software has no faults
    Explanation
    The objective of proving that the software has no faults is not a reasonable test objective because it is practically impossible to prove that a software has no faults. Testing can only help in identifying and finding faults in the software, but it cannot guarantee that there are no faults present. Therefore, the objective of proving the software's faultlessness is not achievable and not a reasonable test objective.

    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
  • Apr 27, 2012
    Quiz Created by
    Indianou

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- All Chapters Exam13 ISTQB- All Chapters Exam13
ISTQB- All Chapters Exam12 ISTQB- All Chapters Exam12
ISTQB- All Chapters Exam8 ISTQB- All Chapters Exam8
Back to Top Back to top
Advertisement
×

Wait!
Here's an interesting quiz for you.

We have other quizzes matching your interest.