# Tester's Role in Manual Testing

## 🧑‍💻 Tester's Role in Manual Testing 🧑‍💻

Manual testing is the <mark style="background-color:yellow;">process of verifying and validating software applications or systems manually, without the use of automated testing tools or scripts. It involves human testers executing test cases and performing various actions on the software to identify defects, ensure its functionality, and assess its overall quality.</mark>

### 📋 Responsibilities

* Understand requirements and identify test scenarios
* Create detailed, comprehensive test cases
* Set up test environments and data
* Perform various types of manual testing like UI, integration, system, exploratory etc.
* Identify and document defects accurately
* Re-test fixes to confirm issues are resolved
* Regression test new builds for unchanged functionality
* Collaborate with team on status, risks, and mitigations

### ⚙️ Technical Skills

* Understanding of SDLC methodologies and testing types
* Domain knowledge of the application under test
* Ability to write clear, organized test cases
* Good documentation skills for bugs and test results
* Hands-on experience using different environments
* Attention to detail in identifying system issues

### 🤝 Soft Skills

* Analytical thinking and problem-solving
* Patience and persistence
* Creativity for exploratory testing
* Communication skills to collaborate
* Agility to continuously test new features
* Passion for quality and desire to break things


---

# Agent Instructions: 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:

```
GET https://qatesting.gitbook.io/qa/manual-testing/overview/testers-role-in-manual-testing.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
