Skip to services

Functional testing and load testing

Software testing and performance testing.

Find out what works as intended, where users get stuck, and how your system behaves under load. You can also contact us for standalone testing of an existing system or one built by another developer.

Built around your goals

How a system behaves under load matters as much as its features.

Preparing to release a new version, receiving bug reports, or experiencing slowdowns? We adapt the assessment to your specific question, system and key user scenarios.

Software testing

Checking features and user journeys against agreed expectations. The aim is to make issues clear to describe and trace.

  • Features and workflowsWorking through key use cases, inputs and expected outcomes.
  • Documented issuesA clear description of the actual and expected behaviour, together with the steps needed to reproduce the issue.
  • Targeted retestingWhere required, checking fixes or retesting affected workflows in a new version.

Performance and load testing

Assessing response times and system behaviour under agreed load scenarios, so the results can inform further planning.

  • Scenarios suited to the real taskAgreeing on the operations to test, load stages and acceptance criteria.
  • Measurement and observationAssessing response times, errors and throughput alongside the available environmental data.
  • Identifying bottlenecksSummarising observations related to slowdowns or errors and suggesting areas for further investigation.

What will you receive?

Feedback you can act on.

We set out the exact scope and agreed tasks in the proposal. At handover, we review the completed work against them.

Testing summary

What was tested, in which environment, and against which criteria.

Issue list or measurement results

Depending on the agreed task, reproducible bug reports or measurement data that can be interpreted and used.

Next steps

A discussion of the findings, with possible directions for fixes and further testing.

Before testing, we agree on the test environment, access, features in scope and timing. Load tests take place in an environment and at load levels agreed in advance.

How we work together

Agreed goals.
Clear steps.

From the first conversation to handover, we clarify what happens and what is needed for the next step.

01

We clarify the question

We identify the version to test, the key workflows and the expected behaviour.

02

We plan the assessment

We agree on the scenarios, environment and measurement criteria.

03

We test and document

We carry out the agreed checks or measurements and record the findings.

04

We discuss the results

We present the findings and the agreed options for moving forward.

Before the next step

What to
clarify in advance.

Can you test a system built by another developer?

Yes. Testing is also available as a standalone service. Before work begins, we clarify the expected behaviour, the available environment and the access required.

What is the difference between the two types of testing?

Functional testing checks whether a feature or workflow produces the expected result. Performance and load testing also measures how the system behaves under a defined workload.

Does testing include fixing the issues?

The testing work delivers an assessment and documented feedback. The scope of fixes, development work and retesting is agreed separately.

What does a load test tell me?

It shows how the tested version behaved in the given environment and load scenario. Test data, resources and the types of operations must also be considered when drawing conclusions.

Let’s start with your idea

What would you like to know
about your system?

Describe the platform, the important workflows, and any errors or slowdowns you are experiencing. It is also helpful to mention the planned handover date.

Email us directly

iroda@officexpert.hu

Your goal and a few key details are enough for the first message. They give us a starting point for the discussion.