Skip to content
Limin Zheng

Testing & Evaluation

Functional & UX testing

Execute agreed user flows and return reproducible findings.

Choose this when
Choose this for independent journey/UX testing; choose AI evaluation & failure diagnosis for AI output evaluation.
Scope unit
A set of journeys across specific device/browser targets
Possible delivery format
Test report, reproduction steps and captures

A brief-first task can still need diagnosis: unreadable scans, an existing design system, or private authenticated journeys.

Prepare a brief →

You send · You receive

What to send

  • URL/build, version and evaluation goals
  • Devices, browsers and priority user journeys
  • Test credentials or sandbox if required, plus permission boundaries

Start by describing the materials you already have; missing details can be added when we agree the scope. Before work begins, we will confirm the materials, permissions and working conditions needed for your specific task.

Possible outputs

  • Coverage checklist and executed test log
  • Issues ranked with reproduction steps and evidence
  • Untested cases and environmental limitations

Key check

Report tested journeys and findings only; no bug-free certification or penetration testing.

Verifiable acceptance · 3
  • Each claimed executed step has evidence
  • High-priority findings are reproducible where possible
  • No-bug result is not presented as proof of perfection

Hypothetical brief & output structure

Illustration · hypothetical

Illustrative example — not a completed client order

The request

Check public pages and mobile browsing flows, then produce actionable UX/functional bugs.

Sample artifacts

  • test-cases.xlsxcoverage
  • issues.mdseverity, repro, screenshots
  • limitations.mduntested areas

File names are illustrative

Other tasks of this kind

  • Test an admin dashboard's CSV import workflow, including invalid files, insufficient permissions and failure feedback.
Output structure / test path

Issue record: screen/device → steps → actual vs expected → evidence → severity

Write a brief from this example →

Scope boundaries

Public no-login journeys can be scoped from a brief; private, payment or write flows require access review first.

Not included by default

  • Penetration, load or invasive security testing
  • High-risk production actions with real funds
  • Fixing all discovered issues unless separately scoped

What affects the quote

Number of flows, platforms, devices and permissions needed.

Actual project references

  • Personal website v6 ↗

    Existing Astro website and design implementation

    Work on my own site, not proof of formal visual delivery or a third-party QA contract.

Self-directed work and published projects demonstrate relevant practice. They are not paid-client delivery records or guarantees for this task.

Start with a short note

Three answers are enough. I will reply with what else is needed and whether a diagnosis comes first. You get a quote before any work starts.

Prepare a brief →

Functional & UX testing

Start with a short note

Three answers are enough. I will reply with what else is needed and whether a diagnosis comes first. You get a quote before any work starts.

What to send
  • URL/build, version and evaluation goals
  • Devices, browsers and priority user journeys
  • Test credentials or sandbox if required, plus permission boundaries
Illustration · hypothetical

Illustrative example — not a completed client order

The request

Check public pages and mobile browsing flows, then produce actionable UX/functional bugs.

Example inputs

  • Public test URL and high-priority journeys
  • Browsers and mobile widths to cover

To start, it helps to mention

  • What page or journey should be tested, and which failure matters most?
  • Which devices, browsers or account states should be covered?

Confirm before work begins: Permission, scoped journeys, test matrix and prohibited actions

Public/de-identified information only. Private access requires separate authorization.

Open email draft →

Preview the text
Services brief — Q01 Functional & UX testing

First contact does not require a complete specification. Unknown fields may be blank or marked unknown.

What do you want to end up with?


What do you already have?


When do you need it? Any budget range?

Select and copy the brief manually if scripting or clipboard access is unavailable.

Public email is a contact starting point. This site has no booking, payment or file-upload service. zhenglimin.design@gmail.com

← Back to category
Prepare a brief →