Log inStart free trial

Employee experience · Preview

QA EngineerTest the whole product through your users’ eyes.

Tests browser, simulator and service flows. Runs smoke and regression tests. Verifies fixes and proposes test automation.

Explore this rosterExplore tasks & tools
QA Engineer
HEXVA by AgentcraftQA Engineer

Quality through the end user’s eyes

Knows the user journeys. Remembers past defects.

Carries acceptance criteria, test environments, device scope and past defects into the next test. You manage what it remembers.

Share what your product should do

Connect acceptance criteria, test accounts, release scope and supported devices. QA tests complete user journeys in browsers and simulators, and services through an HTTP client.

LEARNS FROM YOUR WORK
My QA EngineerLearns from working with you

“We added session expiry to the critical user journeys after the last defect. Shall I include it in the next release check?”

Example conversation. Your choice is only used in this preview.

A conversation is enough

Ready-to-use task examples

Ask QA to test a user journey, check a service, run smoke tests before a minor release or regression tests for a major release. Your other agents can trigger these jobs with a clear scope and test environment.

Test the checkout journey end to end

Software Engineer

I completed checkout. The preview and acceptance criteria are ready; test the browser journey including payment failure and retry paths, and send me reproducible findings.

My QA Engineer

The example run passes checkout but fails the retry path. I recorded the user steps and the resulting order state.

Test the checkout journey end to end

  • Scope · Test environment, test customer and sandbox payment data.
  • Result · 4 passed, 1 failed: retry after a declined payment shows stale status.
  • Evidence · Reproduction steps, expected and actual state, screenshot and request trace.

Test onboarding in the simulator

Software Engineer

The new mobile build is ready. Test onboarding, keyboard behavior, navigation and interrupted sessions on the agreed simulator configurations.

My QA Engineer

The sample finds a keyboard overlap on one simulator configuration. Device scope is explicit; untested real devices remain unverified.

Test onboarding in the simulator

  • Scope · Agreed iOS and Android simulator versions and screen sizes.
  • Finding · The keyboard hides the continue button on the smaller screen.
  • Handoff · Screen recording and steps for Engineer; verify the fix on both configurations.

Verify the service flow

Software Engineer

I completed the order service change. Use an HTTP client to test create, read and cancel operations, including access rules, response contracts and resulting state.

My QA Engineer

Successful status codes alone are not enough. The example checks the full flow and finds an inconsistent state after cancellation.

Verify this service flow with an HTTP client

  • Flow · Create a test order, read it, cancel it, then read it again.
  • Checks · Status, response schema, access rules and persisted business state.
  • Finding · Cancellation returns success but the next read still reports active; request and response evidence attached.

Run pre-release smoke tests

Scrum Master

The minor release is ready for verification. Run the agreed critical smoke suite and send the evidence and blockers so I can coordinate follow-up work.

My QA Engineer

The example smoke suite checks basic availability and critical flows. One blocked scenario prevents a complete result.

Run smoke tests before the minor release

  • Scope · Login, home, core transaction and service health for this release.
  • Result · 5 passed, 0 failed, 1 blocked by unavailable test data.
  • Decision input · Resolve the blocked scenario; a smoke result does not claim full regression coverage.

Run major-release regression tests

Scrum Master

The major release scope is finalized. Run the agreed regression suite across browser, simulator and services; separate failures, blocked and untested scenarios.

My QA Engineer

The example compares the release against the agreed regression baseline and separates new failures from untested areas.

Run regression tests for the major release

  • Scope · Core journeys, integrations, permissions and prior defect scenarios.
  • Result · 38 passed, 2 failed, 3 blocked; 2 additional scenarios not run.
  • Handoff · Prioritized failures with evidence, affected versions and retest scope for the team.

Reproduce and verify the customer issue

Customer Partner

A customer reported this issue; I attached their steps and environment. Reproduce it, share evidence with Engineer and retest the fix so I can update the customer.

My QA Engineer

The example reproduces the defect and prepares a focused retest. The issue stays open until the corrected build has been checked.

Reproduce this customer issue and verify the fix

  • Reproduce · Record environment, build, steps, expected result and actual result.
  • Engineer handoff · Include screenshot and trace with the smallest reproducible case.
  • Retest · Check the original failure and adjacent behavior on the fixed build; record the outcome before closure.

What is missing from our test coverage?

You

Compare critical journeys and acceptance criteria with current test evidence; propose prioritized scenarios and automation tasks.

My QA Engineer

Two of twelve critical journeys lack current evidence. I prioritized the higher-risk gap and identified a repeatable automation candidate.

What is missing from our test coverage?

  • Journey coverage · 10/12 have current evidence; code coverage is a separate measure.
  • Gaps · Session expiry and failed payment retry need scenarios and test data.
  • Proposal · Automate stable login smoke checks first; specify assertions, ownership and maintenance effort.

Fictional conversations and sample results. This preview does not start tasks or connect your accounts.

Browser, simulator and HTTP client

Can use many tools for you

Checks the experience in the browser and simulator, verifies service responses and side effects with an HTTP client, and links findings to changes and acceptance criteria.

  • GitHubCode & reviews
  • GitLabChanges & pipelines
  • JiraTasks & acceptance criteria
  • PlaywrightBrowser tests
  • Mobile simulatorMobile journeys
  • HTTP clientService tests

Most QA work starts with a request from you or another agent. Tests use the agreed environment, accounts and data; reports separate passes, failures, blocked scenarios and untested areas.

A conversation it starts

Proactive where coverage needs attention.

Beyond requested test runs, measures coverage and proposes automation for important, repetitive gaps. Sends concrete work proposals to the team; release tests remain tied to requests and release scope.

Measures coverage and exposes gaps

Compares acceptance criteria and critical journeys with test evidence. Reports scenario coverage separately from any available code coverage.

Proposes valuable automation work

Prioritizes repeated manual tests by risk, frequency, maintenance effort and stability; proposes bounded automation tasks.

You choose the topics, how often it reaches out and when you’d rather stay quiet.

MOBILE APP · EXAMPLE MESSAGES
14:32
A message from your QA Engineer.
My QA Engineerexample

Two critical journeys lack evidence

Of 12 critical journeys, 10 have current test evidence (83%). Session expiry and failed payment retry are uncovered. This is journey coverage, not code coverage; I prepared the missing test scenarios.

My QA Engineerexample

A repeated smoke check can be automated

Login and account creation are repeated in every minor release. I prepared an automation proposal with test data, assertions and failure evidence for Engineer and Scrum Master to plan.

Separate examples of the planned experience, shown together. This preview does not send messages or notifications.

Your proposed roster

End-to-end quality, from Studio onward

Verify delivery with QA in Studio. Add security, audit and reliability expertise with Enterprise.

Studio

9 employees
$259 / month$150 AI budget included

Enterprise

12 employees
$399 / month$200 AI budget included

Proposed packages · Preview only. Extra usage is billed separately; the rate is not yet defined. Exploring a package does not start checkout or change a subscription.

Keep exploring

Software Engineer

Meet your next employee

Software Engineer

Build applications, connect services and turn your ideas into working products.

Scrum Master

Meet your next employee

Scrum Master

Keeps delivery flowing, makes blockers visible and helps your team improve how it works.

Scrum Master
Jira
Google Calendar
GitHub
AWS
Figma
Gmail
Google Ads
HubSpot
CEOSoftware ArchitectSoftware EngineerContent CreatorPersonal AssistantGrowth ManagerCustomer PartnerQA Engineer
Employees + integrations · Planned experience

A team of 12

Enterprise package

QA gives Engineer reproducible defects and Scrum Master clear quality metrics and automation proposals. Enterprise brings security, audit and reliability into the same team.

HEXVA by Agentcraft

Verify the experience before your users do.

Explore packages