Localization and Timezone Exploration Charter Prompt

This prompt is for QA engineers and exploratory testers who need to generate a time-boxed, mission-driven test charter specifically targeting locale-specific behavior, timezone handling, and cultural formatting. The ideal user is someone who already has a feature or product surface that must behave correctly across multiple regions, languages, or time zones, and who needs a structured plan for unscripted human investigation. You should use this prompt when you have access to the locale configuration context—such as supported locales, date/time format specifications, and currency display rules—and you need to translate that context into a focused, 60- to 120-minute exploratory testing session with clear investigation targets and oracle heuristics.

The prompt is not a replacement for automated i18n test suites, translation quality review, or linguistic correctness checks. It is a planning tool for human investigation. Do not use it when you need to verify every string translation, when you require pixel-perfect layout validation across hundreds of locales, or when the work is better served by a scripted regression suite. The charter it produces will help a tester probe for systemic issues—like a date picker breaking on DST transition days, an RTL layout causing text truncation in Arabic, or a currency formatter displaying the wrong symbol after a locale switch—but it will not execute those tests automatically. The output is a mission, not a script.

Before using this prompt, gather the specific locale configuration details: which locales are in scope, what timezone behavior is expected (especially around DST transitions), and any known cultural formatting rules for dates, numbers, currencies, and names. The prompt requires this context to produce region-specific investigation targets rather than generic 'test all locales' advice. After generating the charter, use it to guide a real exploratory testing session, capture observations in the provided session notes scaffold, and debrief afterward to identify coverage gaps. Avoid the temptation to treat the charter as a checklist; its value is in focusing attention on high-risk localization and timezone boundaries that scripted tests often miss.

This prompt template produces a time-boxed exploratory test charter focused on localization and timezone behavior. It is designed to be copied directly into your AI tool, with square-bracket placeholders replaced by your specific application context. The charter output will include a clear mission statement, specific investigation targets for cultural formatting and temporal edge cases, oracle heuristics for determining correct behavior, and a structured note-taking scaffold for the tester to use during the session.

textCopy
You are an exploratory test architect specializing in internationalization, localization, and timezone-aware systems. Your task is to generate a structured exploratory test charter based on the provided context.

## INPUTS
- Feature Under Test: [FEATURE_NAME_AND_DESCRIPTION]
- Supported Locales: [LIST_OF_LOCALES]
- Supported Timezones: [LIST_OF_TIMEZONES]
- Known Risk Areas: [LIST_OF_KNOWN_RISKS_OR_RECENT_CHANGES]
- Session Duration: [TIMEBOX_IN_MINUTES]

## CONSTRAINTS
- Focus on locale-specific formatting, timezone transitions, and cultural conventions.
- Do not duplicate standard functional test cases; target edge cases and implicit assumptions.
- Every investigation target must include a clear oracle heuristic: how will the tester know if the behavior is correct or incorrect?

## OUTPUT_SCHEMA
{
  "charter_title": "string",
  "mission": "string (one-sentence mission for the session)",
  "timebox_minutes": "number",
  "investigation_targets": [
    {
      "target_id": "string",
      "category": "DST Transition | RTL Layout | Currency Display | Date Parsing | Translation Truncation | Collation | Number Formatting | Timezone Conversion | Other",
      "description": "string (specific scenario or boundary to explore)",
      "oracle_heuristic": "string (how to judge pass/fail)",
      "priority": "High | Medium | Low"
    }
  ],
  "session_notes_scaffold": {
    "observations": "string (fillable area)",
    "bugs_found": "string (fillable area)",
    "risks_identified": "string (fillable area)",
    "coverage_assessment": "string (fillable area)",
    "follow_up_charters": "string (fillable area)"
  }
}

## INSTRUCTIONS
1. Analyze the feature, locales, and timezones to identify high-risk formatting and temporal boundaries.
2. Generate investigation targets that probe DST transitions, RTL layout shifts, currency symbol placement, date string parsing ambiguity, and text expansion/truncation in translated strings.
3. For each target, define a concrete oracle heuristic that does not require access to source code.
4. Ensure the charter fits within the specified timebox.
5. Output only valid JSON matching the schema above.

To adapt this template, replace the placeholders in the INPUTS section with your specific context. The [LIST_OF_LOCALES] should include both the base language and region variants where relevant (e.g., en-US, en-GB, ar-EG). The [LIST_OF_TIMEZONES] should include zones with and without DST to ensure transition coverage. After generating the charter, review the investigation targets to confirm they are specific enough for a tester to execute without additional clarification. For high-risk financial or healthcare applications, add a human review step before the charter is assigned to a tester to validate that the oracle heuristics align with regulatory or compliance expectations.

This prompt is designed to be called programmatically as part of a test planning pipeline or a QA engineer's interactive tool. The primary input is a locale configuration context—typically a structured JSON object containing the target locale code, timezone identifier, supported currencies, date formats, and any known UI surface areas (e.g., checkout flow, profile settings, dashboard widgets). The application layer should assemble this context from a test environment configuration service or a locale registry before injecting it into the [LOCALE_CONFIGURATION] placeholder. Do not pass raw, unvalidated user input directly into the locale configuration slot; the harness should verify that the locale code follows IETF BCP 47 format and that the timezone is a valid IANA timezone identifier before prompt assembly.

The output of this prompt is a structured exploratory test charter. To make this usable in a test management system, the harness should parse the model's response against a defined JSON schema. The expected output shape includes: charter_id, mission_statement, timebox_minutes, investigation_targets (an array of objects with area, risk, and oracle_heuristic fields), locale_specific_risks (covering DST transitions, RTL layout, currency formatting, date parsing, and translation truncation), and session_notes_scaffold. Implement a post-processing validator that checks for required fields, confirms that investigation targets are non-empty, and verifies that locale-specific risks reference the provided locale configuration. If validation fails, retry once with the same prompt and append the validation errors as a [CONSTRAINTS] block. If the second attempt also fails, log the failure and route the request to a human QA lead for manual charter creation.

For model selection, use a model with strong structured output capabilities and a context window large enough to hold the full locale configuration plus the prompt template. GPT-4o, Claude 3.5 Sonnet, or Gemini 1.5 Pro are appropriate choices. Enable structured output mode (JSON mode or function calling with a strict schema) to reduce parsing errors. Log every generated charter with the input locale configuration, model version, and validation result for auditability. When the charter targets regulated financial or healthcare locales, add a mandatory human review step before the charter is assigned to a tester. Avoid using this prompt for locales not represented in the configuration input; the model cannot invent accurate locale-specific risks without evidence, and doing so produces plausible but incorrect investigation targets.