Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Downsides to hooks: there's part of the real interface you're not testing #71

Closed
carols10cents opened this issue Sep 1, 2015 · 1 comment

Comments

@carols10cents
Copy link
Contributor

In section 16.3 Provide a Scriptable Interface, you list some of the downsides to adding test hooks to your system:

It’s a security risk, for one thing—if someone discovers how to access the test hooks, they may be able to determine hidden information, overwrite data, or perform other malicious actions (or simply be curious and make a mistake). Adding a scriptable interface will require additional complexity in the program, as well as additional program length and size. The interface may be a drag on performance. Finally, time spent working on the interface means less time spent writing other features of the software, or improving its quality.

I feel like some of this gets close to, but doesn't come out and say, that you're now deliberately bypassing the way real users will interact with the system and you may miss defects that happen all the time in the real interface but never happen in the scriptable interface.

@laboon
Copy link
Owner

laboon commented Sep 4, 2015

Made explicit in 7598cb1

@laboon laboon closed this as completed Sep 4, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants