> For the complete documentation index, see [llms.txt](https://help.aikido.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aikido.dev/docs/docs-ja/autofix-to/faq/how-are-patches-tested.md).

# パッチはどのようにテストされるか

これは両方に適用されます **Aikido Images** および **Aikido Libraries**.

各パッチは、適用前後の両方で自動および人手による複数のテスト層を経て、破壊的変更、リグレッション、または追加の脆弱性が導入されるリスクを最小限に抑えます。

自動テストには以下が含まれます。

* 単体テストおよび統合テスト
* 機能テスト
* スモークテスト
* インストールテスト
* ファズテスト
* セキュリティテスト
* PoC / エクスプロイトの検証

各パッチは、その後、リリース前に人間のセキュリティエンジニアによって個別にレビューされ、再検証されます。


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.aikido.dev/docs/docs-ja/autofix-to/faq/how-are-patches-tested.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.