Static Test Techniques

Reviewed by Editorial Team
The ProProfs editorial team is comprised of experienced subject matter experts. They've collectively created over 10,000 quizzes and lessons, serving over 100 million users. Our team includes in-house content moderators and subject matter experts, as well as a global network of rigorously trained contributors. All adhere to our comprehensive editorial guidelines, ensuring the delivery of high-quality content.
Learn about Our Editorial Process
| By SarojaG
S
SarojaG
Community Contributor
Quizzes Created: 2 | Total Attempts: 17,565
| Attempts: 2,948
Quiz Flashcard
SettingsSettings
Please wait...
  • 1/9 Questions

    Which is not a type of review?

    • Walkthrough
    • Inspection
    • Informal review
    • Management approval
Please wait...
About This Quiz

Certified Tester- Foundation Level Exam
-----------------------------------------------------------
ISTQB Chapter 3- Static Test Techniques

Static Test Techniques - Quiz

Quiz Preview

  • 2. 

    Which of the following artifacts can be examined by using review techniques?

    • Software code

    • Requirements specification

    • Test designs

    • All of the above

    Correct Answer
    A. All of the above
    Explanation
    Review techniques can be used to examine all of the artifacts mentioned in the question, including software code, requirements specifications, and test designs. Reviewing software code helps identify any errors or issues in the code, while reviewing requirements specifications ensures that all necessary requirements are included and properly documented. Similarly, reviewing test designs helps verify that the test cases are comprehensive and cover all aspects of the system being tested. Therefore, all of these artifacts can benefit from review techniques to improve their quality and effectiveness.

    Rate this question:

  • 3. 

    What is the main difference between a walkthrough and an inspection?

    • An inspection is led by the authors, whilst a walk through is led by a trained moderator.

    • An inspection has a trained leader, whilst a walk through has no leader.

    • Authors are not present during inspections, whilst they are during walkthroughs.

    • A walkthrough is led by the author, whilst an inspection is led by a trained moderator.

    Correct Answer
    A. A walkthrough is led by the author, whilst an inspection is led by a trained moderator.
    Explanation
    The main difference between a walkthrough and an inspection is the leadership role. In a walkthrough, the author of the work being reviewed leads the process, while in an inspection, a trained moderator takes on the leadership role. This means that in a walkthrough, the author has more control and can provide more context and explanations, while in an inspection, the trained moderator brings objectivity and impartiality to the review process.

    Rate this question:

  • 4. 

    Which statement about the function of a static analysis tool is true?

    • Gives quality information about the code without executing it.

    • Checks expected results against actual results.

    • Can detect memory leaks.

    • Gives information about what code has and has not been exercised.

    Correct Answer
    A. Gives quality information about the code without executing it.
    Explanation
    A static analysis tool is designed to analyze the source code of a program without actually executing it. It examines the code for potential errors, bugs, or vulnerabilities and provides information about the quality of the code. By analyzing the code statically, it can detect issues such as code complexity, coding standards violations, potential security vulnerabilities, and other code quality metrics. This helps developers identify and fix problems in the code before it is executed, leading to improved software quality.

    Rate this question:

  • 5. 

    Which of the following characteristics and types of review processes belong together? 1. Led by the author 2. Undocumented 3. No management participation 4. Led by a trained moderator or leader 5. Uses entry and exit criteria s. Inspection t. Technical 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

    • Cs = 1 and 5, t = 3, u = 2, v = 4

    • s = 5, t = 4, u = 3, v = 1 and 2

    Correct Answer
    A. s = 4 and 5, t = 3, u = 2, v = 1
    Explanation
    The characteristics and types of review processes that belong together are as follows:
    - s = 4 and 5: This means that the review process includes being led by a trained moderator or leader and using entry and exit criteria.
    - t = 3: This means that the review process is undocumented.
    - u = 2: This means that the review process has no management participation.
    - v = 1: This means that the review process is a walkthrough.

    Rate this question:

  • 6. 

    What statement about reviews is true?

    • Inspections are led by a trained moderator, whereas technical reviews are not necessarily.

    • Technical reviews are led by a trained leader, inspections are not.

    • In a walkthrough, the author does not attend.

    • Participants for a walkthrough always need to be thoroughly trained.

    Correct Answer
    A. Inspections are led by a trained moderator, whereas technical reviews are not necessarily.
    Explanation
    In the context of reviews, the statement "Inspections are led by a trained moderator, whereas technical reviews are not necessarily" is true. Inspections are a formal type of review where a trained moderator leads the process. The moderator ensures that the review follows a defined set of rules and guidelines. On the other hand, technical reviews can be less formal and may not require a trained leader. While it is recommended to have a trained leader for technical reviews, it is not always necessary.

    Rate this question:

  • 7. 

    What statement about static analysis is true?

    • With static analysis, defects can be found that are difficult to find with dynamic testing.

    • Compiling is not a form of static analysis.

    • When properly performed, static analysis makes functional testing redundant.

    • Static analysis finds all faults.

    Correct Answer
    A. With static analysis, defects can be found that are difficult to find with dynamic testing.
    Explanation
    Static analysis is a technique used to analyze software code without executing it. It helps in identifying defects and vulnerabilities in the code that may not be easily detected through dynamic testing, which involves running the software. Static analysis can detect issues such as coding errors, security vulnerabilities, and performance bottlenecks. It complements dynamic testing by providing an additional layer of scrutiny to ensure the quality and reliability of the software. However, it is important to note that static analysis cannot find all faults, as some defects may only manifest during runtime.

    Rate this question:

  • 8. 

    Which of the following statements about early test design are true and which are false? 1. Defects found during early test design are more expensive to fix. 2. Early test design can find defects. 3. Early test design can cause changes to the requirements. 4. Early test design takes more effort.

    • 1 and 3 are true. 2 and 4 are false.

    • 2 is true. 1, 3 and 4 are false.

    • 2 and 3 are true. 1 and 4 are false.

    • 2, 3 and 4 are true. 1 is false.

    Correct Answer
    A. 2 and 3 are true. 1 and 4 are false.
    Explanation
    Defects found during early test design are more expensive to fix because they are identified and addressed before the development process progresses further, saving time and resources. Early test design can also lead to changes in requirements as defects are discovered and addressed. However, it does not necessarily take more effort, as identifying and fixing defects early can prevent larger issues later on. Therefore, statement 1 is false and statements 2 and 3 are true. Statement 4 is false as it contradicts the explanation.

    Rate this question:

  • 9. 

    Static code analysis typically identifies all but one of the following problems. Which is it?

    • Unreachable code

    • Undeclared variables

    • Faults in the requirements

    • Too few comments

    Correct Answer
    A. Faults in the requirements
    Explanation
    Static code analysis - will identify
    unreachable code, undeclared variables, too few comments in the code.
    But it cannot identify Faults in the requirements since it analyses only the code not the requirements.

    Rate this question:

Quiz Review Timeline (Updated): Mar 22, 2023 +

Our quizzes are rigorously reviewed, monitored and continuously updated by our expert board to maintain accuracy, relevance, and timeliness.

  • Current Version
  • Mar 22, 2023
    Quiz Edited by
    ProProfs Editorial Team
  • Nov 15, 2010
    Quiz Created by
    SarojaG
Back to Top Back to top
Advertisement
×

Wait!
Here's an interesting quiz for you.

We have other quizzes matching your interest.