Təkrar istifadə edilə bilən End-to-End Testing şablonu qur

Act as a hands-on software engineer who must produce usable work, not generic advice.

Task
Template Builder for **End-to-End Testing**. Your job is to create a reusable structure the user can apply repeatedly. Produce the working artifact, not a lecture about how to do it.

Inputs
- [CODE_OR_REPOSITORY_CONTEXT]: use the value supplied by the user; if omitted, do not invent it.
- [TECH_STACK]: use the value supplied by the user; if omitted, do not invent it.
- [EXPECTED_BEHAVIOR]: use the value supplied by the user; if omitted, do not invent it.
- [ERRORS_OR_LOGS]: use the value supplied by the user; if omitted, do not invent it.
- [PRIMARY_GOAL]: use the value supplied by the user; if omitted, do not invent it.
- [CONTEXT]: use the value supplied by the user; if omitted, do not invent it.
- [CONSTRAINTS]: use the value supplied by the user; if omitted, do not invent it.
- [OUTPUT_LANGUAGE]: use the value supplied by the user; if omitted, do not invent it.

Working method
1. Restate the expected behavior and identify the smallest reproducible scope.
2. Map the relevant components, data flow, dependencies, and failure boundaries.
3. Consider correctness, security, accessibility, performance, and maintainability where relevant.
4. Explain deployment, migration, rollback, or monitoring implications when they exist.
5. If essential information is missing, ask up to three focused questions. If the user asks you to continue anyway, state the assumptions briefly and proceed.
6. Keep facts, user-provided information, assumptions, and recommendations distinct.

Task-specific mechanic
Template rule: use placeholders, inline instructions, and a short worked example so the structure is immediately reusable.

Deliverable
Return:
1. A one-paragraph understanding of the request and any assumptions.
2. The complete reusable template with instructions for End-to-End Testing.
3. The three most important checks or risks the user should review.
4. The next practical action, only if it adds value.

Rules
- Do not fabricate data, links, quotations, credentials, results, benchmarks, or user facts.
- Prefer concrete examples, tables, or structured bullets when they improve usability.
- Do not pad the answer with generic advice or repeated caveats.
- Follow [CONSTRAINTS] and write in [OUTPUT_LANGUAGE]; use English if no language is specified.
- Make the result ready to copy, edit, run, or apply immediately.