Proactive Debugging

As software complexity increases, developers must become more responsible for their contribution to the overall development project. It is becoming harder and harder for the developer to consider robust, end-to-end testing of their code an unachievable luxury.

In fact, developers need to proactively debug - that is, treat testing as an integral part of the development process, rather than waiting for defects to force their hand.

And why should this not be achievable? The advantage of proactive debugging is that it is manageable - testing is only performed on the code known intimately well by the developer (barring the case of inherited code, where the runtime tracing feature plays such a crucial role). There is little chance for confusion, so the time spent developing and deploying tests are optimized. Defects are eliminated early, ensuring that any system level defects that have slipped through the nets won't find their origin deep in the code. And test independence - due to the Target Deployment Port technology - ensures test reuse despite changes in target architecture.


Matters improve further when one considers the built-in integration that HCL OneTest Embedded possess with other products from software. HCL OneTest Embedded is integrated with: