QA Head / Senior Software Engineer in Test
Mentor @ getmentor.dev · Lecturer @ qa.guru

I build test automation infrastructure, CI/CD quality gates, reporting systems, and engineering practices that help teams ship faster without losing control over quality.

My focus is designing reliable quality feedback loops for engineering teams:

• test automation architecture
• CI/CD quality gates
• Allure reporting and test observability
• Dockerized test execution
• Selenium / Pytest / Java automation templates
• flaky test diagnostics
• test data and environment strategy
• mentoring and QA engineering standards

I help engineering teams turn testing into an integrated engineering system inside CI/CD.

This usually includes:

• designing maintainable automation frameworks
• integrating tests into delivery pipelines
• improving visibility of test results and trends
• reducing flaky and low-signal checks
• building reusable templates and tooling
• mentoring QA engineers and automation specialists

A GitLab CI/CD reporting solution for preserving Allure history across pipeline runs and publishing trend reports on GitLab Pages.

Useful for teams that need:

• historical visibility of test results
• report publishing without external infrastructure
• GitLab-native artifact and Pages flow
• reusable reporting infrastructure for QA pipelines

Repository: https://github.com/aleksandr-kotlyar/gitlab-allure-history

A Python project template for multi-browser Selenium test execution in GitLab CI and locally using Docker.

The project demonstrates:

• Dockerized browser test execution
• Selenium test automation structure
• GitLab CI integration
• reusable automation project template
• local and CI execution consistency

Repository: https://github.com/aleksandr-kotlyar/python-gitlabci-selenium

A CI/CD testing cookbook with practical examples for Python QA automation.

Includes examples for:

• pytest execution in GitLab CI
• test artifacts and reports
• Slack notifications
• linting and quality checks
• Allure logging and attachments
• parallel execution patterns
• Azure Pipelines examples

Repository: https://github.com/aleksandr-kotlyar/python_and_gitlab

A Java automation template for UI testing with JUnit, Selenide, Allure, WebDriverManager, and logging.

The project demonstrates:

• reusable Java test automation structure
• Allure reporting
• browser automation setup
• test framework template practices

Repository: https://github.com/aleksandr-kotlyar/java-automation-template

I have contributed to open-source tools used in Python test automation and Selenium-based UI testing.

Contributed fixes and improvements to webdriver_manager, a Python library for managing browser drivers in Selenium automation.

Contribution areas:

• browser driver version resolution
• Chrome / Edge / Opera driver handling
• driver cache and metadata logic
• CI stability for browser-related tests
• Selenium ecosystem compatibility

Repository: https://github.com/SergeyPirogov/webdriver_manager

Contributed to selene, a Python library for user-oriented Web UI browser tests.

Contribution areas:

• release and project tooling
• issue investigation and user support
• Selenium/Selene behavior analysis
• Python UI testing ecosystem improvements

Repository: https://github.com/yashaka/selene

I teach QA automation, Python testing practices, CI/CD quality gates, and test infrastructure design.

• niffler-py-st1 — staged qa.guru Python automation project for classroom practice and architecture demos
• niffler-py-st2 — advanced qa.guru Python automation project with fixtures, test data, and CI/CD practices

• qa_guru_python_advanced_1_2 — Python Advanced lecture/workshop materials for qa.guru
• qa_guru_python_1_9_jenkins — Jenkins CI workshop materials for qa.guru
• qa_guru_python_1_8_files — file handling examples for Python QA automation
• qa_guru_3_6_files — practical materials for working with files in automation tasks

Good QA engineering is not about adding more tests everywhere.

It is about building a system where:

• critical risks are covered early
• feedback is fast and reliable
• test results are observable and explainable
• flaky tests are treated as technical debt
• quality gates are explicit, measurable, and owned
• automation improves delivery instead of slowing it down

• QA strategy and test automation leadership
• CI/CD quality gates
• Test automation architecture
• Python / Pytest / Selenium
• Java / Selenide / JUnit
• GitLab CI
• Docker-based test execution
• Allure reporting
• Test observability
• Mentoring and engineering standards

QA Head, mentor, lecturer, and Senior Software Engineer in Test.

My background combines hands-on automation engineering with QA leadership: building test infrastructure, defining CI/CD quality gates, improving reporting and observability, mentoring engineers, and turning testing practices into scalable engineering standards.

LinkedIn: https://www.linkedin.com/in/aleksandr-kotlyar/