nextcloud/server

Use the Big List of Naughty Strings for QA input

Open

#3,122 opened on Jan 17, 2017

View on GitHub
 (1 comment) (0 reactions) (0 assignees)PHP (4,865 forks)batch import
1. to developenhancementgood first issuelowtests

Repository metrics

Stars
 (34,953 stars)
PR merge metrics
 (Avg merge 20d) (627 merged PRs in 30d)

Description

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

Research direction
Integrate the Big List of Naughty Strings into the CI pipeline by adding a job that downloads the list and runs tests with those strings as input for file names and comments.
Tech stack
php
Domain
backendtesting
Issue type
Test
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.
1-3 hours
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
GitPHP testing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90