ความครอบคลุมโค้ดและการวิเคราะห์แบบสถิต

Ensuring high-quality code is crucial for reliable software. In this lesson, we'll explore two key practices:

• Code Coverage: How much of your code is tested?
• Static Analysis: Does your code follow best practices and style guidelines?

These tools help you write better, more maintainable code by identifying issues early.

Code coverage measures the percentage of your source code that is executed by your tests. It's a metric that tells you how thoroughly your tests are exercising your application's logic.

While high coverage doesn't guarantee bug-free code, it indicates a good foundation of testing and helps pinpoint untested areas.

JaCoCo (Java Code Coverage) is a popular and free code coverage library for Java projects, which works seamlessly with Groovy. It integrates exceptionally well with build tools like Gradle.

JaCoCo generates detailed reports showing which parts of your code are covered by tests and which are not, helping you identify gaps.

To integrate JaCoCo, apply its plugin in your build.gradle. This automatically adds tasks and allows you to configure report generation, specifying formats like HTML and XML.

We'll also include basic Java/JUnit setup for context.

Once configured in build.gradle, you can run the JaCoCo test report task from your terminal. This command will execute your tests and then generate the coverage report.

The interactive HTML report can be found in build/reports/jacoco/test/html/index.html.

Static analysis is the examination of your code without actually executing it. It's like a linter or a spell checker for your code, identifying potential issues before runtime.

It helps identify problems such as:

• Coding standard violations
• Potential bugs (e.g., null pointer dereferences)
• Security vulnerabilities

Checkstyle is a development tool that helps programmers write Java (and often Groovy) code that adheres to a coding standard. It automates the process of checking code against a predefined set of rules.

By catching style and common error violations early, it improves code consistency and readability.

To integrate Checkstyle, apply its plugin in your build.gradle. You'll typically point it to a ruleset file, often located within your project's config/checkstyle directory, or use a default.

This configuration also ensures reports are generated in useful formats like HTML and XML.

After configuration, you can run Checkstyle from your terminal. It will analyze your source code and generate reports without compiling or running tests.

You can find the HTML report in build/reports/checkstyle/main.html for your main source code.

You've learned about two powerful tools for code quality. Let's test your understanding.

In this lesson, you learned how to integrate essential quality assurance tools into your Gradle build:

• JaCoCo: For measuring code coverage, showing how much of your code is exercised by tests.
• Checkstyle: For static analysis, enforcing coding standards and identifying potential issues without running the code.

These tools are vital for maintaining high-quality, readable, and maintainable software.