ISTQB CTFL-2018 Practice Test - Questions Answers, Page 28

A bug report is a document that records the details of a defect or failure found during testing, such as the steps to reproduce, the expected and actual results, the severity and priority, etc. A bug report should also include any observations or suggestions that may help correct the bug, such as the possible cause, the affected components, the related requirements, etc. This information can help the developers to locate and fix the bug more efficiently and effectively. Therefore, if a tester thinks of a likely cause for a specific bug, they should make a comment about it in the bug report.

Testing and debugging are two different activities that are related to finding and removing defects and failures in software. Testing is the process of evaluating software by applying test cases to find failures and provide information on its quality. Debugging is the process of finding, analyzing, and removing the causes of failures in software. Testing reveals failures, which are deviations of the actual behavior of the software from its expected behavior. Debugging removes defects, which are flaws in the software that cause failures.

Integration testing is the process of testing the interactions between different components or subsystems of a system. Integration testing verifies that the interfaces work correctly, meaning that they pass data and control correctly between components or subsystems, and that they handle errors and exceptions properly. Integration testing can also verify the functionality and quality of the integrated system or subsystem.

A test case is a set of preconditions, inputs, actions, expected results and postconditions developed based on test conditions. A test condition is a statement about what to test in terms of measurable coverage criteria from analysis of the test basis. A test plan is a description of the test objectives to be achieved and the means and the schedule for achieving them. A test oracle is a source to determine expected results to compare with the actual result of the system under test.

Testing and debugging are two different activities that are related to finding and removing defects and failures in software. Testing is the process of evaluating software by applying test cases to find failures and provide information on its quality. Debugging is the process of finding, analyzing, and removing the causes of failures in software. Designing tests to find failures and executing tests to show failures are testing activities. Locating the cause of failures and analyzing and fixing the defects are debugging activities.

The fundamental test process consists of five main activities: test planning and control, test analysis, test design, test implementation and execution, and test evaluation and reporting. During the test analysis activity, the testability of requirements is evaluated, meaning that the requirements are checked for clarity, completeness, consistency, verifiability, etc. Test analysis also involves identifying test conditions based on the test basis, such as requirements, specifications, user stories, or use cases.

The best way to take advantage of the different mindsets of testers and developers is to bring the two mindsets together. Testers and developers have different perspectives and skills that can complement each other and improve the quality of the software. Testers tend to focus on finding defects and verifying the software against the requirements and specifications, while developers tend to focus on creating and implementing the software according to the design and architecture. By collaborating and communicating with each other, testers and developers can share their knowledge, feedback, and ideas, and resolve issues more efficiently and effectively.

In a Scrum development life cycle model, regression testing is an increasingly important activity as the project progresses. Scrum is an agile framework that follows an iterative and incremental approach to software development, where the software is delivered in small units called sprints. Regression testing is a type of testing that verifies that previously tested software still performs as expected after changes or modifications. Regression testing is essential in Scrum, as new features or functionalities are added or modified in each sprint, which can introduce new defects or affect existing ones. Therefore, regression testing should be performed at the end of each sprint, as well as before releasing the software, to ensure that the software meets the quality standards and user expectations.

System testing is a test level that focuses on testing the system as a whole against its requirements and specifications. System testing applies to both functional and non-functional aspects of the system, such as functionality, performance, reliability, usability, security, etc. System testing has several objectives, such as:

Satisfying legal requirements, such as compliance with standards or regulations.

Using system specifications as a test basis, such as system requirements, system design, user stories, or use cases.

Establishing confidence in the system, such as its readiness for release or deployment, its suitability for use, its quality and reliability, etc.

Therefore, statements a and b apply to system testing.