Prompt 00 Sut

# prompt-00 — System Under Test (SUT)

| Attribute         | Detail                                                            |
| :---------------- | :---------------------------------------------------------------- |
| **Location**      | `08-genai-test-acceleration/01-planning-prompts/prompt-00-sut.md` |
| **Project**       | Tricentis Demo Web Shop                                           |
| **Version**       | 1.0                                                               |
| **STLC Phase**    | Pre-Planning                                                      |
| **GenAI Technique** | Zero-shot prompting · Structured prompt · Iterative HITL        |
| **Reference**     | CT-GenAI GenAI-2.1.1 / GenAI-2.1.3 / GenAI-2.3.2                  |

---

## Artifact Description

The **System Under Test (SUT)** identifies and defines the test object before any STLC activity begins. According to ISTQB CTFL v4.0, the *test object* is "the component or system to be tested."

**Role in STLC:** Enables the Planning phase by providing the baseline for the object to be tested. Without an approved SUT, scope, risks, and test strategy cannot be defined.

**Required data:** Product description, public URL, operating system, environment browser, functional user roles, list of identified modules, and explicit exclusions.

> ⚠️ **Pending Section:** The `Ref. REQ` column in the **Modules in Scope** section will be completed in a second iteration, once `requirements.md` is available and **`REQ`** IDs are assigned. The tester will return to this artifact with those details to close traceability.

---

## Prompt

> 🔗 **Requires:** `system-prompt.md` + `context-rules.md` must be active before running this prompt.

---

### Instruction

Build the `system-under-test.md` artifact in collaboration with the tester using this process:

1. Review the input data provided by the tester.
2. Complete all sections of the Output format that can be filled with this input.
3. For every field that cannot be completed with the received input, ask a clear question to the tester — maximum 3 questions at a time.
4. Wait for the tester's response and incorporate it before proceeding.
5. Repeat until all sections are complete, except for `Ref. REQ`, which remains empty until `requirements.md` is received.

Do not assume data. Do not invent modules. Do not add sections outside the Output format.

---

### Input data

The tester provides in their first message: