The Software and Systems Engineering Experts​
The Software and Systems Engineering Experts​
SmarterProcess logo

Contacts

SmarterProcess / ReqPro

ul. Antoniego Pajdaka 5/98
03-134 Warsaw, Poland
NIP : 8921405210
Regon : 146293701

About Products

About us

Ink drawing: a consultant beside a client engineer at two monitors, with a control unit on a test bench behind them
Sketch: a completed checklist with an acceptance seal and a key on a server module

Handed over, ready to run · your team keeps the know-how

Process Consulting

Test automation consulting services

We check what is worth automating, choose the tools and build tests that run in every pipeline.

Overview

Test automation that starts with your process, not with a tool

We check what is worth automating, choose the tools and build tests that run in every pipeline.

Before any script is written, we go through your current tests with your team. Each test goes into one of three groups: automate first, keep manual, or fix before automating. One business flow then runs as a pilot, so you see how the tests behave in your pipeline before the full suite is built.

The suite covers four test levels: integration and API, user interface, performance and security. For each level we pick the tool that fits your needs, the maturity of your team and your budget, from HCL DevOps Test and OpenText to open source. Your testers write the later scripts with us, so they can run and extend the suite on their own.

Once the suite is in place, it checks the whole business process again after every change and sends the results to one place. Specialists spend less time on repetitive testing and can use that time for exploratory tests and a closer review of new features before each release.

Your starting point

Where does your test automation stand today?

Most teams come to us at one of these points. Each one ends with tests that run without repetitive manual work.

Automated runs nobody trusts
Red runs nobody can explainScripts audited, optimized
Regression tested by hand
Manual tests every releaseRepetitive tests automated
Scripts nobody maintains
Written once, never updatedSteps the team can update

Also a starting point

See what is worth automating

Before you automate

  • A tool chosen before the process is clear

Inside the test team

  • Errors found one after another, not in parallel
  • Only developers can automate tests

What's worth automating

Not every test should be automated

Before any tool is chosen, we sort your tests into three groups. You get this list at the end of the first stage.

Automate first

Runs often, changes rarely, costly to miss.

  • Regression of stable business flows
  • API and integration checks
  • Smoke test on every build
  • The same steps with many data sets
  • Load test before each release

Keep manual

Needs a human eye or changes too fast.

  • Exploratory testing
  • Usability and the look of the screens
  • Checks you run only once
  • Features still changing every sprint

Fix before automating

Automation would only repeat the problem.

  • A test environment that is often down
  • No repeatable test data
  • Test cases without expected results
  • Requirements nobody agreed on

Four questions we ask about every test

01How often does it run?

02Does the flow still change?

03What does a missed defect cost?

04Can the test data be repeated?

Test levels and tools

Four test levels, each with the tool that fits it

We choose the tools for your needs, the maturity of your organization and your budget.

Integration and API

Services, messages and interfaces between systems, tested before a screen exists.

Tools

  • HCL DevOps Test Integrations and APIsformerly Rational Integration Tester
  • Open source API test libraries

User interface

Web, desktop and mobile flows that a user clicks through, end to end.

Tools

  • HCL DevOps Test UIformerly Rational Functional Tester
  • OpenText Functional Testingformerly UFT One
  • Selenium
  • Playwright

Performance

Load and stress tests with many virtual users, before a release and after big changes.

Tools

  • HCL DevOps Test Performanceformerly Rational Performance Tester
  • OpenText LoadRunner
  • JMeter

Security

Scans of running applications and source code on every build.

Tools

  • HCL AppScan
  • OWASP ZAP

Results from every level can go to IBM Engineering Test Management or to your pipeline.

How we work

Start with one flow, then scale

A pilot on one business flow shows whether automation pays off for you, before the whole suite is built.

  1. 1

    Assess

    We sort your tests and audit your projects, teams and current scripts. You get the list: automate, keep manual, fix first.

  2. 2

    Pilot

    We pick the tools for each test level and automate one business flow end to end, running in your pipeline.

  3. 3

    Scale

    We add more flows. The same tests run on every build, and the results land in one place.

  4. 4

    Hand over

    We set up the suite and write the first scripts. Your testers write the next ones with us, and we train them on the selected tools.

The same automated tests run on every build and send their results to one placeThe same automated tests run on every build and send their results to one place

Ways to work with us

  • ConsultingTool selection and how to organize test automation in your company.
  • Building testsTest scripts for the selected tools, and the tools set up in your organization.
  • AuditYour current scripts, projects and test teams, with a list of what to fix.

What you get

What stays with your team

Two test engineers review automated test results on a monitor

Automation map

Every test sorted: automate, keep manual, fix first.

Scripts in your repository

Readable, with naming and review rules.

Pipeline jobs

Tests run on every build.

Results in Test Management

Linked to requirements, if you use IBM Engineering Test Management.

Audit report

For existing scripts: what to fix and what to drop.

A trained team

Your testers run and extend the suite.

FAQ

Questions we hear before a test automation project

What do you automate first?

Tests that run often, change rarely and cost a lot when a defect slips through: regression of stable business flows, API checks and the smoke test on every build.

Is test automation worth it for our company?

It depends on your process. Assessing it takes analytical expertise, so we check whether automation can help before any tool is chosen.

Our automated tests fail at random. Can you fix that?

Usually, yes. We audit the scripts and the test environment, find what makes the runs unstable, such as timing, shared test data or an environment that is often down, and fix it or tell you which tests to drop.

Do you work with Selenium and Playwright, or only commercial tools?

Both. We work with HCL DevOps Test, OpenText and open source tools such as Selenium, Playwright and JMeter. Which ones fit depends on what you test and what your team already knows.

Can automated results go to IBM Engineering Test Management?

Yes. IBM Engineering Test Management runs automated tests through adapters for IBM and HCL tools, open source frameworks and command line scripts, and collects the results centrally.

Do we need IBM Engineering Lifecycle Management to use this service?

No. Without it, the results go to your pipeline or to the reports of the test tool you use.

Can you review the test scripts we already have?

Yes. We audit and evaluate your current test scripts and optimize them.

Do you train our test automation team?

Yes. We train test automation teams on the selected test tools.

Talk to our consultants

Leave your details and we will get back to you, usually within one business day.

    We will only use your details to respond to your inquiry. Privacy policy