22 ms·
I've noticed a hole in a lot of people's thinking where even if they thing to write automated testing or QA testing to ensure that a given thing is available to
by jerf 8y ago
I've noticed a hole in a lot of people's thinking where even if they thing to write automated testing or QA testing to ensure that a given thing is available to a certain user or role, there is often not a lot of thought given to writing tests to enure that users or roles that should not have access to the data can't get it.
I'm not sure I've ever found a permission system without explicit testing that the denials work that didn't turn out to have gaping holes in what could actually be done. Generally, the code that hides the UI for what you're not supposed to be able to do works, since that's visible, but on something like the Web where the user also has fairly direct access to the message bus the application is using to communicate to the web server, that's not enough.
- jakear 8y agoTesting a negative is much more difficult. Testing the positive is “can this user access this private data using this procedure”. Testing the negative is “can any use access any private data using any procedure”. That’s almost impossible to verify.