> For the complete documentation index, see [llms.txt](https://docs.idew.org/project-video-game/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.idew.org/project-video-game/project-instructions/2-design-and-build-solution/2.7-internal-playtesting.md).

# 2.7 Internal Playtesting

{% hint style="danger" %}
**UPDATE IN PROGRESS:** Placeholder - revised assignment still in progress.
{% endhint %}

{% tabs %}
{% tab title="✓ TASK" %}
Throughout the development of your team's game code and assets, your team should periodically playtest your game in progress to ensure newly-added features are functioning as intended — and to identify any issues that should be fixed.

Your team's Programming Lead should be testing the game as new code and assets are added. However, it will be helpful to have your team's Art Lead or Research Lead act as another playtester:

* Your team's Art Lead could playtest the game to verify that newly-added assets (animated sprites, sound effects, etc.) are functioning as intended. For example, are the sprites the correct size, are the sprite's animations playing properly, etc.
* Your team's Research Lead could playtest the game more thoroughly — by not only testing new features but also ensuring existing features still work.

Communication between your team members will be important, so the internal playtesting can focus on specific game features that need to be tested, while also providing specific feedback on any issues that are detected.

### **❏ Deliverable**

Submit your team's ...
{% endtab %}

{% tab title="★ RUBRIC" %}

| **✓- Below Standard** | **✓ Meets Standard** | **✓+ Exceeds Standard** |
| --------------------- | -------------------- | ----------------------- |
| Description           | Description          | Description             |
| {% endtab %}          |                      |                         |
| {% endtabs %}         |                      |                         |


---

# 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://docs.idew.org/project-video-game/project-instructions/2-design-and-build-solution/2.7-internal-playtesting.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.