For students
Pick a brief below, or bring the problem statement your department handed you. We architect it with you, review every commit, deploy it to a real URL, and rehearse the viva until no question surprises you.
See student support4 scoped briefs
2 mini · 2 major
Most student QA projects are twenty recorded happy-path scripts that pass, prove nothing, and fall apart the first time CI runs them in parallel. This domain treats testing as engineering: cases aimed where the software is most likely to break, locators and waits that survive a UI change, coverage you can point at — a matrix naming every journey as tested or explicitly not — and flake handled deliberately instead of by retrying until green. A suite is worth exactly what it catches, so every project here ends with a defect log: reproducible steps and evidence, not a screenshot of a passing run.
Two audiences, one engineering standard
Pick a brief below, or bring the problem statement your department handed you. We architect it with you, review every commit, deploy it to a real URL, and rehearse the viva until no question surprises you.
See student supportTest strategy and automation frameworks, turning a manual regression pass into a CI gate, stabilising suites the team has learned to ignore, API and contract coverage, load tests with thresholds that fail the build, and regression gates for LLM features someone else has already built.
Discuss a company buildMini projects
Three to four weeks. Narrow enough to finish, deep enough that you learn the decision that actually matters.
A cross-browser end-to-end suite over a live app with a page-object structure — the hard part is making it pass twenty runs in a row, not once.
You walk away with
A Java regression suite a non-engineer can read and sign off: Gherkin scenarios, thread-safe parallel execution, and test data seeded over the API instead of clicked into existence.
You walk away with
Major projects
Ten to twelve weeks. Architecture, trade-offs, failure modes, deployment, and evidence—the project that carries an interview.
One framework over an app you deploy yourself — UI, API and consumer-driven contract layers sharing a data factory, a sharded CI matrix, flake quarantine, and a k6 load test whose SLO thresholds fail the build.
You walk away with
The app already exists — the RAG chatbot from AI & LLM Applications, or any deployed LLM app you own; building it is out of scope. This is the layer that domain does not ship: a versioned golden set, a calibrated judge, and a CI gate that blocks a prompt change that regresses quality.
You walk away with
Explore more
Bring us a product brief, a business problem, or a final-year project. We’ll turn it into a clear scope, a working build, and a handover you fully own.
Prefer email? info@tenzok.in