Use the Big List of Naughty Strings for QA input
Open
Nobody has claimed this yet.
1. to develop
enhancement
good first issue
low
tests
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
- use https://github.com/minimaxir/big-list-of-naughty-strings in CI jobs
Maybe add them to some unit tests or some integration tests. For example name files like that or post a comment to a file with those strings.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the repository's CI jobs and the unit or integration tests that accept file names or comments, then review how test inputs are assembled. Done means the Big List of Naughty Strings is exercised in CI and the relevant tests verify that those inputs are handled safely.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100