I’m working on a test integration tool. You write your tests declaratively using YAML (ie. setup the environment, databases, etc., load fixtures, make api calls or db calls, and check assertions), so it’s completely language agnostic, which makes it perfect for grey-box/black-box testing. This way of testing also ensures you’re testing functional, business cases, and gives great stability on an exposed interface, because everything runs with real dbs, real queues and so on. From experience, this way of testing hits the perfect balance between reliability, usefulness, maintainability (when done right), and verbosity (at a previous company we replaced the tests on all of our layers with this kind of integration tests and it ended up being the most stable code base and test harness we ever worked on).
I’m currently polishing the logs and reports as much as possible, and then I’ll add support for more tools (Kafka, Rabbit, Nats, etc.). I have tons of features in mind to improve UX, speed, and bring more value to the tests.
Down the line, I want to find a business model for this tool and sell it, but I need to do a lot of thinking on this side since I’ve never done this before.
replies(1):