The latest articles on DEV Community by XAVIER. (@0x887xavi). https://dev.to/0x887xavi https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3910362%2F621ee0fa-3523-48fc-be34-11b5aba8196a.jpg https://dev.to/0x887xavi en XAVIER. Tue, 10 Nov 2026 20:32:03 +0000 https://dev.to/0x887xavi/what-if-you-could-test-a-software-product-without-access-to-its-source-code-2b52 https://dev.to/0x887xavi/what-if-you-could-test-a-software-product-without-access-to-its-source-code-2b52 <p><a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7kxml2vpvz9hgmz5k8jq.jpg" class="article-body-image-wrapper"><img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7kxml2vpvz9hgmz5k8jq.jpg" alt="Test a product without code"></a></p> <h2> What If You Could Test a Software Product Without Its Source Code? </h2> <p>Most testing workflows assume you already have access to something.</p> <ul> <li>The source code</li> <li>The repository</li> <li>An API specification</li> <li>An existing test suite</li> <li>The internal infrastructure</li> </ul> <p>But what if you want to examine a product from the outside?</p> <p>That is where black-box testing starts.</p> <h2> What black-box testing means </h2> <p>Black-box testing looks at what a system does, not how it is built.</p> <p>You send an input.<br> You watch the response.<br> You check if the system behaves as expected.</p> <p>For web apps and APIs, a URL can be your starting point.</p> <p>Here is the flow:</p> <ul> <li>You open your terminal</li> <li>You run one command</li> <li>You enter a product URL</li> <li>You pick the tests you want to run</li> </ul> <p>That is the idea behind Void CLI.</p> <h2> What Void does </h2> <p>Void is a URL-driven testing tool. Each test type runs on its own independent engine.</p> <p>Planned test types:</p> <ul> <li>Functional testing</li> <li>Contract testing</li> <li>Load testing</li> <li>Stress testing</li> <li>Passive security testing</li> <li>Fuzz testing</li> <li>Regression testing</li> <li>Integration testing</li> </ul> <p>Some tests need more than a URL. They may need:</p> <ul> <li>An API specification</li> <li>A baseline</li> <li>Endpoint definitions</li> <li>Explicit test scenarios</li> </ul> <p>The goal is to give you all of these capabilities in one developer workflow.</p> <h2> Where the project stands </h2> <p>I am building Void in private.<br> I am working toward the first alpha.</p> <p>I want to hear from:</p> <ul> <li>Developers</li> <li>QA engineers</li> <li>Infrastructure engineers</li> <li>People who build developer tools</li> </ul> <h2> Your turn </h2> <p>What frustrates you most about testing a product when you don't have its source code?</p> <p>Share it in the comments.</p> <h2> Join early </h2> <p>Follow the project or join the early waitlist:<br> <a href="https://void-waitlist.vercel.app" rel="noopener noreferrer">https://void-waitlist.vercel.app</a></p> security softwareengineering testing