Drill4J Real-time white-box regression testing tool

Currently, Drill4J does not support .NET applications (.NET Framework or .NET Core) in production environments.

We’re currently evaluating full .NET support - it’s in the POC phase, and no production-ready setup is available yet. If this is something you’re interested in, we can offer paid services to implement it specifically for your organization. Otherwise, you’re welcome to wait for general availability, though there’s no defined ETA at this time.

Hi Manishankar,

Thank you for your query.

The answer to your question is a bit more nuanced than a simple YES or NO.

Essentially, you do NOT require direct access to the codebase or the code storage system to use Drill4J.

However, the unique aspect of the Drill4J agent’s operation is that it needs to be launched concurrently with the application, specifically initiating with the JVM process in which your Java application is running.

Once activated, the Drill4J plugin, as a part of the operational Java ecosystem, will have access to the application’s instructions.

This access allows it to provide the detailed insights required for effective testing.

Therefore, while direct access to the code is not necessary, what you will need is the cooperation of system engineers or DevOps professionals who deploy the application under test.

They would be instrumental in launching the test application integrated with Drill4J.

Hope this helps.

No, we haven’t used log4j in our solution: Drill4j admin bases on logback logger. Agent part bases on our custom Native logger.

Drill4J is extensible from the codebase. You can easily develop your own plugins.

To begin, you need to install Drill4J. There is a detailed instruction on GitHub, how to install this automated regression testing tool. Please follow the link.

Yes. It will work with your JVM-based application deployed in your infrastructure.