Software test automation with Python and PyTest.

Discipline
Software test automation
Engineering
Jarek Trepkowski
Principal Software Engineer
Focus
Python / AI / Automation

Python and PyTest test automation for APIs, integrations, regression and CI/CD. Test frameworks and QA consulting for product and engineering teams.

Discuss your tests
An engineer working with code on two monitors.
Software test automation

Tests that verify existing features after every change.

I build Python and PyTest tests that help catch errors before release. I connect product requirements with API, integration and workflow testing in CI/CD.

When is this useful?

For teams slowed down by manual regression, broken integrations after updates or unclear results from existing tests.

What do the tests cover?

APIs and integrations

Cross-system workflows: the contract, the response content and the record in the target system.

Regression of key features

Repeatable checks of important features after changes, with controlled data and a known initial state.

Failure and recovery

Error, timeout and recovery scenarios that show how the system returns to correct operation.

CI/CD and reports

Test runs in your release process and a report showing where and why a result differs.

An integration works before a change and breaks after release.

A new API version changes a response field. The calling service still receives status 200 but no longer saves correct data. The test verifies the contract, the response content and the record in the target system.

  • Repeatable inputs and a known initial state.
  • Data verification beyond the HTTP response code.
  • A report showing where and why the result differs.

From risk to a useful test suite

  1. Choose the workflows

    We start with the important workflows and your current release process. We agree what to automate, which data is needed and what a correct outcome looks like.

  2. Build the tests

    I prepare the Python/PyTest test structure, integrations and run instructions. Maintainable tests need shared requirements, controlled data and reproducible failures.

  3. Hand over to your team

    I connect the tests to your release process and reporting, and show your team how to add further scenarios.

What do you receive?

  • A test suite and environment configuration.
  • Release-process integration and reporting.
  • Documentation and a way to add further scenarios.

Automation and human testing

Repeatable scenarios are good automation candidates. Exploring new behaviour and evaluating user experience still require human testing.

Where do we start?

If you already have tests, I start by reviewing their structure, execution and results. The scope can cover fixing or extending your framework without rebuilding it.

Explore other services

Questions before we start

Can you work with an existing framework?

Yes. I first review its structure, execution and results. The scope can cover fixing or extending existing tests without rebuilding the whole framework.

What is your testing background?

Over 15 years working with devices, networks and data systems, including Samsung and Dell and projects for Intel and Cisco. The home page describes this experience.

Start with the problem

Let’s talk.

What isn’t working in your tests today? Describe your tools and the outcome you need. That is enough to agree the first step.

Email me directly: jaroslawtrepkowski@gmail.comYou can also contact me on LinkedIn.

B2B collaboration in Poland and Europe. I reply to every message personally.

All fields are required.

Your details are used only to reply to your message. Privacy policy.