> For the complete documentation index, see [llms.txt](https://kaze.gitbook.io/qa-theory/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kaze.gitbook.io/qa-theory/readme.md).

# README

[![](https://media.giphy.com/media/l0HlHFRbmaZtBRhXG/giphy.gif)](https://kaze.gitbook.io/qa-theory)

## QA Engineering Theory & Best Practices

The ultimate knowledge base for QA Engineers.\
From Manual Testing fundamentals to Advanced Automation patterns.

[![GitBook](https://img.shields.io/badge/Read_on-GitBook-3b54d1?style=for-the-badge\&logo=gitbook\&logoColor=white) ](https://kaze.gitbook.io/qa-theory)![License](https://img.shields.io/badge/License-MIT-fabc09?style=for-the-badge) ![Last Commit](https://img.shields.io/github/last-commit/KazeKaze93/QA-Theory?style=for-the-badge\&color=success)<br>

> **Note:** This repository contains the **source code** (Markdown files) for my knowledge base. For the best reading experience, please visit the [**GitBook Site**](https://kaze.gitbook.io/qa-theory).

***

### 🗺️ Navigation Map

Here you can find direct links to the source files if you want to contribute or read raw markdown.

| 🧪 Manual Testing                                                                                                                                                                 | 🤖 Automation                                                                                                                                                          | 💻 Programming & Tech                                                                                                          |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| <p><strong>Core Concepts</strong><br>• Testing Types<br>• SDLC & STLC<br>• Test Levels<br><br><strong>Documentation</strong><br>• Test Cases<br>• Bug Reports<br>• Checklists</p> | <p><strong>Frameworks</strong><br>• Selenium WebDriver<br>• Playwright<br>• CI/CD Basics<br><br><strong>Patterns</strong><br>• Page Object Model<br>• Page Factory</p> | <p><strong>Python</strong><br>• Core Syntax<br>• OOP<br>• Fixtures<br><br><strong>Java</strong><br>• Core<br>• Collections</p> |

***

### 🛠️ Topics Covered

<div align="center"><img src="https://skillicons.dev/icons?i=jira,postman,selenium,python,java,docker,git,linux,postgres,jenkins&#x26;theme=dark" alt=""></div>

***

### 🤝 Contribution

Found a typo? Want to add a new topic?

1. Fork this repository.
2. Create a new branch: `git checkout -b feature/new-topic`.
3. Commit your changes.
4. Push to the branch and open a **Pull Request**.

***

Made with ❤️ by [KazeKaze93](https://github.com/KazeKaze93)


---

# 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://kaze.gitbook.io/qa-theory/readme.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.
