iSQI CTFL_Syll2018 Exam Dumps

Maintenance testing is a type of testing that is done on an existing system after modifications or migration, or to prevent deterioration or obsolescence. Maintenance testing can be triggered by various events or situations, such as:

System migration from one platform to another, which can affect the functionality, performance, or compatibility of the system.

Preparation for an audit of a system, which can require verifying the compliance of the system with standards or regulations.

Modifications to a system, which can introduce new defects or affect existing ones.

Therefore, statements a, c, and d are correct.

Cost can be regarded as an exit criterion, as it is one of the factors that can influence the decision to stop testing. Spending too much money on testing will result in an unprofitable product, and having cost as an exit criterion helps avoid this. The other options are incorrect, as the financial value of product quality can be estimated, the cost of testing can be measured effectively, and having cost as an exit criterion does not necessarily constrain the testing project or help achieve the desired quality level.

These are examples of exit criteria, which are the conditions that must be met before testing can be completed. Exit criteria may also include test coverage measures, residual risk assessment, or stakeholder approval. The other options are not exit criteria, but rather test planning activities.

The statement that does not describe how testing contributes to higher quality is ''The testing of software demonstrates the absence of defects''. This statement is false because testing cannot prove that a software system is defect-free or has a certain level of quality because there might be some untested inputs or outputs that could reveal defects or failures. Testing can only provide information about the quality and risk level of a software system based on the observed behavior and results under certain conditions and assumptions. The other statements describe how testing contributes to higher quality by:

Performing a review of the requirement specifications before implementing the system can enhance quality: This statement is true because reviewing the requirement specifications can help identify and prevent defects, ambiguities, inconsistencies, or incompleteness in the requirements before they are implemented in the system, which can save time and effort and improve customer satisfaction.

Properly designed tests that pass reduce the level of risk in a system: This statement is true because passing tests can increase confidence that the system meets its requirements and expectations and provides value to the users and customers. Passing tests can also reduce the probability or impact of failures or defects in the system that could cause harm or loss.

Software testing identifies defects, which can be used to improve development activities: This statement is true because identifying defects can help analyze and remove their causes and prevent them from recurring in future development activities. Identifying defects can also help improve development processes, methods, standards, tools, techniques, etc., by providing feedback and lessons learned.

You can find more information about how testing contributes to higher quality in [A Study Guide to the ISTQB Foundation Level 2018 Syllabus], Chapter 1.

A key difference between a peer review of code and static analysis of code using a tool is that static analysis targets the code technically whereas peer review is applicable to further aspects. Static analysis focuses on the technical aspects of the code, such as syntax, logic, complexity, quality, security, etc. Peer review can also address these aspects, but it can also consider other aspects, such as readability, maintainability, usability, functionality, etc. Peer review can also provide feedback, suggestions, or opinions from different perspectives or expertise levels. compares these two techniques as follows:

Static analysis tools are software tools that examine (analyse) source code without executing it. They are used by developers as part of their development environment for checking their code against coding standards (rules), finding syntax errors etc.

Peer reviews are manual checking activities where work products such as requirements specifications or code are examined by colleagues (peers) for defects.

A, B, and C are incorrect answers. A peer review does not find defects while static analysis finds failures (A), as both techniques can find defects but not failures. Failures are observed at runtime when executing the code. Peer reviews cannot find missing requirements whereas static analysis can (B), as both techniques cannot find missing requirements but only check conformance to existing requirements. Missing requirements can be found by other techniques such as elicitation or validation. A peer review finds failures while static analysis finds defects , as both techniques find defects but not failures. Failures are observed at runtime when executing the code.