Engineers build. Vaktum tests.
Created out of frustration after another failed deployment
One afternoon we got another dreaded Slack message from one of our customers. "Endpoint xxx is not working anymore, did you change anything?".
It turned out one of our engineers had changed the format of a field in our API, which broke their integration. Frustrated of how we missed it, we started thinking of a better solution to fix the problem once and for all.
Vaktum tests, so that the team can build
Our mission is to free the team from the burden of testing, and free up their time and mindspace to focus on building great software.
We test your platform
- End-to-end functional testing
- Our AI generates a custom test plan for your platform
- Support for almost any API
- We support OpenAPI, GraphQL, gRPC, SOAP, webhooks and more
- Identify potentially breaking changes
- Monitor platform API responses and warn when changes are detected
Our AI does it for you
- Get started fast
- Point us to your API documentation and environment, we do the rest
- Reduce effort managing broken tests
- We keep your tests up-to-date as your platform evolves
- Faster product development
- Shorter dev cycles with immediate feedback on your code changes
Vaktum supports most API standards and notification protocols
Get Started in 4 Simple Steps
Getting started with Vaktum is easy. Get started in hours
Upload API specification
Upload your technical spec (OpenAPI, .proto, .graphql, Postman, …). Don’t have one? No problem we can generate it for you
Generate tests
Our AI generates tests for you based on the specification or created/edit the tests yourself
Run tests
Connect to your environment then run the tests on Vaktum.com, in your CI/CD pipeline, on a schedule or using our CLI tool.
Get notified
We let you know if there are any issues over Slack, Email, Webhook or by creating a ticket for you in your task management system
Is Vaktum the right tool for your team?
Designed for developers
Less stressful deployments
Spend time on what you love
Your are in control
Collaborate with your team
Get started for free
Why introduce Vaktum in your test stack?
Vaktum vs. UI testing
It is challenging to test the entire functional scope of an application with UI tests only. UI tests often take long to execute, and are time consuming to maintain
Vaktum vs. manual testing
Manual QA is resource intensive and adds delay to the development process. It is hard for humans to keep attention when performing repetitive tests for longer timeframes
Vaktum vs. unit testing
Unit testing is not designed to capture issues from larger system interactions. While effective for specific code snippets, it often misses larger system issues
Vaktum vs. code analysis
Code analysis e.g. SonarQube can identify problematic technical issues and the risk for functional problems. It often does not capture issues with code changes that are technically “correct” yet undesired.