What If You Could Test a Software Product Without Its Source Code?
Most testing workflows assume you already have access to something.
- The source code
- The repository
- An API specification
- An existing test suite
- The internal infrastructure
But what if you want to examine a product from the outside?
That is where black-box testing starts.
What black-box testing means
Black-box testing looks at what a system does, not how it is built.
You send an input.
You watch the response.
You check if the system behaves as expected.
For web apps and APIs, a URL can be your starting point.
Here is the flow:
- You open your terminal
- You run one command
- You enter a product URL
- You pick the tests you want to run
That is the idea behind Void CLI.
What Void does
Void is a URL-driven testing tool. Each test type runs on its own independent engine.
Planned test types:
- Functional testing
- Contract testing
- Load testing
- Stress testing
- Passive security testing
- Fuzz testing
- Regression testing
- Integration testing
Some tests need more than a URL. They may need:
- An API specification
- A baseline
- Endpoint definitions
- Explicit test scenarios
The goal is to give you all of these capabilities in one developer workflow.
Where the project stands
I am building Void in private.
I am working toward the first alpha.
I want to hear from:
- Developers
- QA engineers
- Infrastructure engineers
- People who build developer tools
Your turn
What frustrates you most about testing a product when you don't have its source code?
Share it in the comments.
Join early
Follow the project or join the early waitlist:
https://void-waitlist.vercel.app
