Hello!
Hello!
I am adding tests to a suite.
To keep things clean, every interface has its own and they are all attached to a single DUnitX project.
Right now, however, I am facing a situation that I really do not fancy.
Our configuration interface needs to be tested to ensure that the right setting names are being used and I do not wish to expose those because I think it's wrong.
So, at the moment I have defined a public read only property which calls the protected method handling that. This property is only visible in Debug, using a compiler directive.
I think this should be OK, but I thought I'd check to see if somebody has got better ideas on how to test this :)
Thank you!
A
I am adding tests to a suite.
To keep things clean, every interface has its own and they are all attached to a single DUnitX project.
Right now, however, I am facing a situation that I really do not fancy.
Our configuration interface needs to be tested to ensure that the right setting names are being used and I do not wish to expose those because I think it's wrong.
So, at the moment I have defined a public read only property which calls the protected method handling that. This property is only visible in Debug, using a compiler directive.
I think this should be OK, but I thought I'd check to see if somebody has got better ideas on how to test this :)
Thank you!
A
Comments
Post a Comment