When testing software, it's easy to focus on whether the expected inputs work.
But what about the inputs that shouldn't work?
What happens when a booking system receives an impossible date, an unsupported number of guests, or a reservation that exceeds the maximum allowed duration?
I'm working on AgentAntibodies, an early-stage tool designed to help developers and QA engineers generate structured test scenarios from business rules.
Here's a simple example
Imagine a booking application with these rules:
Reservations must have between 1 and 6 guests.
The maximum stay is 30 nights.
Reservation dates must be valid.
AgentAntibodies can generate valid and invalid scenarios based on these constraints, export the cases as JSON or JSONL, and support comparisons between expected and actual application behavior.
Where the project stands
We currently have a working local beta with an automated test suite.
However, passing internal tests doesn't prove that the tool is useful in real development workflows. That's exactly what we want to find out.
Looking for 3 beta participants
I'm looking for developers or QA engineers willing to:
Review a short demonstration.
Try a controlled test using sample data.
Share feedback about usefulness, limitations, and missing features.
Participation is free. No production access or sensitive information is required.
If you're interested, leave a comment below.
I'd also love to hear: How do you currently generate negative test cases from business rules?
Top comments (0)