Techniques Of Design Testing

Primary Flow is called as Basic Flow because it represents the main sequence of steps or actions that are required to achieve the desired outcome in a process or system. It is the most common and essential path that users or systems follow to accomplish a specific task. The Basic Flow typically outlines the standard or expected behavior, while Alternate Flows represent alternative paths or deviations from the main flow. Basic with Invalid Flow and Invalid Flow are not commonly used terms in the context of process flows, making Basic Flow the most appropriate and logical choice.

Regression test cases are mostly automated due to the high frequency of releases in maintenance testing. Automation allows for faster and more efficient execution of test cases, reducing the time and effort required for regression testing. Additionally, with each release, there may be changes to the software, and automated test cases can easily be updated to reflect these changes. Automation also ensures consistency in executing test cases, minimizing human errors. Overall, automating regression test cases helps in ensuring the stability and quality of the software during the maintenance phase.

The given statement suggests that a negative scenario should be used to test whether the application behaves correctly or not. This means that the application should not behave in the desired manner in order to pass the negative scenario test. Therefore, the correct answer is true.

When one requirement is mapped with multiple scenarios, it means that there are different situations or conditions in which the requirement can be tested. Similarly, if multiple scenarios are mapped with multiple test cases, it means that different test cases are designed to cover each scenario. This approach ensures that all possible scenarios and variations of the requirement are tested thoroughly, increasing the chances of detecting any potential issues or bugs. Therefore, the statement "When one requirement is mapped with multiple scenarios then the same way multiple scenarios mapped with multiple test cases" is true.

The statement "RTM is not bi-directional" is false. RTM, which stands for Requirements Traceability Matrix, is a tool used in project management to ensure that all requirements are met. It is a bi-directional matrix that links requirements with the corresponding design, development, and testing activities. This means that it allows for tracing requirements both forwards and backwards, ensuring that all aspects of the project are aligned with the specified requirements. Therefore, the correct answer is false.

RTM (Requirements Traceability Matrix) is considered a Many to Many relationship because it allows for multiple test cases and scenarios to be mapped to a single requirement. Additionally, it allows for multiple requirements to be mapped to a single scenario and a single test case. This flexibility in mapping multiple entities to each other makes it a Many to Many relationship.

Test artifacts are indeed part of the test development process. Test artifacts refer to the various documents and deliverables that are created during the testing process, such as test plans, test cases, test scripts, test data, and test reports. These artifacts help in planning, designing, executing, and tracking the testing activities. They provide a systematic approach to testing and ensure that the testing process is well-documented and repeatable. Therefore, the statement "Reviewing the Test Artifacts are part of Test development process" is true.

This statement is false because a single requirement can be mapped with multiple scenarios. Scenarios are used to describe different ways in which a requirement can be satisfied or tested. By mapping multiple scenarios to a single requirement, it ensures that all possible scenarios are considered and tested.

The objective is not the same for all levels of testing. Each level of testing has its own specific objective. For example, unit testing focuses on testing individual components or units of software, while system testing aims to test the entire system as a whole. Similarly, integration testing focuses on testing the interaction between different components or modules. Therefore, the statement is false.

A testable business scenario can be translated into test cases during the test development process. This means that the scenario can be broken down into specific steps or actions that can be tested to verify the functionality or behavior of the system. Test cases are designed to cover different aspects of the scenario and ensure that all the requirements are met. Therefore, the statement "Testable business scenario cannot be translated to test cases during the test development" is false.

Impact analysis helps to decide how much regression testing should be done. This is because impact analysis involves assessing the potential impact of a change in a software system on other parts of the system. By understanding the impact, it becomes possible to determine which areas of the system are most likely to be affected and therefore require more extensive regression testing. This helps in prioritizing the testing efforts and allocating resources effectively.

BVA (Boundary Value Analysis) is a testing technique that focuses on testing the boundaries or limits of input values. ECP (Equivalence Class Partitioning) is another testing technique that divides the input values into different classes or groups. In this context, the statement "BVA will cover ECP" means that by applying BVA, the boundaries and limits of the equivalence classes will be covered during testing. This statement is true because BVA inherently includes testing the values at the boundaries of equivalence classes, ensuring comprehensive test coverage.

The correct answer is 2^n. In a decision table, each input has two possible values, either true or false. If there are N inputs, then there are 2 possible values for each input, resulting in a total of 2^n possible combinations of inputs. Therefore, the maximum number of outputs in a decision table when the input is N is 2^n.

In the given statement, it is stated that each scenario is mapped into a single requirement. However, this statement is not true. In software development, multiple scenarios can often be mapped into a single requirement. Scenarios are used to describe different user interactions or situations, while requirements specify what the software should do. Therefore, it is possible for multiple scenarios to fall under a single requirement.

The entry criteria for test case development include having a frozen requirement document, an approved test strategy, approved standards for the test case document, an approved test case naming convention, and a test data source. In this case, all five criteria are true, so the correct answer is that i, ii, iii, iv, and v are true.

The given answer 5, 120, 70 represents a set of values that fall within the equivalent partitioning range of 10-110. Equivalent partitioning is a technique used in software testing to divide a range of input values into equivalent groups. In this case, the values 5, 120, and 70 are within the range of 10-110, making them equivalent partitions. This means that they can be used interchangeably for testing purposes, as they are expected to produce similar results.

Regression testing is not applicable for a new project because it is the process of retesting the modified or updated parts of a system to ensure that the changes have not introduced any new defects or issues. Since a new project does not have any previous versions or modifications, there is no need for regression testing. Impact analysis is also not applicable for a new project because it involves assessing the potential effects and dependencies of a change on other parts of the system. Since a new project does not have any existing components or dependencies, there is no need for impact analysis.

The given correct answer is "False" because exceptional cases are indeed considered as valid scenarios. Exceptional cases refer to situations that deviate from the normal flow of a program or system, such as error handling or edge cases. These cases are important to consider and test in order to ensure the robustness and reliability of the program or system.

Test conditions act as a bridge between test scenarios and test cases. Test scenarios define the overall objective or goal of testing, while test cases are specific instances or steps to be executed to validate the scenario. Test conditions, on the other hand, are the preconditions or requirements that need to be met in order to execute a test case. They help in determining whether a particular test case is applicable or not for a given scenario. Thus, test conditions play a crucial role in connecting the high-level test scenarios with the detailed test cases.

Transactional data refers to the information that is generated as a result of transactions or business activities. It includes details such as sales transactions, customer orders, invoices, and payments. This type of data is used for various purposes, including analysis, reporting, and decision-making. In the given context, the correct answer suggests that the system used the transactional data for data processing, indicating that it processed and analyzed the information related to business transactions.

Project closure activities are not performed at the end of every test release. Project closure activities typically occur at the end of the entire project, not just at the end of a test release. These activities involve finalizing and documenting project deliverables, conducting a project review, and closing out any outstanding tasks or contracts. Test releases are part of the larger project, and while there may be some specific activities related to closing out a test release, they would not encompass all of the project closure activities. Therefore, the statement is false.

The given correct answer for this question is "Test Cases". In the Test Development Phase, one of the activities is to create test cases. Test cases are a set of conditions or steps that are designed to verify the functionality of a system or software. They are created based on the requirements and specifications of the system being tested. Test cases help in identifying any defects or issues in the system and ensure that it meets the desired quality standards. Therefore, creating test cases is an important part of the Test Development Phase.

The correct answer is i, ii, iii are true and iv is false. This is because the given options state that Test Case Review consists of Formal Review, Peer Review, and Informal Review, which are all true. However, the option iv, which states that Test Case Review consists of Inspection, is false. Therefore, the correct answer is i, ii, iii are true and iv is false.

Peer reviews are a type of quality assurance activity in which a group of peers examines and evaluates a work product, such as a document or a piece of code, for defects, errors, and improvements. While inspections, walkthroughs, and formal reviews are also types of peer reviews, the term "Technical Review" is commonly used to refer to the process of peer reviews. Therefore, "Technical Review" is the correct answer to the question.

RTM, or Requirements Traceability Matrix, helps to ensure functional coverage in an application. It is a document that maps the requirements to the test cases, ensuring that each requirement is tested and covered by at least one test case. This helps in identifying any gaps in testing and ensures that all the required functionalities of the application are thoroughly tested. By using RTM, testers can track the progress of testing and ensure that all functional aspects of the application are covered.

During the test planning phase, the project team establishes a test coverage goal based on the risk and criticality associated with the AUT (Application Under Test). Test coverage refers to the extent to which the AUT is tested to ensure that all the important functionalities, features, and scenarios are covered. By setting a test coverage goal, the team aims to ensure that a sufficient number of test cases are designed and executed to achieve the desired level of coverage, thereby reducing the risk of undetected defects in the software.

Impact Analysis is the correct answer because when introducing a new module or functionality to an existing product under test, it is important to assess the potential impact it may have on the existing system. Impact Analysis helps in identifying the areas that may be affected by the change and allows for proper planning and prioritization of testing efforts. It helps to determine which test cases need to be re-executed and which areas of the system need to be focused on during testing.

Pre-requisites and Test Data are not required for a test scenario. Pre-requisites refer to the necessary conditions or setup that must be in place before the test can be executed. Test Data refers to the specific inputs or data that is used during the test. While an approved test plan and requirement analysis are important for test scenarios, pre-requisites and test data are not directly related to defining or executing a test scenario.

The statement suggests that the Incremental approach will provide a brief detail of the application and business state, which is incorrect. In an Incremental approach, the development process is divided into smaller increments or iterations, where each iteration builds upon the previous one. It focuses on delivering a working product incrementally, rather than providing a detailed overview of the entire application and business state. Therefore, the correct answer is False.

The entry criteria for Test Design include the approved business process document and the functionality document. These documents provide the necessary information and guidelines for designing the tests. The approved business process document outlines the specific processes and workflows that need to be tested, while the functionality document details the specific features and functionalities of the system that need to be tested. These documents ensure that the test design is aligned with the client's requirements and expectations.