or how to organize white-box / black-box testing

[Folkert Meeuw]

Hello Paul,
I made the experience to debug it, is the last step in software development life cycle. Not ever, the possibilty was given to debug it. The paradigm of testing allowed to debug it when white-box testing of software has the failure-fault-error cycle. What, when I made black-box testing? For example I had only a library of compiled, obfuscated code and but the chance on decompiled code, but not the chance to understood the logic and I guess the problem inside it? What would you (maybe Paul) suggest, at this case? Helped the applied use of Aspects?

Kind regards, Folkert M.

[Paul Butcher]

Folkert,

Am I correct that you're asking about debugging third-party code?

In which case, that is something that's discussed in the book. But having said that, if you don't have access to the source code then your options are going to be severely limited I'm afraid. You can certainly help the original author debug it by characterising the bug for them, however.

[Folkert Meeuw]

Paul,
thank you for your answer.

I don't have it yet, where is it discussed in the Debug It book?

Especially I would like to know that, would you use Aspects like AspectJ or AspectC++ to set mark-points into compiled binary third-party code? Or may I maybe complete misunderstand the concepts of using Aspects in programming?

Kind regards, Folkert M.