OWASP/wstg

Adapt guide to be inclusive of API testing

Open

#5 opened on Jun 15, 2017

View on GitHub
 (15 comments) (0 reactions) (2 assignees) (1,624 forks)github user discovery
good first issuenewrevise

Repository metrics

Stars
 (9,439 stars)
PR merge metrics
 (PR metrics pending)

Description

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.

Contributor guide

Research direction
Review existing guide sections, particularly sections 3 and 4.1, to identify where API testing processes differ from client side testing. Suggest specific language changes and potential new article content for API testing.
Tech stack
None
Domain
security
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75