Aref Farahani

Quality Assurance Engineer

I investigate software behavior to find what others miss.

Product behavior · APIs · Integrations · Automation · Evidence

APIREQUESTUIINTERACTIONAUTOMATIONCHECKCLIENTINPUTSTATEOBSERVE
01Break the state

A small state failure.
A big impact.

INV-001State Management · Regression · Data Integrity
Create
Add member
Save
Reopen
Member missing
Reselect
Duplicate
EXPECTED 1 memberOBSERVED 0 selectedPERSISTED 2 entries

What happened

The editor lost the restored selection while the persisted membership remained.

Reselecting the same member created a duplicate.

The UI forgot.
The persisted state didn’t.

Follow the data

It looked correct all the way…
until it reached the user.

Compose
Preview
Render
Send
DeliveredLiteral output

Hello {{recipient.first_name}},

Outbound

Delivered

Hello {{recipient.first_name}},

Literal output

Expected

Hello [resolved name],

Observed

Hello {{recipient.first_name}},

The editor wasn’t the product.
The delivered artifact was.

Check the context

Same entity.Same state.Different truth.

01 /AuthenticatedSession active

Context / Session

State

Completed

Value

Value A

Entity
02 /PublicAnonymous view

Context / Public

State

Completed

Value

Value B

ENTITY sameSTATE completedCONTEXT differentOUTPUT inconsistent

The data wasn’t wrong.
The context was.

Featured lab

Repository
Intelligence

Turning repository history into testing context.

History

Timeline of change

Connections

Reveal what matters

Context

Drive smarter testing

ChangeThe trigger
FilesWhat changed
ConsumersWho uses it
DependenciesWhat it relies on
TestsWhere it's tested
ImpactWhat could break
QA ContextActionable insights

Change found. Impact understood. Testing context ready.

CommitsTest relevant

Repository Intelligence traces a change through the files it touches, the consumers and dependencies that reference them, the tests and impact analysis that follow, converging into QA context — the actionable testing insight the investigation produces.

How I think

Understand.

Break.

Improve.

Repeat.

My QA process is a continuous loop of curiosity, evidence and improvement.

Curiosity first

Start with questions,
not assumptions.

Evidence driven

Observe deeply,
validate clearly.

Measurable impact

Every cycle should make
the product stronger.

Continuous learning

Every investigation should
make the next one smarter.

Every answer creates
a better question.

The QA mindset is a continuous cycle: question, understand, explore, break, observe, and automate, before returning to question again with a better question than the one that started the cycle.

Let’s talk

Let’s investigate
what
matters.

Open to interesting problems and thoughtful collaborations.

Open to
interesting
problems.

GitHubLinkedInEmail

© 2026 Aref Farahani

Quality engineering

2026