ISTQB Mock Test 5

As we move across the life cycle, the cost of defects typically increases. This is because defects that are not identified and fixed early on can lead to larger issues and more costly repairs later in the process. Additionally, as the product or project progresses, the cost of fixing defects generally becomes more expensive due to factors such as increased complexity, integration challenges, and potential impact on other components. Therefore, it is important to address and resolve defects as early as possible to minimize their impact on cost.

Boundary value analysis (BVA) is a testing technique that focuses on testing the boundaries or extreme values of input and output equivalence classes. It tests the boundary conditions on, below, and above the edges of these classes. BVA helps in identifying errors that occur at the boundaries, as they are more likely to cause issues. This technique is different from equivalence partitioning, which divides the input domain into classes and selects representative values from each class for testing. BVA is not limited to structural testing, as it can be applied to various types of testing.

Management Approval is not a type of review because it is not focused on evaluating or critiquing a product or process. Instead, it is a decision-making process where management assesses and approves certain actions or decisions. Reviews, on the other hand, involve analyzing and assessing the quality, effectiveness, or compliance of a product or process. Technical Review, Walkthrough, and Inspection are all types of reviews that are commonly used in various industries to ensure the quality and correctness of a product or process.

Recovery testing is not a part of performance testing. Performance testing focuses on evaluating the system's performance under different conditions such as simulating many users, measuring transaction rates, and measuring response time. Recovery testing, on the other hand, is a type of testing that checks how well the system recovers from failures or crashes. While it is an important type of testing, it is not specifically related to performance evaluation.

The correct answer is A1, B4, C2, D3. This is because the first statement describes the principle of early testing, which emphasizes starting testing activities as early as possible in the software development life cycle. The fourth statement describes the principle of the pesticide paradox, which states that test cases must be regularly reviewed and revised to ensure their effectiveness. The second statement describes the principle of exhaustive testing, which states that testing everything is not feasible except for trivial cases. The third statement describes the principle of the absence-of-errors fallacy, which highlights that finding and fixing defects does not help if the system built is unusable and does not fulfill the user's needs and requirements.

User Requirements are the best source of expected outcomes for User Acceptance Test Scripts because they outline the specific functionalities and features that the end users expect from the software. These requirements are derived from the needs and expectations of the users and serve as a basis for defining the success criteria for the acceptance testing phase. By referring to the User Requirements, the testers can ensure that the software meets the desired outcomes and satisfies the users' needs. Program specification, System Specification, and Actual Results may provide additional information, but User Requirements are the primary and most reliable source for defining the expected outcomes.

The correct answer is "Checking the on-line booking screen information and the database contents against the information on the letter to the customers." This is a functional test because it involves verifying that the on-line booking system is functioning correctly by comparing the information displayed on the screen and stored in the database with the information provided in the letter to the customers. It focuses on the system's ability to perform its intended function accurately and effectively.

The goals and objectives of testing include finding defects, preventing defects, and gaining confidence in and providing information about the level of quality. Finding defects is an important goal as it helps identify and fix issues in the software. Preventing defects aims to implement practices and techniques that minimize the occurrence of defects. Gaining confidence in and providing information about the level of quality involves evaluating the software's performance and ensuring it meets the desired standards. Therefore, all of the given options are correct goals and objectives of testing.

not-available-via-ai

Alpha testing is a type of user acceptance testing, not integration testing. Integration testing focuses on testing the interaction and integration between different components or modules of a system, ensuring they work together as expected. On the other hand, alpha testing is conducted by end-users or internal testers to evaluate the software's usability, functionality, and overall user experience before its official release. Therefore, alpha testing is not considered a type of integration testing.

Component testing is also known as program testing, module testing, and unit testing. This is because component testing refers to the process of testing individual components or units of a software system to ensure that they function correctly and meet the specified requirements. Program testing, module testing, and unit testing are all different terms used to describe this type of testing. Therefore, the correct answer is "All of the above."

The correct sequence of the test process activities is as follows: Planning and control (III) is the first step, followed by Analysis and design (I), Implementation and execution (IV), Evaluating exit criteria and reporting (V), and finally Test closure activities (II). This sequence ensures that the testing process is conducted in a logical and organized manner, starting with planning and ending with closure activities.

To promote and maintain good relationships between testers and developers, it is crucial to explain test results in a neutral fashion. This means presenting the findings without bias or personal opinions, focusing on objective data and facts. By doing so, it fosters a collaborative and non-confrontational environment, allowing testers and developers to work together effectively in resolving any issues or bugs identified during testing. It helps to minimize misunderstandings, conflicts, and blame game between the two parties, leading to better communication, trust, and ultimately, improved software quality.

Scalability is not a software characteristic because it refers to the ability of a system to handle increased workload or growing demands. It is more related to hardware or infrastructure rather than software itself. Software characteristics typically include usability, reliability, and maintainability, which focus on the functionality, performance, and ease of maintenance of the software.

Regression tests are not the same as confirmation testing (statement I is incorrect). They can be effective even if not automated (statement II is incorrect). However, they can be useful if well designed and can help reduce the risk of adverse effects from system changes (statements III and IV are correct). Therefore, the correct answer is III and IV.

The typical factors for the 'entry and exit criteria' include test items, acquisition and supply, and quality. These factors are important in determining when a test can begin (entry criteria) and when it can be considered complete (exit criteria). Test items refer to the specific components or elements that will be tested. Acquisition and supply involve the processes and resources needed to obtain the necessary test items. Quality refers to the standards and requirements that must be met for the test to be considered successful. Therefore, all of the options mentioned (test items, acquisition and supply, quality) are relevant factors for entry and exit criteria.

The correct answer is 3, 8, 22.

The given question asks for test inputs that cover all the valid and invalid equivalence classes for the numeric values accepted in the range 5 to 20. The valid equivalence classes are the values within the range (5 to 20), and the invalid equivalence classes are the values outside the range (20).

Among the given options, 3 and 8 fall within the valid range (5 to 20), covering the valid equivalence class. 22 falls outside the valid range, covering the invalid equivalence class. Therefore, 3, 8, and 22 cover all the valid and invalid equivalence classes.

Test Execution provides the biggest potential cost saving from the use of CAST. This is because CAST (Computer-Aided Software Testing) automates the execution of test cases, reducing the need for manual testing. Automation saves time and effort, allowing for faster and more efficient testing. It also reduces the risk of human error and increases test coverage. By automating the test execution process, organizations can save significant costs associated with manual testing, such as hiring and training resources, and improve overall testing productivity.

The task of Test control involves initiating corrective actions, making decisions, and providing information on testing. However, writing a test summary report for stakeholders is not a task of Test control. This report is typically prepared by the Test Analyst or Test Manager to provide a summary of the testing activities, test results, and overall quality of the software being tested.

The procedure asks two questions: one about the type of ticket (Single or Return) and another about the rate (Standard or Cheap-day). The number of test inputs needed to ensure that all the questions have been asked, all the combinations have occurred, and all replies are given can be calculated by multiplying the number of options for each question. In this case, there are 2 options for the type of ticket (Single or Return) and 2 options for the rate (Standard or Cheap-day), resulting in a total of 2 * 2 = 4 possible combinations. However, since one of the combinations does not require any further questions (Single ticket), we subtract it from the total, resulting in 4 - 1 = 3. Therefore, 3 test inputs are needed to cover all the possible combinations and replies.

not-available-via-ai

During the activity of evaluating exit criteria and reporting, we assess whether the previously defined criteria for completing the testing process have been met. This involves analyzing the test results, checking if the test objectives have been achieved, and determining if additional tests are necessary to ensure the desired level of quality. This step helps in making informed decisions about whether to proceed with further testing or to conclude the testing process.

Organizational factors are included in project risk because they can significantly impact the success of a project. These factors can include lack of communication, inadequate resources, poor project management, and resistance to change within the organization. All of these can contribute to delays, budget overruns, and ultimately, project failure. Therefore, considering and managing organizational factors is crucial in effectively managing project risks.

The given statement "Configuration management tool -- Check for consistence" is a mismatch because a configuration management tool is not primarily used to check for consistency. Configuration management tools are used to track and manage changes in software or hardware configurations, ensuring that all components are properly configured and versioned. Consistency checking is typically performed by other tools or processes, such as testing or quality assurance.

The cyclomatic complexity of a program is a measure of the number of linearly independent paths through its source code. In this program, there are three linearly independent paths: one for the "IF A THEN" condition, one for the "ELSE IF Y >= Z THEN" condition, and one for the "ELSE" condition. Therefore, the cyclomatic complexity of this program is 3.

Creating test suites from test cases is not a test analysis and design process activity because it falls under the test implementation and execution phase. Test analysis and design activities involve identifying test conditions, evaluating testability, and designing the test environment set-up. Once these activities are completed, the test cases are created, and then test suites are formed from these test cases for execution.

The role and responsibilities of a Moderator include scheduling meetings, disseminating documents before the meeting, coaching other team members, and storing the data that is collected.

The given code contains an if-else statement that checks the values of x and y. If x is equal to y, then the code inside the if block is executed. In this case, z is incremented by 1 and then it is checked if z is less than 5. If z is less than 5, the value of w is set to 10. On the other hand, if x is greater than y, the code inside the elseif block is executed and the value of w is set to 5.

In order to ensure 100% statement coverage, we need to test all possible paths of the code. The combination of x=3, y=3, and z=3 satisfies the condition x=y, and zy, so only the elseif block is executed. Therefore, these two combinations ensure 100% statement coverage.

The likely name for a test plan that is written to establish confidence in the system is an "Acceptance Test Plan". This type of test plan outlines the testing activities that will be conducted to determine if the system meets the requirements and is acceptable for delivery to the end users or stakeholders. The acceptance test plan focuses on validating the system's functionality, usability, and overall performance to ensure that it meets the expectations and needs of the users.

The purpose of Function Point Analysis (FPA) is to measure the size of the functionality of an Information System. FPA is a software metric used to quantify the functionality provided by a software application. It measures the functionality based on the inputs, outputs, external interfaces, and data files involved in the system. By measuring the size of the functionality, FPA helps in estimating project effort, cost, and resources required for development and maintenance of the system.

To achieve 100% statement coverage (SC), only one test input is needed because there is only one statement in the code. However, to achieve 100% decision coverage (DC), two test inputs are needed because there are two conditions in the code: (a > b) and (c > d). Therefore, the correct answer is SC = 1; DC = 2.

Test Comparator is the correct answer because it is a tool specifically designed to compare and identify differences across various data sources such as files, databases, and test results. It helps in identifying discrepancies and inconsistencies in the data, allowing testers to analyze and troubleshoot any issues that may arise during testing. Test Comparator is an essential tool for ensuring data integrity and accuracy in testing processes.

The correct answer is that the participants work individually on the document under review. This is not true about the Kick-off meeting because the goal of the meeting is to get everybody on the same wavelength regarding the document under review. The participants work together to discuss and understand the objectives of the review and the documents. The result of entry check and defined exit criteria are also discussed during the meeting.

XP, or Extreme Programming, is an agile software development methodology that promotes pair programming and shared code ownership among developers. Pair programming involves two programmers working together on the same task, with one writing the code and the other reviewing it in real-time. This practice helps improve code quality, knowledge sharing, and collaboration within the team. Shared code ownership means that all team members have equal responsibility for the codebase, allowing for better collaboration, faster problem-solving, and reduced bottlenecks.

The statement "In technical review, a formal follow-up is carried out by the moderator applying exit criteria" is true. In technical review, a formal follow-up is conducted by the moderator to ensure that all identified defects have been addressed and the necessary exit criteria have been met.

The IEEE 829 Standard Test Plan Template includes sections such as staffing and training needs, suspension and resumption criteria, and responsibilities. However, special procedural requirements are not a part of this template. Special procedural requirements may refer to any additional or unique procedures that are specific to a particular project or organization, but they are not explicitly mentioned in the IEEE 829 Standard Test Plan Template.

Data-control scripts are not a level of scripting. The other options mentioned, linear scripting, structural scripts, and shared scripts, are all valid levels of scripting. Linear scripting refers to a sequential script execution, structural scripts involve the use of control structures like loops and conditionals, and shared scripts are scripts that can be used by multiple users or applications. However, data-control scripts do not fit into any specific level of scripting.

The correct answer is a1, b2, c3,4,5,6,7. According to the IEEE 829 standard, the test incident report should include the test incident report identifier (a1), the summary (b2), and the impact (c3). Additionally, it should also record the incident description (c4), inputs (c5), expected results (c6), actual results (c7), and anomalies (c8).

The statement "Black box techniques all have an associated test design technique" is FALSE. Black box techniques refer to testing without knowledge of the internal structure or implementation of the component being tested. These techniques focus on the input and output of the component. While black box techniques do have associated test techniques, not all of them have an associated test design technique. Some black box techniques, such as equivalence partitioning and boundary value analysis, have specific test design techniques, but others, such as exploratory testing, do not have a specific associated test design technique.

A manual test script specifies the sequence of actions or steps that a tester needs to follow in order to execute a test. It provides detailed instructions on how to perform each step, including any input data that needs to be entered and the expected output or result. By following the manual test script, the tester can ensure that the test is executed consistently and accurately. Test design specification, test plan, and test case specification may provide overall guidelines or instructions, but it is the manual test script that provides the specific sequence of actions for executing the test.