microsoft/restler-fuzzer

include replay log paragraph in replay documentation

Open

#415 opened on Dec 3, 2021

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (329 forks)auto 404
documentationhelp wanted

Repository metrics

Stars
 (2,929 stars)
PR merge metrics
 (PR metrics pending)

Description

Include the following in replay documentation, which currently is only included in the replay file.

This log may contain specific values for IDs or names that were generated during fuzzing, using the fuzzing dictionary. Such names will be re-played without modification. You must update the replay log manually with any changes required to execute the requests in your environment (for example, replacing pre-created account, subscription, or other resource IDs, as needed).

Contributor guide

Research direction
Locate the replay documentation file in the repository and add the provided paragraph about the replay log.
Tech stack
python
Domain
apisecurity
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90