ISTQB Mock Test 8

Non-functional system testing focuses on evaluating the quality attributes of the system, such as 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 primary functions, but rather its overall performance and user experience. By conducting non-functional system testing, organizations can ensure that their system meets the desired quality standards and provides a satisfactory user experience.

Re-testing is the process of testing a previously failed test case again after the identified fault has been fixed to ensure that the fault has been successfully removed. On the other hand, regression testing is performed to verify that the changes or fixes made to the software have not introduced any new faults or unexpected side-effects in the existing functionality. Therefore, the correct answer states that re-testing ensures the original fault has been removed, while regression testing looks for unexpected side-effects.

Reviews and inspections can be considered part of testing because they help detect faults and improve the quality of the software. Reviews and inspections involve examining the development documentation, code, or design to identify defects, inconsistencies, or areas for improvement. This process helps ensure that the software meets the required standards and specifications. While reviews and inspections are typically conducted before testing, they are still an integral part of the overall testing process as they contribute to the overall quality of the software.

A failure refers to a deviation from the specified or expected behavior that is visible to end-users. It is a situation where the system does not perform its intended function correctly or produces incorrect results. This can be observed by the users and may lead to dissatisfaction or inconvenience. A failure can occur due to errors, faults, or defects in the system.

The cost of fixing a fault increases the later it is found because as time progresses, the fault can cause more damage and impact other parts of the system. Additionally, the longer a fault goes undetected, the more effort and resources will be required to identify and fix it. Therefore, it is important to identify and fix faults as early as possible to minimize the cost and impact on the system.

Beta testing is performed by customers at their own site. This means that the customers who will be using the software in the real-world environment test the software in their own environment to identify any issues or bugs. This type of testing allows for real-world scenarios and feedback from actual users, which can help identify any potential problems before the software is released to the general public.

Regression testing should be performed after the software has changed and when the environment has changed. This is because regression testing is done to ensure that the changes made to the software do not have any unintended side effects and that the software still functions correctly in the new environment. Performing regression testing every week, as often as possible, or when the project manager says to do so may not be necessary or efficient.

Testing should be stopped when it is aligned with the risks associated with the system being tested. The decision to stop testing should be based on an evaluation of the potential risks and the level of confidence achieved through testing. If the risks are deemed acceptable and the desired level of confidence has been reached, testing can be concluded. However, if there are significant risks remaining or if the desired level of confidence has not been achieved, testing should continue until these concerns are addressed.

Auditing conformance to ISO 9000 is not part of configuration management because ISO 9000 is a quality management standard that focuses on ensuring consistent quality in the processes and products of an organization. Configuration management, on the other hand, is a discipline that focuses on managing and controlling changes to software or hardware configurations throughout their lifecycle. While configuration management may involve auditing and quality control processes, specifically auditing conformance to ISO 9000 is not directly related to configuration management.

The purpose of a test completion criterion is to determine when to stop testing. This criterion helps in setting a specific condition or criteria that need to be met in order to consider the testing phase complete. It helps in ensuring that sufficient testing has been done and that the desired level of quality has been achieved. By defining this criterion, it becomes easier to make a decision on when to halt the testing process and move forward with the next phase of the software development lifecycle.

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 loads. Recovery testing, on the other hand, is a type of testing that checks how well the system recovers from failures or crashes. While recovery testing is important for ensuring system stability and resilience, it is not directly related to evaluating performance.

The given answer (10000, 50000, 99999) is correct because it includes the valid boundaries of the range (10000 and 99999) and a value within the valid equivalence class (50000). This ensures that the tests cover the minimum and maximum values as well as a representative value within the valid range.

LCSAJ (Linear Code Sequence and Jump) is not a black box testing technique because it involves analyzing the code structure and logic flow of a program. Black box testing techniques focus on testing the functionality of a system without considering its internal structure. State transition testing, syntax testing, and boundary value analysis are all examples of black box testing techniques as they only consider the inputs and outputs of the system under test.

Functional system testing is a type of testing that focuses on testing the end-to-end functionality of the system as a whole. This means that the testing is done to ensure that all the different components and features of the system work together correctly and meet the desired requirements. It involves testing the system's functionality from the user's perspective, making sure that all the functions and interactions within the system are working as expected. This type of testing helps to identify any issues or bugs that may arise when different parts of the system are integrated and used together.

Developers typically use static analysis (i) to analyze code without executing it and identify potential issues or bugs. They also use dynamic analysis (iv) to analyze code while it is running and identify runtime errors. On the other hand, the independent system test team typically uses performance testing (ii) to test the system's performance under different conditions and test management (iii) to plan, organize, and track the testing activities. Therefore, the correct answer is that developers would typically use i and iv, while the test team would typically use ii and iii.

Error guessing is best used after more formal techniques have been applied because formal techniques such as requirements analysis, specification-based testing, and structural testing help in identifying and covering the majority of the known and predictable errors. Once these formal techniques have been applied, error guessing can be used to uncover any additional errors that were not identified through the formal techniques. This approach ensures that a comprehensive set of test cases is developed, covering both known and unknown potential errors in the system.

The objective of proving that the software has no faults is not a reasonable test objective because it is practically impossible to prove that any software is completely free of faults. Testing is a process of finding defects and identifying areas of improvement, rather than proving perfection. Therefore, this objective is not feasible and does not align with the purpose of software testing.

The IEEE 829 test plan documentation standard includes test items, test deliverables, and test tasks. However, it does not include test specifications. Test specifications are typically included in other documentation standards, such as test design specifications or test case specifications.

The Test Plan document of the Test Documentation Standard includes various elements such as test objectives, test scope, test deliverables, test strategies, test environment requirements, test execution schedule, and resource requirements. However, quality plans are not typically included in the Test Plan document. Quality plans usually focus on the overall quality management process and are separate documents that outline the organization's quality goals, metrics, and processes. Therefore, quality plans are not included in the Test Plan document of the Test Documentation Standard.

Early test design refers to the process of designing tests at the earliest stage of the software development life cycle. The given answer states that statements i, iii, and iv are true, while ii and v are false. This means that early test design can prevent fault multiplication, can find faults, and can cause changes to the requirements. On the other hand, faults found during early test design are not necessarily more expensive to fix, and early test design does not always require more effort.

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 of the software system. It ensures that the integration process is organized and systematic, allowing for efficient testing and identification of any issues or bugs that may arise during the integration process. By specifying which modules to combine and when, the integration strategy helps in managing the complexity of the integration process and ensuring that it is carried out effectively.

Inspection is the correct answer because it is a type of review that follows a formal process with specific entry and exit criteria, including metrics. During an inspection, a team of reviewers examines the work product or deliverable in detail to identify defects, errors, or deviations from standards. The process is systematic and rigorous, aiming to ensure quality and adherence to requirements. Walkthroughs, management reviews, and post-project reviews may also involve some level of review, but they may not have the same level of formality and structured criteria as inspections.

The given code has two IF statements. To achieve full statement coverage, it is enough to execute the code once, so only 1 test is required. However, for branch coverage, each branch of the IF statements needs to be tested separately. The first IF statement has two branches (p+q > 100 and p+q 50 and p

Static analysis is a method used to analyze code without actually executing it. It can detect various issues such as the use of a variable before it has been defined, unreachable code, and array bound violations. However, static analysis is not able 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. Static analysis focuses on code structure and syntax, whereas memory leaks involve runtime behavior and memory management, which cannot be fully analyzed without executing the code.

BS 7925-1 is the correct answer because it is a standard that provides definitions of testing terms. ISO/IEC 12207 is a standard for software life cycle processes, ANSI/IEEE 829 is a standard for software test documentation, and ANSI/IEEE 729 does not exist. Therefore, BS 7925-1 is the most appropriate standard for providing definitions of testing terms.

Incidents are typically raised to report and track issues or problems in a system or process. In this context, incidents are not raised against improvements suggested by users. Instead, improvements suggested by users are usually considered as valuable feedback and suggestions for enhancing the system or process. Incidents are more commonly raised against requirements, documentation, and test cases when there are discrepancies or errors identified in these areas.

The correct answer is s = 4 and 5, t = 3, u = 2, v = 1. This is because the characteristics mentioned in the question, such as being led by a moderator or leader, and using entry and exit criteria, are typically associated with an inspection process. Additionally, the absence of management participation and the lack of documentation suggest an informal review process. Therefore, option s = 4 and 5, t = 3, u = 2, v = 1 aligns with these characteristics.

Top-down integration testing is not part of system testing because it is a type of integration testing, which focuses on testing the interaction between modules or components of a system. System testing, on the other hand, is a level of testing that verifies the complete and integrated system against the specified requirements. It involves testing the system as a whole, including its functionality, performance, usability, and other aspects. Therefore, top-down integration testing is not considered as part of system testing.

The given correct answer is "inspection is appropriate even when there are no written documents". This statement is not true because inspections typically involve reviewing written documents or physical objects to identify defects or non-compliance with standards. Without any written documents or physical evidence, there would be nothing to inspect. Inspections are a formal review process that should be led by a trained leader and can be performed by managers on management documents.

A typical commercial test execution tool is capable of performing various tasks such as recording test inputs, reading test values from a data file, and comparing expected outcomes with actual outcomes. However, it is not designed to calculate expected outputs. This means that the tool may not have built-in functionality to perform complex calculations or generate expected outputs based on specific criteria. Therefore, calculating expected outputs would be the one task that a typical commercial test execution tool would not be able to perform.

Maintenance testing uses Impact Analysis most because it involves testing changes made to an existing system or software. Impact Analysis helps in understanding the potential consequences of these changes on the system as a whole. It identifies the areas that may be affected by the changes and helps in determining the extent of testing required. This ensures that the changes do not introduce any new defects or disrupt the existing functionality of the system. Therefore, maintenance testing heavily relies on Impact Analysis to ensure the smooth functioning of the system after modifications.

Acceptance testing is a type of testing that evaluates whether a system meets the business requirements and is acceptable to the end users. It focuses on testing the system from a business perspective to ensure that it meets the desired objectives and functions correctly in real-world scenarios. This type of testing is crucial to ensure that the system is ready for deployment and meets the expectations of the stakeholders. It is not primarily focused on finding faults in the system or testing its integration with other systems, but rather on assessing its suitability for business use.

Live data would not come under Configuration Management because Configuration Management is the process of managing and controlling changes to software, hardware, documentation, and other items that make up a system. Live data refers to the current and active data being used in a system, and it is not typically managed or controlled as part of the configuration management process.

This answer states that statements ii, iii, and iv are true, while statements i and v are false. This means that 100% branch coverage does guarantee 100% statement coverage, 100% branch coverage does guarantee 100% decision coverage, and 100% decision coverage does guarantee 100% branch coverage. However, 100% statement coverage does not guarantee 100% branch coverage, and 100% statement coverage does not guarantee 100% decision coverage.

Expected outcomes are not defined by the software's behavior. Instead, they are derived from a specification, which outlines the desired behavior of the software. The software's behavior may or may not align with the expected outcomes, and it is the purpose of testing to identify any discrepancies. Therefore, the statement that expected outcomes are defined by the software's behavior is false.

The given statement that "black box test design techniques all have an associated test measurement technique" is FALSE. Black box test design techniques focus on testing the functionality of a component without considering its internal structure. These techniques do not necessarily have an associated test measurement technique because they primarily involve testing the inputs and outputs of the component without knowledge of its internal workings. Test measurement techniques are typically associated with white box test design techniques, which involve testing the internal structure and logic of the component.

The correct answer is "i is true, ii, iii and iv are false." This means that statement i is true, which states that an incident may be closed without being fixed. However, statements ii, iii, and iv are false. Statement ii states that incidents may not be raised against documentation, which is not true. Statement iii states that the final stage of incident tracking is fixing, which is also not true. Lastly, statement iv states that the incident record does not include information on test environments, which is false.

The typical costs for an inspection process include setting up forms and databases, analyzing metrics and improving processes, and the time spent on the document outside the meeting. However, writing the documents to be inspected is not included in these costs. This suggests that the documents to be inspected are likely prepared separately and are not considered as part of the inspection process itself.

Maintenance testing refers to the process of testing a released system that has been changed. This type of testing is conducted to ensure that the modifications made to the software do not introduce any new defects or issues. It involves testing the system's functionality, performance, and reliability after the changes have been implemented. The purpose of maintenance testing is to verify that the system still meets the business needs and requirements effectively. It is typically performed by users or testers who are familiar with the system and its intended usage.

The expected results are derived from the code. This means that the expected outcomes or outputs of a program are determined by analyzing the code itself. This is important because it ensures that the program is functioning correctly and producing the desired results. It also helps in identifying any discrepancies or errors in the code that may affect the expected results.