Orqestria Download
← Back to Full workflow

Skill · Version 1.0.0

Technical research for QA

Checks version-matched primary sources so tests distinguish application defects from documented platform behavior.

technical-research-for-qa

Workflow agents using this skill

See how it helps

When is it useful?

Use when a browser, database or external API detail determines whether a reported issue is a bug.

What does it help you do?

  • Narrows research to the exact testing uncertainty.
  • Matches installed versions to official documentation, specifications and known upstream issues.
  • Converts findings into targeted cases and traceable defect evidence.

Try asking this

Research the installed database's concurrent-write behavior and design a test showing how our application should handle contention. Create two conflicting writes using the installed engine version. Distinguish its documented locking behavior from an application failure to handle that response.

Detailed documentation

Read the skill’s original instructions, examples and checks in their authored language.

Details…Show less

Technical Research for QA

When testing touches external APIs, browser Web APIs, framework lifecycle hooks, or version-specific libraries, check authoritative sources so QA findings distinguish real application bugs from documented platform behavior.

Workflow

  1. Formulate a focused QA research question:
    • Keep research strictly scoped to the testing question at hand (e.g., "How does SQLite handle concurrent BEGIN IMMEDIATE transactions under WAL mode?" or "Does Safari support ClipboardItem with async Promises inside user gesture handlers?").
  2. Consult primary, version-matched sources:
    • Check the exact version installed in the project (package.json, lockfiles, runtime version) against:
      • Official framework/library documentation and changelogs.
      • MDN / W3C / WHATWG / IETF specifications for web, HTTP, and browser behavior.
      • Upstream GitHub issue trackers for known platform bugs or version-specific edge cases.
  3. Apply findings to test design and bug triage:
    • Known upstream / browser quirk: If a browser or external SDK has a documented limitation (e.g., iOS Safari viewport resize behavior on virtual keyboard open, or a third-party webhook delivering events at-least-once), design a targeted test case to verify our application handles that reality gracefully.
    • Cite primary evidence: When reporting a version-specific or spec-compliance bug, include the exact specification rule or official documentation reference so developers can see immediately why the current behavior is invalid.
    • For deep multi-repo technology evaluations or architectural replacements, coordinate with the technology researcher (Radar).

Included files 1

  • SKILL.md