Indicative EUR starting prices, not fixed quotes. Complexity, integrations and agreed testing determine the final proposal.
What you receive
An agreed application area, risk focus and test-data approach
Findings with reproduction steps, expected versus actual behavior and priority
A written release-risk summary, with coverage limits made explicit
For automation: an agreed Java/RestAssured suite, execution guidance and handover
What to bring
Identify the release, critical journeys and known risks
Provide API documentation and an approved staging or test environment
Use test accounts and synthetic or approved data, not production customer records
Agree permissions, exclusions and how destructive operations will be avoided
A focused audit is not a security certification, penetration test, accessibility certification or guarantee of defect-free software. Load testing, broad platform coverage and ongoing monitoring need separate agreements.
No. A focused manual audit can be the right first step. Test strategy, regression scenarios, Postman and automated API checks are selected according to the agreed risks and scope.
Which tools can be used?
Professional capabilities include Java, RestAssured, JUnit, Cucumber, Postman, SQL, Maven, Jenkins and CI/CD. Tooling is agreed around the existing project rather than imposed as a new platform.
Is the public QA example client work?
No. The public sample documents an actual issue and regression checks on Made by KREATIV's own website. It demonstrates the reporting approach without exposing employer or client systems.
