You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
In section 16.3 Provide a Scriptable Interface, you list some of the downsides to adding test hooks to your system:
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.
The text was updated successfully, but these errors were encountered: