Launch readiness review
You have a release coming up and need to know where to focus.
- Review of agreed critical user journeys
- Prioritized findings with reproduction steps
- Release risks and recommended next checks
Independent consultant · Las Vegas / Remote
Before you ship,
let’s check
the details.
I’m Gunel. I help product teams test important workflows, make sense of requirements, and check that the data tells the same story as the screen.
Tools behind the workJava / TestNGCucumber / GherkinPostmanSQLJira
Ways to work together
Know what needs fixing.
Know what comes next.
For product teams, startups, and agencies that need a careful second look or hands-on testing support. We agree on the workflows, access, and deliverables before work begins.
QA & regression sprint
You need reliable coverage as your product changes.
- Functional and regression test coverage
- Java / BDD automation where it fits your stack
- Defect tracking, fix verification, and handoff notes
UAT & business-rule validation
Everyone needs the same understanding of “done.”
- Requirements and acceptance-criteria review
- Business scenarios and traceable test cases
- UAT issue log and acceptance summary
API & data quality review
The screen looks right. You need to know what happened underneath.
- Postman request and response checks
- SQL validation of agreed data and business rules
- Mismatch findings and repeatable validation steps
Start with one important workflow.
For a first engagement, we can focus on signup, onboarding, or another release-critical journey. You receive a prioritized issue report, supporting evidence, and a handoff discussion. Access, coverage, timing, and price are agreed before testing begins.
Project-based or ongoing support. Scope and pricing are agreed after a short review of your needs.
Selected work
Open the work.
Follow the reasoning.
Professional experience explains the context. The independent sample below gives you something you can inspect and run.
Independent work sample / synthetic data
One request.
Four ways it can go wrong.
From acceptance criteria to Java checks, API assertions, and stored-data comparisons. A fictional onboarding workflow makes the decisions visible without exposing employer systems. Start with the findings, then inspect the source and execution output.
Business rulesJavaGherkinPostmanSQL
Executed reference-model checks
6 → 8
Passing Java checks before and after correcting two intentionally seeded defects. Eight checks total.
Read the execution output ↗What a client receives
A finding that explains the risk, how to reproduce it, what should happen, and what needs retesting.
Read a sample defect report ↗What a passing test doesn’t prove
A release decision needs to account for untested risks. The sample includes a clear boundary between model validation and production readiness.
Read the release recommendation ↗Professional background
Business context.
Hands-on testing.
LexisNexis Risk Solutions
San Jose office · 2022–2025
Business Analyst / Automation Engineer
I worked across requirements and testing: understanding expected behavior, automating front-end scenarios, and checking API responses and backend data.
- Used Java and TestNG alongside Cucumber and Gherkin in a BDD framework for front-end automation.
- Used Postman to send requests through APIs, retrieve information, and check the returned output.
- Validated backend data with SQL and compared results with business expectations.
- Worked with business and technical teams on requirements, test scenarios, defects, and UAT.
Working together
No mystery around the next step.
Start with the risk
Tell me what is changing, who uses it, and what would hurt if it failed. We define the workflows and scope.
Make findings actionable
I document what I tested, what happened, and how to reproduce the issue. Priority follows business impact.
Leave a useful handoff
You get the findings, verification status, remaining questions, and a practical recommendation for what comes next.
A little about me
I’m comfortable in the
meeting and in the details.
My background connects business analysis, quality engineering, and technical project delivery. I enjoy finding the point where a requirement sounds clear to one person and means something different to another.
I’m based in Las Vegas and work with teams remotely. Clear documentation and straightforward communication are central to how I work.