TESTING, DIAGNOSTICS AND APPLICATION DEVELOPMENT

I help test, improveand develop applications.

I combine testing and diagnostics with focused code improvements and automation. I use AI and verify the results in practice.

How I can help

Testing and quality

Manual, automated and API tests, with performance verification before release.

Diagnostics and improvements

Investigating errors, logs and data, making focused code fixes and checking the results.

Tools and automation

Scripts, workflows and application tools that reduce repetitive work.

Explore services and how I work

SELECTED WORK

A product you can inspect, not just a claim.

MyAnalyze is the clearest example of how I turn an idea into a working product and keep improving it across real releases.

ReactTypeScriptNode.jsSQLiteElectronJest
See MyAnalyze quality evidence
WHAT TO LOOK AT
  • Attention to detail and consistency across a growing interface
  • Product ideas turned into practical user flows
  • Complex data and import workflows handled as one coherent product
  • Versioned releases, regression thinking and documented changes
  • Design decisions balanced with usability and business rules

HOW I CHECK QUALITY

From a risk to a specific check.

Examples based on MyAnalyze project tests. They describe checks, not a client audit or a guarantee of application-wide quality.

01

An import must not change amounts

Risk
A malformed amount can be misread as a valid number.
Check
Import tests cover corrupted values, different separators and signed amounts. Expected behaviour: reject the invalid row and preserve valid data.
Why it matters to your business
The same approach helps check data quality in order imports, reports and integrations.
02

Similar records are not always duplicates

Risk
Two legitimate transactions can share a date, description and amount.
Check
Separate tests cover similar transactions without identifiers and a repeated unique identifier. The rule should preserve the former and exclude an actual duplicate.
Why it matters to your business
This helps check whether a system drops valid records or saves the same data twice.
03

One change should preserve other data

Risk
Changing a card's available credit must not overwrite its debt.
Check
An account-model test checks that changing one value preserves the other. These checks can flag broken rules as the product changes.
Why it matters to your business
In client work, I look for the same dependencies: what could change behind the visible field?
Have a similar process to check? Tell me about it →
mikolajdworak@icloud.comLinkedInContact