-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Adapt guide to be inclusive of API testing #5
Comments
Refer issue OWASP#5
#76 partially addressed this issue. A review of existing articles is still outstanding. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I can take this one. |
I see there is “testing for APIs” page (in the root of the repo). I would like to suggest taking this content and reworking it into several subtopics within the API section. Starting with a 00-API Testing Overview Section. Interesting in leadership thoughts on this approach. |
I think this makes sense! Would you like to do a rough draft for the new content? I'm happy to help go over it then. |
Thank you. I almost have a PR ready for the Overview section. |
@victoriadrake There is a PR available for you to review. |
Related to OWASP#5 and follow-up to OWASP#1140 Signed-off-by: kingthorin <[email protected]>
Web-based APIs can, for the most part, be testing using this guide. Some elements are naturally client-side and therefore irrelevant to API testing.
I suggest that we create an article in section 3 or 4.1 that talks about how the guide can be used for API testing.
I further suggest that we review the existing articles to ensure that the language used is appropriate for web app and APIs alike, and determine where any additions might be needed where testing for the same issue on an API involves a different process.
The text was updated successfully, but these errors were encountered: