Istqb3 - Static Testing - Quiz & Trivia

1. The Phases of formal review process is mentioned below. Arrange them in the correct order. i. Planning ii. Review Meeting iii. Rework iv. Individual Preparations v. Kick Off vi. Follow Up

I,ii,iii,iv,v,vi

Vi,i,ii,iii,iv,v

I,v,iv,ii,iii,vi

I,ii,iii,v,iv,vi

The correct order of the phases of the formal review process is as follows: Planning, Kick Off, Individual Preparations, Review Meeting, Rework, Follow Up. First, the planning phase takes place to outline the objectives and scope of the review. Then, the kick-off phase occurs to officially start the review process. Individual preparations come next, where participants study the material independently. The review meeting is then conducted to discuss findings and address any issues. Rework is the phase where necessary changes and improvements are made based on the review. Finally, the follow-up phase ensures that actions and recommendations from the review are implemented.

Explanation

The correct order of the phases of the formal review process is as follows: Planning, Kick Off, Individual Preparations, Review Meeting, Rework, Follow Up. First, the planning phase takes place to outline the objectives and scope of the review. Then, the kick-off phase occurs to officially start the review process. Individual preparations come next, where participants study the material independently. The review meeting is then conducted to discuss findings and address any issues. Rework is the phase where necessary changes and improvements are made based on the review. Finally, the follow-up phase ensures that actions and recommendations from the review are implemented.

2. In which phase static tests are used

Requirements

Design

Coding

All of the above

Static tests are used in all phases of software development, including requirements, design, and coding. These tests involve analyzing the code or documentation without actually executing it. In the requirements phase, static tests can be used to review and verify that the specified requirements are complete and consistent. In the design phase, static tests can be used to ensure that the design meets the requirements and is free from errors. In the coding phase, static tests can be used to detect and fix issues in the code before it is executed. Therefore, static tests are applicable in all phases of software development.

Explanation

Static tests are used in all phases of software development, including requirements, design, and coding. These tests involve analyzing the code or documentation without actually executing it. In the requirements phase, static tests can be used to review and verify that the specified requirements are complete and consistent. In the design phase, static tests can be used to ensure that the design meets the requirements and is free from errors. In the coding phase, static tests can be used to detect and fix issues in the code before it is executed. Therefore, static tests are applicable in all phases of software development.

3. What can static analysis NOT find?

The use of a variable before it has been defined

Unreachable ("dead") code

Memory leaks

Array bound violations

Static analysis is a method of analyzing code without actually executing it. It can identify issues like the use of a variable before it has been defined, unreachable code, and array bound violations. However, static analysis is unable to detect memory leaks, which occur when a program fails to release allocated memory after it is no longer needed. Memory leaks can only be found through dynamic analysis, which involves executing the code and monitoring memory usage. Therefore, static analysis is not capable of identifying memory leaks.

Explanation

Static analysis is a method of analyzing code without actually executing it. It can identify issues like the use of a variable before it has been defined, unreachable code, and array bound violations. However, static analysis is unable to detect memory leaks, which occur when a program fails to release allocated memory after it is no longer needed. Memory leaks can only be found through dynamic analysis, which involves executing the code and monitoring memory usage. Therefore, static analysis is not capable of identifying memory leaks.

4. Which of the following BEST describes the difference between an inspection and a walkthrough?

Both inspections and walkthroughs are led by the author.

An inspection is led by a moderator and a walkthrough is led by the author.

Both inspections and walkthroughs are led by a trained moderator.

A walkthrough is led by the author. The author is not present during inspections.

An inspection is a review process led by a moderator, who is typically an independent person not involved in the development of the product. The moderator's role is to facilitate the inspection and ensure that it follows a structured process. On the other hand, a walkthrough is led by the author of the product, who guides the participants through the product and explains its functionality. The author's presence during a walkthrough allows for immediate clarification and discussion of any issues or concerns that arise.

Explanation

An inspection is a review process led by a moderator, who is typically an independent person not involved in the development of the product. The moderator's role is to facilitate the inspection and ensure that it follows a structured process. On the other hand, a walkthrough is led by the author of the product, who guides the participants through the product and explains its functionality. The author's presence during a walkthrough allows for immediate clarification and discussion of any issues or concerns that arise.

5. Who is responsible for document all the issues, problems and open point that were identified during the review meeting

Moderator

Scribe

Reviewers

Author

The scribe is responsible for documenting all the issues, problems, and open points that were identified during the review meeting. They are tasked with taking detailed notes and accurately recording the discussions and decisions made during the meeting. This helps ensure that all relevant information is properly documented and can be referred to later for follow-up actions or further discussion. The scribe plays a crucial role in maintaining a record of the review meeting and ensuring that nothing is overlooked or forgotten.

Explanation

The scribe is responsible for documenting all the issues, problems, and open points that were identified during the review meeting. They are tasked with taking detailed notes and accurately recording the discussions and decisions made during the meeting. This helps ensure that all relevant information is properly documented and can be referred to later for follow-up actions or further discussion. The scribe plays a crucial role in maintaining a record of the review meeting and ensuring that nothing is overlooked or forgotten.

6. Which of the following statements are TRUE for informal reviews? I. Easy to get started and have some benefit II. Have no or minimal formal process III. The process must be documented IV. May include "paired programming"

I, II and IV

I and III

III and IV

I, III and IV

Informal reviews are known for being easy to get started and still providing some benefit. They do not have a formal process or minimal formal process, making them less structured than formal reviews. The process does not necessarily need to be documented. Informal reviews may also include "paired programming," where two individuals work together on a task.

Explanation

Informal reviews are known for being easy to get started and still providing some benefit. They do not have a formal process or minimal formal process, making them less structured than formal reviews. The process does not necessarily need to be documented. Informal reviews may also include "paired programming," where two individuals work together on a task.

7. Which expression best matches the following characteristics or review processes: 1. Led by author 2. Undocumented 3. No management participation 4. Led by a trained moderator or leader 5. Uses entry exit criteria s) Inspection t) Peer review u) Informal review v) Walkthrough

S = 4, t = 3, u = 2 and 5, v = 1

S = 4 and 5, t = 3, u = 2, v = 1

S = 1 and 5, t = 3, u = 2, v = 4

S = 5, t = 4, u = 3, v = 1 and 2

S = 4 and 5, t = 1, u = 2, v = 3

This answer suggests that the characteristics or review processes described in the question are best matched by the following:

- s = 4 and 5: Led by a trained moderator or leader and uses entry exit criteria
- t = 3: No management participation
- u = 2: Undocumented
- v = 1: Led by author

This combination of characteristics matches the process of a walkthrough, where a trained moderator or leader leads the review, there is no management participation, the process is undocumented, and the author leads the discussion.

Explanation

This answer suggests that the characteristics or review processes described in the question are best matched by the following:

- s = 4 and 5: Led by a trained moderator or leader and uses entry exit criteria
- t = 3: No management participation
- u = 2: Undocumented
- v = 1: Led by author

This combination of characteristics matches the process of a walkthrough, where a trained moderator or leader leads the review, there is no management participation, the process is undocumented, and the author leads the discussion.

8. Defects discovered by static analysis tools include: i. Variables that are never used. ii. Security vulnerabilities. iii. Programming Standard Violations iv. Uncalled functions and procedures

I , ii,iii,iv is correct

Iii ,is correct i,ii,iv are incorrect.

I ,ii, iii and iv are incorrect

Iv, ii is correct

Static analysis tools are used to analyze code without actually executing it. They can detect various types of defects, including variables that are never used, security vulnerabilities, programming standard violations, and uncalled functions and procedures. Therefore, options i, ii, iii, and iv are all correct as they accurately identify the defects that can be discovered by static analysis tools.

Explanation

Static analysis tools are used to analyze code without actually executing it. They can detect various types of defects, including variables that are never used, security vulnerabilities, programming standard violations, and uncalled functions and procedures. Therefore, options i, ii, iii, and iv are all correct as they accurately identify the defects that can be discovered by static analysis tools.

9. Which of the following is a purpose of the review planning phase?

Log defects.

Explain the documents to the participants.

Gather metrics.

Allocate the individual roles

The purpose of the review planning phase is to allocate individual roles. During this phase, the team assigns specific responsibilities and tasks to each team member involved in the review process. This ensures that everyone has a clear understanding of their role and helps to streamline the review process. By allocating individual roles, the team can effectively manage and coordinate the review activities, leading to a more efficient and successful review.

Explanation

The purpose of the review planning phase is to allocate individual roles. During this phase, the team assigns specific responsibilities and tasks to each team member involved in the review process. This ensures that everyone has a clear understanding of their role and helps to streamline the review process. By allocating individual roles, the team can effectively manage and coordinate the review activities, leading to a more efficient and successful review.

10. For which of the following would a static analysis tool be MOST useful?

Supporting reviews.

Validating models of the software

Testing code executed in a special test harness.

Enforcement of coding standards.

A static analysis tool is most useful for enforcing coding standards. Static analysis involves analyzing the code without executing it, identifying potential issues or violations of coding standards. By using a static analysis tool, developers can automatically check their code against predefined coding standards and guidelines, ensuring consistency and quality in the codebase. This tool can detect common coding errors, security vulnerabilities, and other issues that may lead to software bugs or maintenance problems. Therefore, it is most beneficial for enforcing coding standards in the development process.

Explanation

A static analysis tool is most useful for enforcing coding standards. Static analysis involves analyzing the code without executing it, identifying potential issues or violations of coding standards. By using a static analysis tool, developers can automatically check their code against predefined coding standards and guidelines, ensuring consistency and quality in the codebase. This tool can detect common coding errors, security vulnerabilities, and other issues that may lead to software bugs or maintenance problems. Therefore, it is most beneficial for enforcing coding standards in the development process.