Understand the connected system
API and integration testing, automation and UAT across financial products and payment workflows.
Where my product thinking became technical—through financial workflows, integrations, quality and delivery.
Overview
Technical QA taught me to read the product as a connected system: interface, data, APIs, acceptance and release behavior.
- Test the requirement
- Question the requirement
- Improve the experience
- Define the change
- See it delivered
Turn review into improvement
Used documentation and test-case review to surface clearer use cases, flows and interface behavior.
Connect quality with delivery
Connected technical validation with Scrum facilitation and distributed collaboration.
Quality managed as a product system
The Test Plans inventory shows the test-management context across Finance in Motion work. It is evidence of the environment and workflow—not a claim that every visible plan or item was authored or owned by me.
Main Challenge
Beyond the happy path
Payment and financial workflows need explicit behavior for invalid inputs, alternatives, retries and failures.
Beyond literal acceptance
A requirement can be testable while still leaving a use case, flow or interface unclear.
Across people and systems
Technical expectations need shared understanding across engineering, QA, business counterparts and distributed teams.
Featured Decisions
From testing requirements to shaping delivered changes
Review became a way to improve the experience, not only check the implementation.
ContributionIdentified accepted flow and UI improvements; later authored several delivered user stories.
Validate the payment system across its branches
Ineco EasyPay regression covered payment intents and payments across four currency suites.
ContributionAPI and integration testing with automated regression.
- Regression scope
- 121 API requests/checks
- Currency suites
- AMD · USD · EUR · RUB
- Coverage
- Positive + negative paths · Multiple Choices flow · retry/idempotency
Examine behavior under concurrent demand
Performance testing added a system-level view of payment-intent behavior.
ContributionJMeter testing and analysis of concurrent payment intents.
- Method
- JMeter · concurrent payment intents
- Test profiles
- Smoke · baseline · stress · spike
- Analysis
- Latency · throughput · error rate · timeouts
Selected Evidence
Scrum leadership in practice
This complete Fimvest retrospective board supports the Scrum and delivery context.
People behind the delivery
A workshop with colleagues from Germany and Kenya shows the distributed collaboration behind the work.