ISTQB- Module2 - Exam1 - Quiz & Trivia

1. Beta Testing is:

Performed by customers at their own site

Performed by developers at their developer site

Performed by an independent team

Useful to test bespoke software

Performed as early as possible in the life cycle

Beta testing is a type of testing performed by customers at their own site. This means that the customers who will be using the software in the real world environment are given the opportunity to test it before its official release. This allows for real-world feedback and helps identify any potential issues or bugs that may not have been detected during earlier stages of testing. Beta testing is usually done towards the end of the software development life cycle to ensure that any remaining issues are addressed before the final release.

Explanation

Beta testing is a type of testing performed by customers at their own site. This means that the customers who will be using the software in the real world environment are given the opportunity to test it before its official release. This allows for real-world feedback and helps identify any potential issues or bugs that may not have been detected during earlier stages of testing. Beta testing is usually done towards the end of the software development life cycle to ensure that any remaining issues are addressed before the final release.

2. Non functional system testing includes:

Testing to see where the system does not function properly

Testing quality attribute of the system including Performance & Usability

Testing a system feature using only the software required for that action

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

Testing for the functions that should not exists

Non functional system testing involves testing the quality attributes of the system, such as its performance and usability. This type of testing focuses on evaluating how well the system performs under different conditions and how user-friendly it is. It helps identify any issues related to the system's performance, responsiveness, scalability, and user experience. By conducting non functional system testing, organizations can ensure that their system meets the required quality standards and provides a satisfactory user experience.

Explanation

Non functional system testing involves testing the quality attributes of the system, such as its performance and usability. This type of testing focuses on evaluating how well the system performs under different conditions and how user-friendly it is. It helps identify any issues related to the system's performance, responsiveness, scalability, and user experience. By conducting non functional system testing, organizations can ensure that their system meets the required quality standards and provides a satisfactory user experience.

3. Testing where in we subject the target of the test , to varying workloads to measure and evaluate the performance behaviors and ability of the target and of the test to continue to function properly under these different workloads.

Load Testing

Integration Testing

System Testing

Usability Testing

Load testing is a type of testing where the target of the test is subjected to varying workloads in order to measure and evaluate its performance behaviors and ability to function properly under different workloads. This type of testing helps to determine how well a system or application can handle a large number of users or transactions, and identify any performance bottlenecks or issues that may arise under heavy loads. Load testing is important for ensuring that a system can handle the expected workload and perform efficiently without any degradation in performance.

Explanation

Load testing is a type of testing where the target of the test is subjected to varying workloads in order to measure and evaluate its performance behaviors and ability to function properly under different workloads. This type of testing helps to determine how well a system or application can handle a large number of users or transactions, and identify any performance bottlenecks or issues that may arise under heavy loads. Load testing is important for ensuring that a system can handle the expected workload and perform efficiently without any degradation in performance.

4. Testing activity which is performed to expose defects in the interfaces and in the interaction between integrated components is :

System Level Testing

Integration Level Testing

Unit Level Testing

Component Testing

Integration Level Testing is the testing activity that is performed to expose defects in the interfaces and in the interaction between integrated components. This type of testing focuses on testing the integration between different components or modules of a system to ensure that they work together correctly and as expected. It helps to identify any issues or defects that may arise when different components are integrated and ensures that the system functions as a whole.

Explanation

Integration Level Testing is the testing activity that is performed to expose defects in the interfaces and in the interaction between integrated components. This type of testing focuses on testing the integration between different components or modules of a system to ensure that they work together correctly and as expected. It helps to identify any issues or defects that may arise when different components are integrated and ensures that the system functions as a whole.

5. Which is the non-functional testing

Performance testing

Unit testing

Regression testing

Sanity testing

Performance testing is a type of non-functional testing that evaluates the system's ability to handle a specific workload and measure its response time, scalability, and stability under different conditions. It aims to identify any performance issues such as slow response times, high resource usage, or bottlenecks in the system. Unlike unit testing, which focuses on testing individual components, performance testing assesses the overall system performance. Regression testing and sanity testing are functional testing techniques that focus on verifying the system's functionality.

Explanation

Performance testing is a type of non-functional testing that evaluates the system's ability to handle a specific workload and measure its response time, scalability, and stability under different conditions. It aims to identify any performance issues such as slow response times, high resource usage, or bottlenecks in the system. Unlike unit testing, which focuses on testing individual components, performance testing assesses the overall system performance. Regression testing and sanity testing are functional testing techniques that focus on verifying the system's functionality.

6. What is beta testing?

Testing performed by potential customers at the developers location

Testing performed by potential customers at their own locations

Testing performed by product developers at the customer's location

Testing performed by product developers at their own locations

Beta testing is a type of testing where potential customers use the product at their own locations. This allows developers to gather feedback and identify any issues or bugs that may arise in real-world scenarios. By involving potential customers in the testing process, developers can gain valuable insights into the product's usability, performance, and overall user experience. This helps in refining and improving the product before its official release.

Explanation

Beta testing is a type of testing where potential customers use the product at their own locations. This allows developers to gather feedback and identify any issues or bugs that may arise in real-world scenarios. By involving potential customers in the testing process, developers can gain valuable insights into the product's usability, performance, and overall user experience. This helps in refining and improving the product before its official release.

7. Which of the following are examples of iterative development models?(i) V-model(ii) Rapid Application Development model(iii) Waterfall model(iv) Agile development model

(i) and (ii)

(ii) and (iii)

(ii) and (iv)

(iii) and (iv)

The other two models are sequential models

Explanation

The other two models are sequential models

8. Contract and regulation testing is a part of

System testing

Acceptance testing

Integration testing

Smoke testing

Contract and regulation testing is a part of acceptance testing because acceptance testing focuses on ensuring that a system meets the requirements and expectations of the end-users or stakeholders. Contract and regulation testing specifically involves validating whether the system complies with any contractual agreements or regulatory standards that it needs to adhere to. This type of testing ensures that the system is legally compliant and meets all the necessary obligations set forth by contracts and regulations.

Explanation

Contract and regulation testing is a part of acceptance testing because acceptance testing focuses on ensuring that a system meets the requirements and expectations of the end-users or stakeholders. Contract and regulation testing specifically involves validating whether the system complies with any contractual agreements or regulatory standards that it needs to adhere to. This type of testing ensures that the system is legally compliant and meets all the necessary obligations set forth by contracts and regulations.

9. Which of the following statements are true?(i) For every development activity there is a corresponding testing activity.(ii) Each test level has the same test objectives.(iii) The analysis and design of tests for a given test level should begin after the corresponding development activity.(iv)Testers should be involved in reviewing documents as soon as drafts are available in the development life cycle.

(i) and (ii)

(iii) and (iv)

(ii) and (iii)

(i) and (iv)

Option (ii) is incorrect: each test level has a different objective.
Option (iii) is also incorrect: test analysis and design should start once the documentation has been completed.

Explanation

Option (ii) is incorrect: each test level has a different objective.
Option (iii) is also incorrect: test analysis and design should start once the documentation has been completed.

10. Link Testing is also called as :

Component Integration testing

Component System Testing

Component Sub System Testing

Maintenance testing

Component Integration testing is the correct answer because link testing refers to the testing of the connections or links between different components or modules of a system. It ensures that the components are integrated correctly and work together as expected. This type of testing focuses on verifying the interactions and communication between components, identifying any issues or errors that may arise during integration, and ensuring the overall functionality and reliability of the system.

Explanation

Component Integration testing is the correct answer because link testing refers to the testing of the connections or links between different components or modules of a system. It ensures that the components are integrated correctly and work together as expected. This type of testing focuses on verifying the interactions and communication between components, identifying any issues or errors that may arise during integration, and ensuring the overall functionality and reliability of the system.

11. Which of the following is a benefit of test independence?

It does not require familiarity with the code

It is cheaper than using developers to test their own code

It avoids author bias in defining effective tests

Testers are better at finding defects than developers

Test independence is a benefit because it avoids author bias in defining effective tests. When the author of a code is responsible for testing it, they may unintentionally overlook certain areas or make assumptions about how the code should behave. By having independent testers, who are not involved in the development process, define and execute tests, the risk of bias is reduced. This helps in identifying potential defects or issues that may have been missed by the author.

Explanation

Test independence is a benefit because it avoids author bias in defining effective tests. When the author of a code is responsible for testing it, they may unintentionally overlook certain areas or make assumptions about how the code should behave. By having independent testers, who are not involved in the development process, define and execute tests, the risk of bias is reduced. This helps in identifying potential defects or issues that may have been missed by the author.

12. Which of the following is not part of Performance Testing?

Measuring response time

Measuring transaction rate

Recovery Testing

Simulating many users

Generating many transactions

Recovery Testing is not part of Performance Testing because it focuses on testing the system's ability to recover from failures or crashes, rather than evaluating its performance under normal conditions. Performance Testing, on the other hand, involves measuring response time, transaction rate, simulating many users, and generating many transactions to assess the system's speed, scalability, and stability.

Explanation

Recovery Testing is not part of Performance Testing because it focuses on testing the system's ability to recover from failures or crashes, rather than evaluating its performance under normal conditions. Performance Testing, on the other hand, involves measuring response time, transaction rate, simulating many users, and generating many transactions to assess the system's speed, scalability, and stability.

13. PDCA is known as

Plan, Do, Check, Act

Plan, Do, Correct, Act

Plan, Debug, Check, Act

Plan, Do, Check, Accept

PDCA is a four-step management method used for continuous improvement. The first step is to "Plan" by setting goals and creating a plan to achieve them. The second step is to "Do" by implementing the plan and carrying out the tasks. The third step is to "Check" or evaluate the results and compare them to the desired goals. Finally, the fourth step is to "Act" by making any necessary adjustments or improvements based on the evaluation. This cycle is repeated continuously to drive ongoing improvement.

Explanation

PDCA is a four-step management method used for continuous improvement. The first step is to "Plan" by setting goals and creating a plan to achieve them. The second step is to "Do" by implementing the plan and carrying out the tasks. The third step is to "Check" or evaluate the results and compare them to the desired goals. Finally, the fourth step is to "Act" by making any necessary adjustments or improvements based on the evaluation. This cycle is repeated continuously to drive ongoing improvement.

14. Expected results are:

Only important in System Testing

Only used in Component Testing

Never specified in advanced

Most useful when specified in advanced

Derived from the code

This answer suggests that specifying expected results in advance is the most useful approach. This implies that having a clear understanding of what the expected outcome should be before conducting testing can help guide the testing process and ensure that the system or component being tested is functioning correctly. By specifying the expected results in advance, it becomes easier to identify any deviations from the expected behavior and address them accordingly.

Explanation

This answer suggests that specifying expected results in advance is the most useful approach. This implies that having a clear understanding of what the expected outcome should be before conducting testing can help guide the testing process and ensure that the system or component being tested is functioning correctly. By specifying the expected results in advance, it becomes easier to identify any deviations from the expected behavior and address them accordingly.

15. Integration Testing has the following characteristics:(i). It can be done in incremental manner(ii). It always done after system testing(iii). It includes functional test(iv). It includes non functional test

(i), (ii) & (iii) are correct

(i) is correct

(i), (iii) & (iv) are correct

(i), (ii) & (iv) are correct

Integration testing can be done in an incremental manner, meaning that it can be conducted by gradually adding components or modules to the system being tested. It also includes functional testing, which focuses on testing the functionality of the integrated components. Additionally, integration testing includes non-functional testing, which aims to evaluate the performance, security, and other non-functional aspects of the integrated system. Therefore, the correct answer is (i), (iii), and (iv) are correct.

Explanation

Integration testing can be done in an incremental manner, meaning that it can be conducted by gradually adding components or modules to the system being tested. It also includes functional testing, which focuses on testing the functionality of the integrated components. Additionally, integration testing includes non-functional testing, which aims to evaluate the performance, security, and other non-functional aspects of the integrated system. Therefore, the correct answer is (i), (iii), and (iv) are correct.

16. The ___________ Testing will be performed by the people at client own locations.

Alpha testing

Field testing

Performance testing

System testing

Field testing is the correct answer because it involves testing a product or system in real-world conditions at the client's own locations. This type of testing helps to identify any issues or problems that may arise when the product is used in its intended environment. Alpha testing, performance testing, and system testing are different types of testing that may be performed during the development process, but they do not specifically involve testing at the client's own locations.

Explanation

Field testing is the correct answer because it involves testing a product or system in real-world conditions at the client's own locations. This type of testing helps to identify any issues or problems that may arise when the product is used in its intended environment. Alpha testing, performance testing, and system testing are different types of testing that may be performed during the development process, but they do not specifically involve testing at the client's own locations.

17. Which of the following is a non-functional requirement?

The system will enable users to buy books

The system will allow users to return books

The system will ensure security of the customer details

The system will allow up to 100 users to log in at the same time

The other options are functional requirements. Note that security is regarded as a functional requirement in this syllabus

Explanation

The other options are functional requirements. Note that security is regarded as a functional requirement in this syllabus

18. Error guessing is best used:

As the first approach to deriving test cases

After more formal techniques have been applied

By inexperienced testers

After the system has gone live

Only by end users

Error guessing is best used after more formal techniques have been applied. This means that error guessing should not be the primary or initial approach to deriving test cases. Instead, it should be used as a supplementary technique after other more structured and systematic testing methods have been employed. This is because error guessing relies on the tester's intuition, experience, and knowledge of potential errors in the system, which may not be comprehensive or reliable without the foundation provided by formal techniques. Therefore, error guessing is most effective when used in conjunction with other testing approaches.

Explanation

Error guessing is best used after more formal techniques have been applied. This means that error guessing should not be the primary or initial approach to deriving test cases. Instead, it should be used as a supplementary technique after other more structured and systematic testing methods have been employed. This is because error guessing relies on the tester's intuition, experience, and knowledge of potential errors in the system, which may not be comprehensive or reliable without the foundation provided by formal techniques. Therefore, error guessing is most effective when used in conjunction with other testing approaches.

19. Which of the following is true about the V-model?

It has the same steps as the waterfall model for software development

It is referred to as a cyclical model for software development

It enables the production of a working version of the system as early as possible

It enables test planning to start as early as possible

The V-model enables test planning to start as early as possible. In the V-model, the testing activities are integrated throughout the development process, starting from the initial stages such as requirements gathering and design. This early involvement of testing ensures that potential issues and defects are identified and addressed early on, reducing the overall cost and effort required for testing. By incorporating testing from the beginning, the V-model helps in delivering a high-quality product by detecting and resolving issues at an early stage.

Explanation

The V-model enables test planning to start as early as possible. In the V-model, the testing activities are integrated throughout the development process, starting from the initial stages such as requirements gathering and design. This early involvement of testing ensures that potential issues and defects are identified and addressed early on, reducing the overall cost and effort required for testing. By incorporating testing from the beginning, the V-model helps in delivering a high-quality product by detecting and resolving issues at an early stage.

20. Which test investigates both functional and non-functional system requirements?

Alpha testing

System testing

Acceptance testing

Confirmation testing

System testing is a type of testing that investigates both functional and non-functional system requirements. It is performed on a complete, integrated system to evaluate its compliance with the specified requirements. This testing phase verifies that the system meets the intended purpose and performs as expected in different scenarios. It focuses on testing the system as a whole rather than individual components or units. System testing helps identify any defects or issues that may arise due to the interaction between various components of the system.

Explanation

System testing is a type of testing that investigates both functional and non-functional system requirements. It is performed on a complete, integrated system to evaluate its compliance with the specified requirements. This testing phase verifies that the system meets the intended purpose and performs as expected in different scenarios. It focuses on testing the system as a whole rather than individual components or units. System testing helps identify any defects or issues that may arise due to the interaction between various components of the system.

21. Which testing is used to verify that the system can perform properly when internal program or system limitations have been exceeded

Stress Testing

Load Testing

Performance Testing

Volume testing

Stress testing is used to verify that the system can perform properly when internal program or system limitations have been exceeded. This type of testing is done by subjecting the system to extreme conditions such as high user loads, large amounts of data, or limited system resources to assess its stability and robustness. It helps identify any weaknesses or vulnerabilities in the system when it is pushed beyond its normal operating limits, ensuring that it can handle unexpected or excessive demands without crashing or malfunctioning.

Explanation

Stress testing is used to verify that the system can perform properly when internal program or system limitations have been exceeded. This type of testing is done by subjecting the system to extreme conditions such as high user loads, large amounts of data, or limited system resources to assess its stability and robustness. It helps identify any weaknesses or vulnerabilities in the system when it is pushed beyond its normal operating limits, ensuring that it can handle unexpected or excessive demands without crashing or malfunctioning.

22. Component Testing is also called as :-i. Unit Testingii. Program Testingiii. Module Testingiv. System Component Testing

I,ii,iii are true and iv is false

I,ii,iii,iv are false

I,ii,iv are true and iii is false

All of above is true

Component Testing is also known as Unit Testing, Program Testing, and Module Testing. This means that options i, ii, and iii are true. However, option iv, which states that Component Testing is also called System Component Testing, is false. Therefore, the correct answer is i, ii, iii are true and iv is false.

Explanation

Component Testing is also known as Unit Testing, Program Testing, and Module Testing. This means that options i, ii, and iii are true. However, option iv, which states that Component Testing is also called System Component Testing, is false. Therefore, the correct answer is i, ii, iii are true and iv is false.

23. Which of the following is the standard for the Software product quality?

ISO 9126

ISO 829

ISO 1012

ISO 1028

ISO 9126 is the standard for software product quality. This standard defines a set of quality characteristics and sub-characteristics that can be used to evaluate the quality of a software product. It provides guidelines for measuring and assessing the quality of software in terms of functionality, reliability, usability, efficiency, maintainability, and portability. ISO 9126 is widely recognized and used in the software industry to ensure that software products meet the desired quality standards.

Explanation

ISO 9126 is the standard for software product quality. This standard defines a set of quality characteristics and sub-characteristics that can be used to evaluate the quality of a software product. It provides guidelines for measuring and assessing the quality of software in terms of functionality, reliability, usability, efficiency, maintainability, and portability. ISO 9126 is widely recognized and used in the software industry to ensure that software products meet the desired quality standards.

24. How much percentage of the life cycle costs of a software are spent on maintenance.

10%

30%

50%

70%

Maintenance costs typically account for the majority of the life cycle costs of a software. This is because once a software is developed and deployed, it requires ongoing support, bug fixes, updates, and enhancements. These maintenance activities can be time-consuming and resource-intensive, thus contributing to a significant portion of the overall costs. Therefore, it is not uncommon for approximately 70% of the life cycle costs to be spent on maintenance.

Explanation

Maintenance costs typically account for the majority of the life cycle costs of a software. This is because once a software is developed and deployed, it requires ongoing support, bug fixes, updates, and enhancements. These maintenance activities can be time-consuming and resource-intensive, thus contributing to a significant portion of the overall costs. Therefore, it is not uncommon for approximately 70% of the life cycle costs to be spent on maintenance.

25. During this event the entire system is tested to verify that all functional information structural and quality requirements have been met. A predetermined combination of tests is designed that when executed successfully satisfy management that the system meets specifications.

Validation Testing

Integration Testing

User Acceptance Testing

System Testing

User Acceptance Testing (UAT) is a type of testing where the system is tested by end-users or clients to determine if it meets their requirements and expectations. It is conducted to validate that the system is ready for actual use and to ensure that it meets the business needs. UAT is usually the final phase of testing before the system is deployed. In this phase, the system is tested in a real-world environment, and any issues or discrepancies are identified and resolved. Therefore, the given answer, User Acceptance Testing, is the correct one based on the explanation provided.

Explanation

User Acceptance Testing (UAT) is a type of testing where the system is tested by end-users or clients to determine if it meets their requirements and expectations. It is conducted to validate that the system is ready for actual use and to ensure that it meets the business needs. UAT is usually the final phase of testing before the system is deployed. In this phase, the system is tested in a real-world environment, and any issues or discrepancies are identified and resolved. Therefore, the given answer, User Acceptance Testing, is the correct one based on the explanation provided.

26. A _____ is the step-by-step method followed to ensure that standards are met

SDLC

Project Plan

Policy

Procedure

A procedure is a step-by-step method followed to ensure that standards are met. It outlines the specific actions and guidelines that need to be followed in order to achieve a desired outcome or meet a particular standard. Procedures provide a structured approach and help ensure consistency and efficiency in performing tasks or processes. They are typically documented and serve as a reference for individuals to follow in order to achieve desired results.

Explanation

A procedure is a step-by-step method followed to ensure that standards are met. It outlines the specific actions and guidelines that need to be followed in order to achieve a desired outcome or meet a particular standard. Procedures provide a structured approach and help ensure consistency and efficiency in performing tasks or processes. They are typically documented and serve as a reference for individuals to follow in order to achieve desired results.

27. Majority of system errors occur in the _________ phase

Requirements Phase

Analysis and Design Phase

Development Phase

Testing Phase

The majority of system errors occur in the requirements phase because this is the initial stage where the system's needs and objectives are defined. Any misunderstandings or miscommunications during this phase can lead to incorrect or incomplete requirements, which can result in errors throughout the rest of the development process. It is crucial to have a clear and comprehensive understanding of the system's requirements to minimize errors and ensure a successful project outcome.

Explanation

The majority of system errors occur in the requirements phase because this is the initial stage where the system's needs and objectives are defined. Any misunderstandings or miscommunications during this phase can lead to incorrect or incomplete requirements, which can result in errors throughout the rest of the development process. It is crucial to have a clear and comprehensive understanding of the system's requirements to minimize errors and ensure a successful project outcome.

28. Which of the following are valid justifications for developers testing their own code during unit testing?(i) Their lack of independence is mitigated by independent testing during system and acceptance testing.(ii)A person with a good understanding of the code can find more defects more quickly using white-box techniques.(iii)Developers have a better understanding of the requirements than testers.(iv)Testers write unnecessary incident reports because they find minor differences between the way in which the system behaves and the way in which it is specified to work.

(i) and (ii)

(i) and (iv)

(ii) and (iii)

(iii) and (iv)

Developers testing their own code during unit testing is justified because their lack of independence is addressed by independent testing during system and acceptance testing. Additionally, developers with a good understanding of the code can quickly identify more defects using white-box techniques. This allows for a thorough examination of the code and helps ensure its quality.

Explanation

Developers testing their own code during unit testing is justified because their lack of independence is addressed by independent testing during system and acceptance testing. Additionally, developers with a good understanding of the code can quickly identify more defects using white-box techniques. This allows for a thorough examination of the code and helps ensure its quality.

29. In ______ testing doesn't know anything about the software being tested; it just clicks or types randomly

Random testing

Gorilla testing

Adhoc testing

Dumb monkey testing

Dumb monkey testing refers to a type of testing where the tester has no knowledge about the software being tested and randomly clicks or types without any specific test cases or strategy. This approach is used to check the robustness and stability of the software by subjecting it to random inputs and actions. It is called "dumb monkey" as it lacks any intelligence or understanding of the software's functionality.

Explanation

Dumb monkey testing refers to a type of testing where the tester has no knowledge about the software being tested and randomly clicks or types without any specific test cases or strategy. This approach is used to check the robustness and stability of the software by subjecting it to random inputs and actions. It is called "dumb monkey" as it lacks any intelligence or understanding of the software's functionality.

30. Which of the following is NOT part System Testing:

Business process-based testing

Performance, Load & Stress Testing

Requirements-based Testing

Usability Testing

Top-Down integration Testing

Top-Down integration testing is not part of system testing because it is a type of integration testing. System testing focuses on testing the entire system as a whole, ensuring that all the components work together correctly and meet the specified requirements. Business process-based testing, performance, load & stress testing, requirements-based testing, and usability testing are all types of testing that are typically performed during system testing to ensure the system's functionality, performance, and usability are in line with the intended requirements and user expectations.

Explanation

Top-Down integration testing is not part of system testing because it is a type of integration testing. System testing focuses on testing the entire system as a whole, ensuring that all the components work together correctly and meet the specified requirements. Business process-based testing, performance, load & stress testing, requirements-based testing, and usability testing are all types of testing that are typically performed during system testing to ensure the system's functionality, performance, and usability are in line with the intended requirements and user expectations.

31. A top-down development strategy affects which level of testing most?

Component testing

Integration testing

System testing

User acceptance testing

The development strategy will affect the component testing (option (A)), in so far as it cannot be tested unless it has been built. Options (C) and (D) require the system to have been delivered; at these points the development strategy followed is not important to the tester. Option (B) needs knowledge of the development strategy in order to determine the order in which components will be integrated and tested.

Explanation

The development strategy will affect the component testing (option (A)), in so far as it cannot be tested unless it has been built. Options (C) and (D) require the system to have been delivered; at these points the development strategy followed is not important to the tester. Option (B) needs knowledge of the development strategy in order to determine the order in which components will be integrated and tested.

32. The main focus of Acceptance Testing is:

Finding faults in the system

Ensuring that the system is acceptable to all users

Testing the system with other systems

Testing for a business perspective

Testing by an independent test team

Acceptance testing is a type of testing that focuses on testing the system from a business perspective. It aims to ensure that the system meets the requirements and expectations of the stakeholders and is acceptable to all users. This type of testing evaluates the system's functionality, usability, and overall performance to determine if it aligns with the business goals and objectives. It is typically conducted by an independent test team to provide an unbiased assessment of the system's readiness for deployment.

Explanation

Acceptance testing is a type of testing that focuses on testing the system from a business perspective. It aims to ensure that the system meets the requirements and expectations of the stakeholders and is acceptable to all users. This type of testing evaluates the system's functionality, usability, and overall performance to determine if it aligns with the business goals and objectives. It is typically conducted by an independent test team to provide an unbiased assessment of the system's readiness for deployment.

33. Which of the following combinations correctly describes a valid approach to component testing: i) Functional testing of the component in isolationii) Structure-based testing of the code without recording incidentsiii) Automated tests that are run until the component passesiv) Functional testing of the interfaces between modules

I and ii

I, ii and iii

Iii

Ii and iv

The correct answer is I, ii and iii. This combination accurately describes a valid approach to component testing. Functional testing of the component in isolation (i) ensures that the component functions correctly on its own. Structure-based testing of the code without recording incidents (ii) focuses on testing the internal structure and logic of the code. Automated tests that are run until the component passes (iii) involve running automated tests repeatedly until the component meets the desired criteria. These three approaches cover different aspects of component testing and contribute to a comprehensive testing strategy.

Explanation

The correct answer is I, ii and iii. This combination accurately describes a valid approach to component testing. Functional testing of the component in isolation (i) ensures that the component functions correctly on its own. Structure-based testing of the code without recording incidents (ii) focuses on testing the internal structure and logic of the code. Automated tests that are run until the component passes (iii) involve running automated tests repeatedly until the component meets the desired criteria. These three approaches cover different aspects of component testing and contribute to a comprehensive testing strategy.

34. Which of the following is not true of regression testing?

It can be carried out at each stage of the life cycle

It serves to demonstrate that the changed software works as intended

It serves to demonstrate that software has not been unintentionally changed

It is often automated

This is a definition of confirmation testing. The other three options are true of regression testing

Explanation

This is a definition of confirmation testing. The other three options are true of regression testing

35. A software model that cannot be used in functional testing

Process flow model

State transaction model

Menu structure model

Plain language specification model

The menu structure model is a software model that cannot be used in functional testing because it focuses on the organization and structure of menus within a software application. It does not provide detailed information on the functionality or behavior of the software. Functional testing requires models that can simulate user interactions and test the functionality of the software, such as process flow models and state transaction models. Therefore, the menu structure model is not suitable for functional testing purposes.

Explanation

The menu structure model is a software model that cannot be used in functional testing because it focuses on the organization and structure of menus within a software application. It does not provide detailed information on the functionality or behavior of the software. Functional testing requires models that can simulate user interactions and test the functionality of the software, such as process flow models and state transaction models. Therefore, the menu structure model is not suitable for functional testing purposes.

36. Which test can be performed at all test levels?

System testing

Operational testing

Structural testing

Integration testing

Structural testing can be performed at all test levels. Structural testing focuses on testing the internal structure of the software, such as code, logic, and paths. It ensures that the code is functioning correctly and meets the expected specifications. This type of testing can be conducted at different levels, including unit testing, integration testing, system testing, and even during the maintenance phase. By examining the internal structure, structural testing helps identify any defects or issues that may arise and ensures the software's overall quality and reliability.

Explanation

Structural testing can be performed at all test levels. Structural testing focuses on testing the internal structure of the software, such as code, logic, and paths. It ensures that the code is functioning correctly and meets the expected specifications. This type of testing can be conducted at different levels, including unit testing, integration testing, system testing, and even during the maintenance phase. By examining the internal structure, structural testing helps identify any defects or issues that may arise and ensures the software's overall quality and reliability.

37. Which of the following is the main purpose of the integration strategy for integration testing in the small?

To ensure that all of the small modules are tested adequately

To ensure that the system interfaces to the other systems and networks

To specify which modules to combine when & how many at once

To ensure that the integration testing can be done by small team

To specify how the software should be divided in to modules

The main purpose of the integration strategy for integration testing in the small is to specify which modules to combine when and how many at once. This strategy helps in determining the order and timing of integrating different modules to ensure a smooth and efficient integration process. By specifying which modules to combine and when, the integration testing can be properly planned and executed, ensuring that any dependencies or interactions between modules are properly tested and validated.

Explanation

The main purpose of the integration strategy for integration testing in the small is to specify which modules to combine when and how many at once. This strategy helps in determining the order and timing of integrating different modules to ensure a smooth and efficient integration process. By specifying which modules to combine and when, the integration testing can be properly planned and executed, ensuring that any dependencies or interactions between modules are properly tested and validated.

38. Which of the following is usually the test basis for integration testing?

Program specification

Functional specification

Technical specification

Requirement specification

Integration testing is a level of testing where individual software modules are combined and tested as a group. The purpose of integration testing is to ensure that the modules work together correctly and that the integration between them is successful. The test basis for integration testing is usually the technical specification, as it provides detailed information about the technical aspects of the software modules, such as interfaces, data formats, and communication protocols. This information is necessary to design and execute integration test cases effectively. Program specification, functional specification, and requirement specification may provide some information relevant to integration testing, but the technical specification is typically the most comprehensive and specific.

Explanation

Integration testing is a level of testing where individual software modules are combined and tested as a group. The purpose of integration testing is to ensure that the modules work together correctly and that the integration between them is successful. The test basis for integration testing is usually the technical specification, as it provides detailed information about the technical aspects of the software modules, such as interfaces, data formats, and communication protocols. This information is necessary to design and execute integration test cases effectively. Program specification, functional specification, and requirement specification may provide some information relevant to integration testing, but the technical specification is typically the most comprehensive and specific.

39. Which of the following statements about the Component testing standard is false:

Black Box Design Tech all have an associated measurement technique

White Box design Tech all have an associated measurement technique

Cyclomatic Complexity is not a test measurement tech

Black Box measurement techniques all have an associated test Design Technique

White Box measurement techniques all have an associated test Design Technique

The statement "Black Box Design Tech all have an associated measurement technique" is false. Black box design techniques focus on testing the functionality of a component without considering its internal structure. These techniques do not involve measuring specific aspects of the component. Measurement techniques are typically associated with white box design techniques, which involve testing the internal structure and logic of the component.

Explanation

The statement "Black Box Design Tech all have an associated measurement technique" is false. Black box design techniques focus on testing the functionality of a component without considering its internal structure. These techniques do not involve measuring specific aspects of the component. Measurement techniques are typically associated with white box design techniques, which involve testing the internal structure and logic of the component.

40. Which of the following statements contain a valid goal for a function test set?

A Goal is that no more failures will result from the remaining defects

A goal is to eliminate as much as possible the cause of defects

A goal is to fulfill all requirements for the testing that are defined in the project plan

The correct answer is "A Goal is that no more failures will result from the remaining defects." This statement suggests that the goal of a function test set is to identify and fix all existing defects in order to prevent any further failures. This aligns with the objective of ensuring the software's reliability and stability by eliminating any potential issues that could lead to failures.

Explanation

The correct answer is "A Goal is that no more failures will result from the remaining defects." This statement suggests that the goal of a function test set is to identify and fix all existing defects in order to prevent any further failures. This aligns with the objective of ensuring the software's reliability and stability by eliminating any potential issues that could lead to failures.