New project
Automation from scratch
We design the project structure, pick tools that fit your stack, write the first UI and API scenarios, wire the run into GitLab CI or GitHub Actions, and leave documentation people can actually read.
QA Automation · Python
Test automation that doesn’t need fixing every sprint
Grishin Lab builds test automation frameworks from scratch and puts existing ones back in order: stable scenarios, honest reports, and a CI run on every merge request.
Python · Selenium · Playwright
Remote or relocation
Part-time · hourly or fixed project price
Services
Three ways to work with us
We take a project end to end or join the code that already exists. Scope and format follow your team.
Existing project
Maintenance and growth
We dig into flaky tests, update locators after a redesign, speed up the run, repair broken pipelines, and keep the suite working while your team stays on the product.
Consulting
Audit and advice
We review your current automation project and name what holds it back: what to rewrite, what to drop, where coverage is missing. We can also help pick tools, set up runs in Docker and Kubernetes, or work through one specific problem with your team.
Stack
What we work with every day
Tools follow the project, but the foundation stays the same.
LanguagePython
UI testsSeleniumPlaywright
APIPostman
CI/CDGitLab CIGitHub
InfrastructureDockerKubernetes
Test managementTestRail
Process
How the work runs
Four steps from the first call to tests that run on every merge request.
01
Getting to know the project
We go through the application, the current tests and the pipeline, and ask where it hurts: what breaks most often and what still gets checked by hand before every release.
02
Plan and estimate
We propose what to automate first and name the timeline and format. You see the scope before the start, not along the way.
03
Implementation
We write tests in iterations and show results as they land, not at the end. The code lives in your repository and goes through review under your own rules.
04
CI and handover
Tests run automatically on every merge request, and the report is readable by the whole team, not only QA. Documentation stays behind so the project can run on its own afterwards.
Projects
What we have built
One key project and a result you can measure.
E-commerce platform
Automation framework from scratch
Built the automation project from scratch: structure, the first scenarios, the CI run. From there we kept expanding coverage of the key user journeys as the product grew.
Regression
12 h → 60 min
Second project
Two or three sentences are enough: what the product was, what was done and what changed. Specifics work better here than a list of responsibilities.
Team
Who runs the lab
Dmitry Grishin
Middle QA Engineer
Dmitry Grishin is a test automation engineer with two years of hands-on automation practice and a university degree. He writes Python, works with Selenium and Playwright, and sets up runs in GitLab CI and Kubernetes. He runs every project in the lab himself: you talk to the person who writes the code.
2 years in automation
University degree
Remote or relocation
Contact
Tell us about your project
Write a couple of lines about the product and what is still tested by hand. We will reply with a proposal for what to automate first.
Part-time
Hourly rate
Fixed project price